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.

Labels:

Comments

Post a Comment

Popular posts from this blog

Delay on YouTube Feeds

Most YouTube feeds have not sent new notifications since 2023-10-02 14:20 UTC. We will be triggering a manual YouTube feeds over the next hour and all missing notifications will be sent. If you have any missing notifications after 2023-10-05 14:00 UTC please reach out to support. Update 14:00 : All updates have been sent. If you believe that you are still missing updates feel free to reach out. The rest of this post is a technical analysis of the issue. Background This was caused due to recent emergency response to YouTube WebSub notifications. The emergency response was necessary is due to the following factors. YouTube WebSub posts are not spec compliant and do not contain the required information to send notifications. Therefore FeedMail uses these notifications as a "ping" to re-fetch the feed. YouTube often sends notifications before the entries appear in the feed. The exact reason is not known but sometimes entries do not appear for up to an hour after the WebSub push. ...
Post a Comment
Read more

Invalid DKIM Signature for Some Mail

As of 2023-07-26 FeedMail messages sent via AWS SES have an invalid feedmail.org DKIM signature. This may result in messages ending up in your spam folder. This is an ongoing issue and updates will be posted here as they are available. 2023-09-25 We have issue an update that should avoid SES re-formatting signed fields. This is a workaround but should result in valid signatures. Who is affected? This is unlikely to affect most of our users for the following reasons: 97% of our mail is sent by us directly, not via AWS. This mail still has a SPF-verified sending IP. However this may still affect users because spam filters may consider these messages less "good" than they would have been with a valid DKIM signature. The most notable Inbox Providers affected by this are Apple and Microsoft. FeedMail uses AWS SES for these providers as they reject all messages from our network provider. However other smaller providers may also have a portion of their messages sent via AWS SES. ...
Post a Comment
Read more

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.
Post a Comment
Read more