Skip to main content

New Burst Protection Algorithm

To protect users against surprise charges, FeedMail covers the cost of sudden bursts of updates. The initial algorithm, only charging once a day, was too simple. Many feeds regularly see multiple updates a day and the burst-protection algorithm was artificially subsidizing these feeds.

FeedMail is now using an updated algorithm to protect from bursts. The exact implementation is subject to change but is based on the following principles:

  • Updates more than 24h apart are almost always charged.
  • An average update rate is tracked per-feed. If a feed suddenly starts updating faster than the traditional rate the additional updates will not be charged.
  • The average is updated over time, so if a feed continues updating at the elevated rate credit consumption will slowly increase to match the new update rate.

FeedMail aims to be very low cost. To achieve this we need to keep our expenses predictable and fair. Otherwise we would need to overcharge some users to cover uncertainty and higher cost users.

To be fair to users who have purchased credits with the previous expectation in mind existing paid users will have their credit balance doubled to account for this difference. Based on our analysis this means that the remaining balance will last longer for all existing users. If any paid users feel like this will reduce the value of their credits please reach out to our support team and we will find the fair adjustment.

Comments

Popular posts from this blog

Changes to Billing for Multiple Simultaneous Updates

This change may result in increased credit usage for non-digest subscriptions. Am I Affected? Digest Subscriptions are unaffected . Owner-paid Feeds are unaffected . Frequently updating real-time subscriptions are affected . If you have questions regarding your specific subscriptions please contact FeedMail support . Background FeedMail pricing has always been 1 credit per email notification. However in practice FeedMail would charge at most 1 credit every time a feed was checked, even if there were multiple new items on that feed and multiple emails were sent. In other words FeedMail sometimes undercharged users. Going forward, this billing error will be corrected, which may result in higher credit usage for feeds that were previously undercharged. Correcting this issue is essential to preventing abuse, ensuring long-term sustainability, and maintaining fair pricing. Multiple updates are a rare occurrence. It usually happens on on feeds that update very often (faster than once every 5...

Support for SMTP MTA Strict Transport Security

FeedMail now supports SMTP MTA Strict Transport Security (MTA-STS) . This standard provides receiving domains a way to attempt to indicate that incoming mail should only be delivered over a secure connection. When FeedMail receives this signal it will refuse to deliver over insecure connections (retrying mail as required). FeedMail does not currently support SMTP TLS Reporting (TLSRPT) . We will be reaching out to any existing customers who's mail may be rejected due to this change.

Planned Database Maintaince

FeedMail will be undergoing database maintenance starting at 2025-03-20 22:00 UTC. You can use this site to view this in your local time zone: https://dateful.com/eventlink/1416363428 . This maintenance is expected to take about 30 minutes. During this time FeedMail will not send feed updates but should be mostly available for logging in and viewing your subscriptions. If complications arise, the maintenance window may last longer. This post will be updated at the start and end of the maintenance window and as needed if the expectations change. Feed updates will automatically resume when maintenance is complete. Updates 22:00 Maintenance started. 22:15 FeedMail is fully operational again. 22:24 Maintenance complete.