If you're publishing your podcast entries directly via the FeedPress dashboard, you are now able to edit the Episode ID that will be present in the XML feed. It's useful in some cases like when it's used by a third party app to identify your episodes.
When you upload a picture in the podcast post editor, the uploaded picture will be seen as the episode thumbnail by podcast clients like Spotify.
We experienced a worldwide network outage that made FeedPress unavailable between 6:00 and 7:00 UTC.
The downtime was due to a worldwide outage by our hosting provider (OVH). Apparently due to human error that has been fixed.
More details here: http://travaux.ovh.net/?do=details&id=53798&
We fixed an issue that could occur when you tried to synchronise your Dropbox account to your FeedPress account.
We've seen a change of feed hits by Apple since the last Apple Podcasts updates, leading to a decrease of subscribers count on this client (you can see it as well in your feed dashboard by clicking on the Podcasts clients menu item).
It appears that since the last update of Apple Podcasts the client app (which fetches the RSS feed) doesn't refresh as often as before, therefore you can see an important drop. Currently we're showing you a 7-day sum of unique hits but maybe it's not the most relevant figure anymore.
What we will do is spread the 7-day unique subscribers count to 30 days in order to have a better overview of infrequent clients. We could also look at integrating unique downloading IP addresses as subscribers, but that would work only if you have download tracking enabled on FeedPress.
On March 10 our ISP had a major incident in one of their datacenter in France. A fire destroyed a whole datacenter.
While we don't have any server in that specific datacenter some services were directly impacted because of the electricity outage. Load balancers have been replaced by backups to ensure feeds delivery.
What could be missing while we're waiting for electricity and connectivity:
HTTPS certificate renewals (although we renew them at least 60 days in advance)
Podcasts files if they were hosted on the new infrastructure
Don't hesitate to contact us if you need help.
More info here regarding the situation: http://travaux.ovh.net/?do=details&id=49484
On some HTML content the width of the pictures could exceed the newsletter width. We fixed the issue automatically for all newsletters.
Our enclosure detection engine now supports binary/octet-stream media files as well as classic audio/mpeg files. This binary type is usually sent by CDN like Amazon Web Services.
If you have a custom hostname on FeedPress you can add specific records like a URL redirection or pointing to a feed. You can also now set a
410 Gone HTTP status for old feed URLs that you want to delete from crawler bots or podcast clients for example.