Feedly does not currently have a good feed management interface. We offer a dashboard and a springcleaning page but they only offer the option to edit a single subscription at the time. The result is that it is currently not very easy to manage categories.

But Feedly is integrated with Google Reader and Google Reader has a really nice interface to manage subscriptions. So here is how you can work around the problem:

1. Go to the settings page in Google Reader
2. Click on subscriptions
3. Use the Google Reader UI to manage subscription and categories (you can do any operation that the Google Reader UI allows you to do).
4. When you are done, simply restart the browser or logout and log back in to feedly to see all the changes you made reflected in feedly.

Note: versions of feedly older than 1.2.99 have a caching issue where it might take a day or so for the changes to be reflected. In version 1.2.99, the caching issue was addressed and you should see the changes reflected in real-time when you restart the browser.

Re-blogging… Thank you Jenny. I think I need a cookie now.

@boringo asked today:

The “Greatest” view (renamed to the “home” view in 1.2.95+) is feedly’s attempt at showcasing what are the “best” unread articles available in your feedly. The goal is to try to filter out the best content in case you only have a few minutes and do not have time to read everything.

The filtering is based on various parameters: is the source the article is coming from one of your favorite sources or not, how many recommendation does the article have, how old is the article, has this article been recommended by someone your follow directly, how many articles does the source publish per week, how many unread articles are they associated with this article and your personal reading and sharing patterns.

Although the specifics are opaque (and ever changing), as a user you can have a great influence on the filtering by marking sources as favorites (you can mark a source as favorite by clicking on the star next to the source title in the dashboard).

If you have specific questions or suggestions on how to improve the filtering, please let me know and I will forward the information to the dev team.

Hello. My name is Elisa. I am the new community manager for feedly. If you run into any problem, I am here to help. You can reach me on twitter (@elifeedly) or on getsatisfaction/feedly

Thanks to digg diggest, 聚笑之地, 小飞的足迹 and 自然卷, we now have chinese users. Welcome!

Update Dec 2nd: The problem related to the use of the Microsoft Yahei font has been identified and addressed as part of the 1.2.95 patch. Special thanks to Bo for his help in this process.

We are continuing to trend in the right direction: people read their feedly more often, read more articles and tweet and share more. The only metrics that is lagging behind is the number of annotations.

Next steps: Get feedly 2 out and work hard to get on the firefox recommended add-on list.

Special thanks to all the users who continuously provide us feedback and  help us improve the experience.

Special thanks for spreading the good word.

Hello. TechCrunch is organizing an event called the Crunchies. We have decided to throw our hat in and participate in the “Best Bootstrapped Startup”.

If you enjoy feedly and have 30 secondes, you can help by nominating feedly: Best Bootstrapped Startup

If you really like feedly, you can do it once a day every day between now and Dec 10th.

It is the first time we are doing something like this so I am not sure how far we will get but “you have to start somewhere”.

Thank you!

In preparation of feedly “iteration 2″ - which we will be released in December, we are focusing on removing as many quirks and improving stability and performance. Part of the results of this effort are included in patch 1.2.90.

Change Log

Optimized the “greatest” page both in terms of load time (30% faster) as well as the relevance of the initial set of recommendations.

Fixed set of issues related to the unread count getting out of sync if you have very few unread articles in our feedly.

Reduced memory footprint by 25% and network bandwidth by 35%.

See getsatisfaction for the list of other issues addressed.

(*many* thanks to Phillip Johnson and Orjan Lundberg for their contribution!)

Update: Nov 18, 6:45pm

We just pushed out 1.2.91 and 1.2.92 to address a regression and a hickup in the handshake between feedly and Google Auth which resulted in a feedly unavailable message. Sorry for the inconvenience.

Update: Nov 18, 9:00pm

One more patch (1.2.93). This time to address a problem with keyboard navigation and flickering.

Nov 10, 2008 at 13:45pm PST.
We melted our servers. Sorry for the inconvenience. We are working as fast as we can to get things back and and increase capacity. We will update this post as soon as we have more information.

Nov 10, 2008 at 14:30pm PST.
The service is back up. We are going to try to learn from it and avoid the same problem in the future.

After five month of listening, fire-fighting, iterating, the feedly stats are finally trending in the right direction. This feels really good. Special thanks to all the beta users who patiently provided us bug reports, feedback and suggestions and encouraged us during the process. Have a great week end!