- RF-141 – Add Deauthorize option to Twitter Credential
This works just like the option of the same name on the Facebook credential – it disconnects your app from the connected Twitter account. It is not technically required by Twitter’s developer terms, but it makes for you to want it.
- RF-168 – Fix Scribie result formatting
This transcription service is very reliable and provides great quality at a low-to-modest price, but the output format has been a problem, almost entirely because of our very limited implementation (no one was using it, so why should we improve it?). That is now largely fixed. If you are interested in creating transcriptions from audio, then ask support and I’ll show you how. It’s a common need right now so I don’t see the need to do full-blown documentation yet, but that is coming, see RF-156 below.
- RF-140 – Associate Facebook Pixel with each promoted ad
This was a (minor) oversight in the 5.0.0 release. It caused no loss or even reduction in function, but it did reduce the reporting of ad success for the campaigns run via ResultFlow. This is “retroactive” in the sense that all ads run through ResultFlow will now be associated with the ad account pixel. On the other hand, it is not retroactive in the sense that reporting for existing and expired ads is updated – that’s simply impossible.
- RF-149 – Implement GA parameter removal and Google Alerts redirect in feed reader
In Persona v13, you will find a set of workflows in a “Clean Urls” folder that run a script to remove Google Analytics parameters and execute the Google Alerts redirect. In Persona v14, we removed these functions and implemented the equivalent in the backend system that loads feeds – except it did not work quite right. 🙁 It is now fixed. For all new feed items, starting mid-day 18-Mar-2019, you will find that the feedItemUrl parameter is devoid of GA parameters and is *never* an Alerts URL. Moreover, these changes fix a bad interaction between Google Alerts and OpenGraph image load.
- RF-155 – Replace COD result email stream with SES+Workmail
I know that makes no sense to anyone outside our development staff, but stay with me…
There has been a long standing intermittent issue with getting COD results into your app once they were completed in the COD Factory in our app. You see, we run everything in ResultFlow too, and use an email venue to connect our app to a backend system that connects to yours. Simple and elegant. Also not reliable! The culprit was gmail. It was throttling access without notice, and while we were not losing any work, we we were not processing it either. We are now (reliably!) running the same scheme on Amazon – where we run everything else as well. Thank you Jeff Bezos!
- RF-156 – Non-text feed item failing due to OG image load
Here’s a little secret – behind the scenes we are working with “a very influential podcaster” to develop the next killer-app for podcasters. Part of that required that we actually read a podcast feed, which we could not, because we specifically rejected it. Hey, it made sense at the time, okay? Now we’re fine with podcast feeds … and youtube feeds too BTW. Stay tuned for more on this as it develops (rapidly) in the coming weeks.