Feedbin Updates

Reeder Update

Reeder 3.2 is out. This update brings support for the faster and more accurate version 2 of the Feedbin API. Between the API change and what I can only assume is some sort of magic added by Silvio, sync is fast. Very fast.

I encourage everyone to update because:

API V1 Deprecation

With the release of Reeder 3.2 all major clients are using version 2 of the API. I’d like to deprecate version 1 as soon as possible because it uses a ton of database resources. The index for the records that track read/unread information for V1 of the API has grown to about 30GB, most of it sitting in RAM at all times. Getting rid of this will be huge relief for the database server.

If you are still using V1 of the API for anything please let me know. Version 2 is very similar except for the way it tracks read/unread information so it should be easy enough to switch over. Check out the documentation for more details.

Pricing

I announced this on Twitter yesterday but the price for new customers has gone up to $3/month or $30/year. The plan for the extra money is to be able to invest more in Feedbin. The types of things I’d like to spend the money on are paying for top-of-the line hardware, building expensive features like search and if I’m really lucky, hiring some help. It’s hard to say whether it will pay off because I definitely expect less people to sign up.

The rates for all existing customers will remain the same.

I was surprised and touched when existing customers started saying they would pay more, given the option, so this is now possible in your billing settings.

The Future

Now that the server move is out of the way and v1 of the API is on the way out, some real work can begin. First up is a long list of issues and feature requests that have been ignored for far too long. After that Todd and I have a bit of a redesign in the works. Finally there is one surprise that could have a big impact on Feedbin, but I’m not quite ready to talk about that yet :)