We have removed the support for TLS (Transport Layer Security) versions 1.0 and 1.1 from our load balancer. TLS is a protocol that encrypts and delivers data securely over the internet, preventing eavesdropping, tampering, or message forgery.

TLS 1.0 and 1.1 are outdated encryption protocols that are no longer considered secure against modern threats. They lack support for current cryptographic algorithms and hash functions, which are crucial for protecting the integrity and confidentiality of data.

We added a handy privacy feature on your feed settings page.

There is now a checkbox called "This is a private feed".

Your feed will not be publicly available on the feedpress.me domain. If you want your feed to be available on a specific URL, you will need to add a custom hostname record.

You can now duplicate posts directly in your Publishing dashboard, just click on the right button next to your post you want to duplicate.

You can now write a post and publish it for later.

To be able to do that, just set any date in the future and publish the post (not draft).

The post will automatically be visible in your feed on the specified date.

You can now upload your transcript file directly in the FeedPress podcast post form.

You can now customise the URL of your podcast post (usually displayed as "Episode Website" in Apple Podcasts etc.).

You can also specify a transcript file URL for every episode.

You can now send yourself a newsletter to your email address, to test your fancy custom template update.

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&