Tips on how to personalize your feedly

We are very excited to see feedly included in the Top 100 Tools for Learning list C4LPT has created. Education is a vertical that is very dear to our heart. We love to see teachers and students use feedly.

Share this:

Like this:

We are releasing 18.1 to the Android Beta channel while at the same time submitting the build for review to Apple.

Here is a detailed change log:

Fixed the iOS 5.1 startup crash.

Fixed paste issue in the Android search box

Fixed a infinite loading loop in the Home section.

Improved the contrast in the black theme.

Fixed a twitter sharing bug on Android.

Fixed an facebook sharing bug on the Kindle and Kindle Fire.

Fixed a bug where marking the all section partially as read was actually marking the entire feedly as read.

Fixed an image resize bug on rotation.

Fixed the gloss on the iOS 4 and iOS 5 icon.

Clarified Google+ vs Google OAuth login options.

Added black theme support to the un-clutter option.

18.1 will be available on the beta channel later tonight. We will promote it to production within the next couple of days if there are not P0 bugs reported against it.

18.1 will be available in the Apple Store within a week or so – as soon as it has been fully reviewed by Apple.

Update: Tuesday Jan 21, 2014 at 2:00pm PST. We promoted 18.1 to the production channel. You should be able to update the app within an hour or so.

Next? Once 18.1 is out, we are doing to start focusing on v19, which will be centered around Evernote integration, Pinterest integration, smooth scrolling in the list view, tagging and offline support for must reads, home and saved items.

Share this:

Like this:

We are getting reports that the new feedly 18 for iOS is crashing on the first generation iPad when running iOS 5.x. The team is at the office looking at the issue. We apologize to the users who are running into this issue. We are going to make sure that it is fixed in 18.1.

If there are other pressing issues you would like to see fixed in 18.1, please leave a comment and we will try to see what we can do.

Update: Sunday, Jan 19, 6:00pm PST – After 4 hours of debugging, we now understand the cause of this problem. The problem is not related to iPad. It is related to the fact that one of the libraries we use requires Dynamic Fonts and that feature is only available on iOS 6 and higher. We are going to fix it this evening and submit version 18.1 to Apple for review tonight or tomorrow.

Update: Monday, Jan 20, 6:00pm PST – We were able to fix the crash and a few other issues. 18.1 has been submitted to Apple for review. If there are no issues during the review, the app should be in the AppStore within 7 days.

We would like to introduce you to the new feedly URL shortener: feedly.com/e

We have been testing this feature for about 8 weeks. Collected feedback during that process and improved the experience.Here is a quick overview:

The feedly URL shortener shortens links.

The feedly URL shortener automatically redirect people to the publisher website – using an HTTP 302 redirect. We explored earlier on a feature which would optimize the rendering of the content based on the RSS content – some sites load still super slowly on mobile but there was a push back from some bloggers and we disabled that feature. Click on see: http://feedly.com/e/Viuh2Msb as an example.

The feedly URL shortener captures analytics about how people are engaging with the content you are sharing (how many people are clicking on the link, when, etc…). We will soon be offering a UI which will let you determine the karma you are building up via your sharing. We are also capturing this engagement information in the top stories recommendation which are shown in the feedly home page.

The feedly URL shortener also automatically generates facebook, twitter and Google+ metadata (title, summary, source, visual) for the articles you are sharing based on the data available in the RSS feed and the web page to make your sharing are visual and impactful as possible and draw as much engagement as possible.

The feedly URL shortener gives twitter mobile users the option to open the link in feedly. The goal is to allow feedly users who read your tweets to access the content in their feedly to be able to save and share it more effectively and help spread the word about feedly. This is a separate option from the main link which will also lead to the blogger/publisher who wrote the content. [Instead, we are going to reach out to bloggers and content creators and asked them to add “follow in feedly” buttons to their sites. Thanks to Matt Gemmell, Maarten den Braber for the feedback]

As a feedly user, you have the option to turn the shortener on/off (all users, not just pro users). In version 18.1, the preference will also be honored on feedly mobile. See http://feedly.com/#preferences for more information

We think that the analytics/karma part of this feature is going to be interesting and look forward to iteration 2 of this feature. Do not hesitate to ping us if you have questions and suggestions.

Have a great week.

/Edwin

Share this:

Like this:

Last week I gave a talk on Designing with your ears at the parisian startup incubators Le Camping and The Family. The goal of this talk is to give startups simple techniques to get feedback from their users or potential user while they are designing their services.

I always love feedback so if you have anything to share with me or any questions please leave a comment.

Like this:

As mentioned in the beta announcement, the main feature of this release is speed reading – a new tap gesture which allows power readers to quickly jump from one inlined article to the next:

Here is a summary of the other features and bug fixes we are releasing as part of the this request:

1) We redesigned the user experience on the Nexus 7 – focusing on speed and efficiency.

2) We fixed the back button bug reported by many users – where the app would sometimes require multiple back taps to exit.

3) We addressed the rendering bug reported by many Android 4.1 users. This was due to an optimization we put in place for Kitkat but did not play nice with Android 4.1. If you are a feedly + android 4.1 user, you should see fewer rendering issues.

4) We enhanced the login. We now offer a full Google+ login option (the red ‘Login with Google’ button) as well as the old Google OAuth button. The Google+ option comes with a safer Single Sign On implementation and a better sharing dialog. Your choice.

5) Fixed the login expiration bug.

6) Improved the speed of the image processing service. This was one of the key requirements to delivering the speed reading feature.

7) Added a new Mark All As Read card which includes some status about your reading session. More on this later this year.

8) Compatibility with the Samsung Galaxy Gear. More on this next week.

9) Removed the colors in the left selector. This is because we will soon allow users to assign colors to categories, making colors functional.

10) New enhanced black/night theme.

What are the next features we are exploring for feedly mobile 19?+ Tagging+ Evernote integration (pro)
+ Customizable font and font size
+ Ability to associate a color to each collections
+ Better search
+ Smooth scrolling for the title only view
+ Offline support for home, must reads and saved items
+ Notification support for must reads

This new update is centered around bug fixes (rendering on Android 4.1, back button issue, login expiration, etc.) and a new feature we call speed reading – a tap gesture which allows faster transition from one article to the next.

If you want to try this new authentication module and provide use feedback, please go to http://feedly.com/beta, log out and log back in. We worked hard with the Google team to make it seamless: No Google+ account required, no Google+ profile required and works in corporate environments which block Google+.

Let’s note that none of your feedly information (what you are following, what you are reading, what you are saving, what you are searching or anything else) is shared with Google or any other third party.

Next:

1. This sign in code is new so we are going to run it on the beta channel for a few days and make sure that there are no bugs preventing users from accessing their feedly. If there are no issues reported by the end of this week, we will promote 17.7 to the main channel over the week end.

2. We know that some users would like to use different sign-ins so we are working on a feedly login, a facebook login, a twitter login and a wordpress login. More on this in 2014.

3. Once this new google login module is completely deployed, we will be able to use incremental auth to allow the subset of feedly users who like Google+ to take advantage of some of the new cross device authentication and new sharing features the Google team has been working on. The beauty of incremental auth is that it allows some users to take advantage of those features without forcing the entire community to upgrade to Google+.

Thank you to Google for listening and offering both this new sign in module and incremental auth!

Share this:

Like this:

Buffer is a product and team we really love. Today they announced a new addition to the buffer family:Buffer for Business.

The goal of buffer for business is to help social media manager teams in larger organizations work more effectively. It includes support for more social accounts, more team members and approvals.

Buffer for business works seamlessly with feedly web, feedly iOS and feedly Android (both the pro and non more editions). You can use feedly to discover great content from the voices you trust around the topics that matter to you and use buffer for business to share that content at the right time across all your social media accounts (twitter, facebook, linkedin, google+ pages, etc..).

The buffer team is a great inspiration to us. We want to congratulate them on reaching this great milestone!

/Edwin

Share this:

Like this:

During the June-July period, we received a lot of requests from publishers to be able to more effectively track the direct and indirect traffic generated by feedly readers. To address that request, we added then a utm_source decoration to the title of the article – the link which leads users from feedly to the publisher’s site.

Today someone reported that adding the utm_source was interfering with information already encoded in the URL. At first we did not understand what they meant. After doing some research, it seems that the titles of some RSS feeds link directly to third party sites (and not the publishers’ sites) and in that case, utm_source is valuable information to be sent to that third party.

Even though this seems to happen for less than 0.0001% of all the articles we serve, it seems to be a valuable use case so we pushed out a new version of feedly which instead of replacing utm_source=feedly simply adds utm_reader=feedly.

This is going to impact negatively the publishers who are using utm_source to track their engagement in feedly but hopefully they can change their analytics to look for utm_reader instead of utm_source.

Also to be clear: feedly never touches any of the links that publishers embed in the content of their posts because those links often link to third party sites and some have affiliate or other type of sponsorships associated with them.

Update: The change has been rolled out to both the main channel and the beta channel.

Share this:

Like this:

We want to be able to listen to the feedback of the community on some of the new features we are working on before we roll them out in production. To help streamline this process, we have created a new version of feedly called the feedly beta channel and a new google+ community called feedly beta.

Share this:

Like this:

If you are trying to access your feedly and running into an empty account, it is most likely due to the fact that your session has expired and you are logged into the wrong Google account.

The solution to this problem is to log out of feedly, then go to http://www.google.com and add all your Google Accounts to the account switcher and then go back to http://feedly.com and login again. At that point, you will be prompted to pick an account, make sure that you pick the one you used when you initially created your feedly account.

Also, if you are trying to access feedly via an old bookmark pointing to http://feedly.com/home and getting a 404 error, please update the bookmark to http://feedly.com (no home or cloud needed anymore).

Happy thanksgiving to everyone!

/Edwin

Share this:

Like this:

All the feedly back end services are now running in our new data center. We can therefore merge cloud.feedly.com and feedly.com into the simpler feedly.com URL. The DNS change might take a few minutes to propagate.

If you have trouble access your feedly during that transition, please refresh http://feedly.com

Note: If you are using the feedly Fluid integration, please recreate the app with this new URL to make sure that you are not redirected out of the window.

This is a step towards making feedly a better web citizen by creating better and simpler URLs. More on that over the next 12 weeks.

Share this:

Like this:

We just release version 17.5 of feedly.com. Here is a short change log:

1) Must reads. The “must read” experiment we ran on mobile has been very successful so we are bringing it to the desktop. The idea behind must read is that we all have some feeds we do not want to miss. You can now promote them to must read. This will create a special must read category in your feedly and increase the probability that those feeds are featured in the home section. A lot of users have been asking for the ability to selectively turn on notifications (email, mobile, chrome extension) on must reads. We are working on that.

2) Gmail integration. Based on popular demand, we replaced the mailto: mail integration with a gmail module. More on this soon. [Update: we added a preference knob for people who prefer using a native mail client instead of GMail]

3) Smarter engagement counts. Arthur is working on simplifying the concept of engagement counts. In 17.5, we are making a step in that direction: engagement counts are now grayed out unless the number is abnormally high (compared to the average for that source), in which case they turn orange. In the next update, we will offer the opportunity to turn off engagement count.

4) feedly.com/e We are working on a new iteration of our URL shortener. One that will support twitter cards, facebook open graph and feedly connect and make sharing more effective. A lot more in this area soon.

5) Card view. We further cleaned up the card view. We are moving in general towards the direction where colors in feedly will be meaningful (green for call for action, blue for links, orange for engagement and saved, etc..) as opposed to pretty. You should see that philosophy apply to mobile and desktop over the next 12 weeks. Arthur will right a more detailed blog post about this.

6) Clean home. We simplified home to the minimum.

7) Beta channel. This is the last direct release we are performing on cloud.feedly.com. Going forward, we are going to open a beta channel where a community of beta testers can try changes and provide us feedback before we push the changes to the main channel. More on that change next week.

8) Customer satisfaction and roadmap. Remi has been working on a customer satisfaction/roam survey. It should start rolling out next week. We are curious to hear about the features and bugs you would like us to work on. Please be vocal.

Like this:

Share this:

Like this:

Sunday Nov 17th, 11:08am PST. The site is down. The dev and ops team are looking into it. More information in the next 20 minutes. Sorry for the inconvenience.

Sunday Nov 17th, 11:22am PST. We understand the problem. It is related to a timeout issue in our caching layer. We are looking at fixing the problem and bringing the system back up.

Sunday Nov 17th, 12:29pm PST. A new build is needed to protect the caching layer from a set of rogue requests coming from a third party client which seems to be suffering from some infinite loops. The dev team is working on the code change. More in 30 minutes.

Sunday Nov 17th, 1:27pm PST. We disabled the IP range of the rogue third party clients and restarted the app servers. The service should be back online now.

We learned a couple of lessons from this painful experience: 1) we are going to change the code to prevent this type of rogue requests to jam the cache and 2) we are going to better partition requests so that one third party client can not impact the quality of service for other clients (this is going to take a little bit of time).

Sorry for the inconvenience. Enjoy the rest of the week end.

/Seb, Oliv, David, Kireet, Michal and Edwin

Share this:

Like this:

Friday Nov 15th 2013, 10:55pm PST. As mentioned in our previous post. We need to take the service offline for 45 minutes to optimize HBase and upgrade a few pieces of software. We will update this post live over the next 60 minutes.

Share this:

Like this:

We just pushed out an update which polishes the title only view and the cards view.

People use the title-only view to crunch through lots of content as efficiently as possible. So we pulled out the engagement count into its own column to let you quickly identify the most engaging content published in your feedly.

The cards view, on the other hand, is useful when you want to glance through visual content and are looking for inspiration. So we simplified it so that visuals play a bigger role.

These are 2 of the 4 views you can assign to different sections of your feedly by clicking on the gear icon at the top right of each page and selecting the presentation option.

Do you take advantage of the different views? What is your favorite view and why?

/Edwin

Share this:

Like this:

A quick post to let you know that we will be taking feedly offline Friday, November 15th at 11:00pm PST to further tune HBase. The service will be down for about an hour. We will live update this post on Saturday to keep you up-to-date.

/Oliv

Share this:

Like this:

Saturday, Nov 9th, 16:00pm PST– OUTAGE – There has been a network error between one of our app servers and some of our data nodes. The ops and dev team are looking into it. We will update this post as soon as we have an ETA on the fix. Sorry for the inconvenience.

Saturday, Nov 9th, 17:30pm PST– FIXED – The service is back up. We will do a post mortem on Monday to understand why the redundancy mechanism we have in place did not work properly. We will publish more details then.

Saturday, Nov 9th, 18:45pm PST – START UPGRADE – It seems that part of the bug is due to an infinite splitting loop in HBase. This splitting bug has been fixed in a newer version of HBase so we are going to take the service down for 45 minutes and upgrade HBase to version 0.94.13.

Saturday, Nov 9th, 19:30pm PST – UPGRADE COMPLETE / LIVE – feedly is now running HBase 0.94.13. We can confirm that the Infinite splitting loop issue has been fixed in this newer version. Everything is be back to normal. Please restart the app on iOS and Android or reload cloud.feedly.com. Enjoy the rest of the week end.

Like this:

The fact that the change is forcing users to create a Google+ profile and that Google+ is not available in some companies and on some Google Apps domains outweighs the benefit of being about to login more seamlessly across devices (Android).

So we are going to rollback the Google+ login change later today.

We will try to see if there is an optional way to deliver the Google+ login benefits to people who like Google+ and Android.

We are still planning to offer more login options over the next 7 weeks.

[Update: The change has been rolled back: you can now go to http://cloud.feedly.com and login using the old Google Authentication mechanism. The main lesson we learned here is that user should control how they want to login to login to their feedly. We will make sure not to forget this. Have a good week end].

-Edwin

Share this:

Like this:

When we created feedly a few years ago, we made the decision to use Google OAuth as our authentication service. The goal was to let users safely login with their existing Google identity instead of having to create and manage yet another identify.

Google has been slowly transitioning from Google OAuth to Google+ as their unifying identity system. This transition opens the door to interesting opportunities like simpler login across devices – and a lot more.

We are following on Google’s lead and transitioning feedly from Google OAuth to Google+ login.

You will see this transition surface on cloud.feedly.com this week and on Android and iOS later this month.

This will also open the door to some interesting sharing features we have been working on – more on this in a couple of weeks.

We also understand that some people would prefer to have more identity choices. So we have been testing twitter, facebook and wordpress login options. We will be rolling them out over the next 7 weeks.

[Update 1: the fact that this changing is forcing users to create a Google+ profile and that Google+ is not available in some companies and on some Google Apps domains outweighs the benefit of being about to login more seamlessly across devices. So we are going to rollback this change later this afternoon – Friday 1:00pm PST. We will try to make it optional in the future for some users who like Google+. Thanks for the feedback].

[Update 2: The change has been rolled back: you can now go to http://cloud.feedly.com and login using the old Google Authentication mechanism. The main lesson we learned here is that user should control how they want to login to login to their feedly. We will make sure not to forget this. Have a good week end].

Share this:

Like this:

We just pushed out 17.4 to the cloud.feedly.com. Given that a lot of users have been asking for a change log, here is a quick overview of what’s new:

New “You might also like” Module

The feedly community is continuously discovering and organizing new feeds. We are now connected to more than 37 million sources of content. The purpose of the “You might also like” module is to help you discover new voices.

Exploring new designs for the home

In 17.3, we added a new feature which allows you to change the view of the home page to title only, magazine or cards. In 17.4, we are exploring a different design for the cards layout. This is a work in progress so feel free to provide feedback in the comments on what your dream home layout would be.

Lifetime pro edition

A few users have been requesting that we bring back a lifetime version of feedly Pro. The key motivation seems to be simpler payment and simpler expensing. So we are bringing back a Lifetime pro edition priced at $299. Learn more about feedly pro lifetime edition

Share this:

Like this:

Last week we pushed out a new version of feedly cloud which includes 3 new pro features and 3 new standard features. Here is a quick overview.

Speed Boost (pro). Overall, we optimized the polling speed of the feedly cloud so that all the feeds are refreshing about 30% faster than before. We also added a pro feature where feeds from smaller sites – those with fewer followers – are updated about 4x faster. The result is that feedly should load faster and feel even fresher than before.

Popular. Thanks to the engagement and sharing behavior from the community, we are getting a very clear signal of which articles are the most popular within each feed. We added a “Popular” section at the top of each feeds to make sure that you do not miss those articles. If you prefer a chronological view only, this feature can be turned off in the preferences via Preferences > General > Popular.

Custom Sharing (pro). There is now a preference option to allow you to define a custom send to URL. This allows you to send articles directly to the service or clipper of your choice. To configure this feature, go to Preferences > Sharing > Custom Sharing. Read more about Custom Sharing in this blog post.

Home Views. You can now change the view of your feedly home to title only, magazine or cards. This feature was first requested by David Pogue in his June review.

Pro Roadmap (pro). If you are a pro member, you can suggest new pro features and vote on them to prioritize development. See https://cloud.feedly.com/#pro once you have upgraded for more information.

Improved feed search. When you go to “+add content” and search for feeds by title, url or topic, the results are now powered by a brand new search engine. It should be a lot easier to find the and the right sources. We are continuously working and investing on improving searching for content in feedly and this is area will continue to evolve.

Article search. We have been working on scaling up the feedly cloud infrastructure and we are now able to return the first search result for article searches to all users. You can try searching your feedly feeds using the “search articles” box in the top right corner of feedly desktop. Full search in articles is a feature of feedly Pro, read more about Article Search in the feedly knowledge base.

Share this:

Like this:

We are sorry: it seems that some of the GPU rendering optimization we put in place for Android 4.1+ did not work well on Android 3.x and Android 4.0.x.

The dev team is looking at selectively turning off some of those optimization. We just pushed out a 17.1 update which does some of that and should address most of the rendering issues experienced by users who are running Android 3.0 and Android 4.0.3 and 4.0.4.

17.1 should be available onthe Google Play Store within 45 minutes. If you are using feedly on Android 3.x and Android 4.0.x, please update and confirm in the comments that the rendering problems are gone.

If 17.1 does not address your rendering issue, please leave a comment with your device name, Android version and if you know it the amount of GPU RAM your device has.

With your help, we should be able to selectively revert back all the optimization and make sure that the enhancements targeted at newer devices do not come at the cost of a penalty for other devices.

Special thanks to the Google Android and Google Chrome teams for their coaching.

Version 17 will be submitted to Apple for review on Friday and should be available in the app store shortly after.

If you run into a bug, please leave a comment and we will pass the feedback to the dev team.

Update (Wednesday morning): Some of the optimizations we performed for Android 4.1 and 4.3 seem to cause some issues on Android 2.x and 4.0. The dev team is looking this. We aim to have a fix out by Monday.

Share this:

Like this:

A lot of users have been asking us for knobs to simplify the share bar. We pushed an update last night which includes a set of preference options which allow you to customize which sharing icons should be visible and which sharing icons should be hidden.

Share this:

Like this:

As part of the latest release of feedly Desktop (v17.3.639), we are launching anew feedly Pro feature: Custom Sharing. It allows you to integrate your feedly with a variety of services to directly save or share articles.

Here below are some examples of what you can do with Custom Sharing in feedly.

Share this:

Like this:

Millions of users depend on their feedly for inspiration, information, and to feed their mind. But one size does not fit all. Individuals have different workflows, different habits, and different devices. In our efforts to evolve feedly from a product to a platform, we have therefore decided to open up the feedly API. Effective immediately, developers are welcome to deliver new applications, experiences, and innovations via the feedly cloud. We feel strongly that this will help to accelerate innovation and better serve our users.

We have been working with fifty developers over the past six months to design an API which is flexible enough to capture the needs of different classes of application (readers, vertical enterprise apps, dashboards, integration hubs, vertical communities), but simple enough that a single developer can build a great app in less than a week.

Developers are a passionate and imaginative lot. With the feedly cloud API now publicly available, we are looking forward to seeing applications and services that those of us at feedly could never have imagined. We will do our best to highlight some of these forthcoming apps on this blog in the coming months.

The feedly cloud API encapsulates not only data access to millions of feeds but also offers a powerful personalization graph. Categories, feeds, topics, tags, mixes, and more are higher-level concepts that allow users to easily define the slice of the Web they want to consume. The power of the feedly cloud is that users can perform this personalization once and access it across many apps. The same personalization graph can power an iPhone reader, a desktop reader, a phone dashboard application, an auto entertainment system, a profile in someone’s favorite fashion hub, or a profile in an enterprise marketing or purchasing app.

The feedly cloud API is the same API we use to build all applications, including article search and other feedly pro features.

Simply put, personalized content makes applications and user experience better. Feedly cloud is offering a simple yet powerful way to add content to existing applications or to design new ones.

Finally, a special thanks to all the developers that have helped us shape the feedly cloud API. You can find their creations at: http://www.feedly.com/apps.html

Share this:

Like this:

We spent 3 days investigating some of the performance issues reported recently on feedly on chrome. The result is in: The AddThis chrome extension makes loading feedly on Chrome very slow and delays the loading of feedly pages by 5 to 20 seconds, completely hanging the browser during that time.

The work around to this problem is simple: go to chrome://extensions and disable the AddThis extension.

We have sent an email to AddThis with the result of this research so hopefully they will take the time and fix this behavior: generating high CPU background behavior on every page without explicit user engagement is rogue behavior. Hopefully they will acknowledge and fix this.

Spread the word.

Have a great week end.

/Edwin

Update: Thanks to the AddThis team for the responsiveness. They have acknowledged the issue and are working on a fix. We will let you know as soon as the fix is out.

Share this:

Like this:

We are excited to announce that feedly pro is now generally available. For $5 per month or $45 per year, you can get access to the first batch of pro features: search, one-click Evernote integration, one-click Pocket integration, and premium customer support.

New pro features will be added regularly. The goal is to offer our most passionate users more productivity and make feedly sustainable in the long run.

This is an important milestone for feedly because a more sustainable company will lead to more innovation for users of both feedly pro and feedly standard.

We would like to once again thank the first 5,000 early feedly pro backers. The funds from that campaign helped us invest in the infrastructure and customer support needed to make feedly pro generally available. We also listened to your feedback and added one-click Pocket integration and brought HTTPS support to feedly standard.

Share this:

Like this:

We pushed this week a set of bug fixes and enhancements to cloud.feedly.com. Here is the change log.

FIXED> Better alpha sorting of feeds in the left navigation bar (lower case vs upper case)
FIXED> Remove video auto play for youtube and vimeo.
FIXED> More precise feed and category mark as read.
FIXED> Saved for later status on the list is not in sync with the action.
FIXED> New implementation of the engagement countFIXED> Caching the Evernote notebooksFIXED> Use lastEntryId instead of timestamp for the mark as read.
FIXED> HTTPS and youtube video URLs
FIXED> Better support for youtube in full article view
FIXED> Adjusted spacebar navigation (used to scroll by 110%)
FIXED> Improved OPML export
FIXED> Add a c keyboard shortcut which clips the post to a default “feedly notebook” in evernote.
FIXED> Seems you can’t access the rename or remove buttons if a category title is too long. When attempting to rename or remove, you are redirected to the category itself or begin dragging and dropping the category.
FIXED> Postfix in twitter is not working.
FIXED> Confirm mark as read when clicking on the number in the left navigation bar.
FIXED> Enhanced the chrome app and extensions so that it has an option to let the user select http or https
FIXED> Mark older than 1 day/1 week as readFIXED> Chrome scrolling is much smoother

Share this:

Like this:

Today, we are starting a new chapter in the feedly journey. We call it feedly pro. The goal is to offer our most passionate users more productivity and make feedly sustainable in the long run.

We are starting with 4 features: search in my feeds, one-click Evernote integration, premium support and HTTPS. We will be iterating and adding new features regularly.

The limited lifetime edition we released earlier today sold out in 8 hours. A big thank you to the first 5,000 backers. You are making this journey possible.

The funds from this early edition are going to help us acquire the hardware needed to open feedly pro to everyone. More on this in a couple of weeks. Thank you for your patience.

This is an important milestone for us because a more sustainable feedly means more innovation for both feedly pro and feedly standard users.

feedly pro sends a clear message that you are the customer and not the product: We are excited to have a business model centered around customer satisfaction and we are going to do everything we can to make sure that both standard and pro users are happy.

I would like to take a minute and thank the team for all the hard work they have poured into feedly over the last 120 days. We weathered a perfect storm and came out of it stronger.

/Edwin

Note: we heard the people who would like to see HTTPS be also part of the standard feedly offer. HTTPS will be the first feature to go free when the next batch of feedly pro is available. Thanks for the feedback.

Share this:

Like this:

We have been focusing the last 3 weeks on polishing some of the rough edges.

Here is a detailed change log:FIXED> Continued to add hardware to make both polling and accessing feedly faster
FIXED> Added a preference knob to enable an even more compact list view.
FIXED> Mark as read synchronization across devices.
FIXED> Login sessions will persist in feedly+fluid
FIXED> Feedly+fluid shows an unread count badge which refreshed every 10 minutes.
FIXED> Better font (easier to read and support for international characters)
FIXED> Better spacebar and shift+spacebar navigation support.FIXED> Authentication issue when logging into cloud.feedly.com from an iPad.FIXED> +Add content should set focus on the input elementFIXED> OPML import and export
FIXED> Synching of category orders between cloud and mobile.
FIXED> Shift+m and shift+a mark the current feed or category all as read.
FIXED> Better focus handling for space navigation
FIXED> Use the “a” keyboard shortcut to +add content.
FIXED> The “m” shortcut to mark as read in the list view.
FIXED> Offer direct twitter and facebook sharing in addition to buffer.

We are getting a lot of questions on twitter. Here are some answers:

1) When will the feedly mini toolbar be back?
Arthur is working on redesigning feedly mini into something more capable and less intrusive. The new feedly mini will be a key part of the coming v17 – scheduled for early fall.

2) When will the android widget be back?
We are re-implementing the android widget on top of the feedly cloud. It requires a couple of weeks of work. Not sure if we will be able to schedule it for v17 or if it will have to wait for v18.

If the bug is related to a feed not loading properly in feedly, please send an email to care@feedly.com with [feed] in the title and the feed URL in the body (please make sure that the feed URL is still valid).

If the bug is related to an invalid image being associated to an article, please send an email to care@feedly.com with [image] in the title, the feed URL and the article title.

If the bug is related to the feedly UI misbehaving, please send an email with [bug] in the title and description on how to reproduce the issue and /cc edwin@feedly.com

Share this:

Like this:

I am really impressed by the thoughtfulness and transparency of Ben Horowitz and the courage he proved during the Loudcloud to Opsware transformation! One of my favorite #entrepreneurship voices: http://bhorowitz.com/

Some of the interesting questions extracted from this conversation:

What is the one thing you believe in that no one else believes in? (via Peter Thiel)

What are some of the tough/courageous decisions you made over the last 12 months?

Does your company have the right communication architecture in place?

Are you able to zoom in and out to make sure that you have both the right game plan and the right execution plan?

Do you have a culture in place where employees can raise alerts when they see problems?

Share this:

Like this:

Good news: Feedly 16.1 is out. Please go to the App Store and upgrade to 16.1 and you should be able to login and access you feedly from your iPhone, iPad and iPod. No more over capacity message!

Special thanks to the Apple team for expediting the review. Special thanks for the feedly community for their patience and support over the last 8 days. This ends an incredible 100-day sprint! The storm is over. Blue sky ahead.

Like this:

We would like to apologize to all the feedly+iOS users who are not able to login because of the “Over Capacity/Login” bug. We hear your frustration. We do not have an ETA yet but the fix (version 16.1) was submitted 7 days ago so we are hopefully that it will be accepted by Apple soon.

This might also be a perfect time to try some of the new iOS applications which integrate with Feedly and see which one you like best:

We will report back as soon as v16.1 is available for download. Looking forward to seeing this issue resolved.

Like this:

Sorry. This is not a capacity issue but a bug! During the login, it tries to connect to Google Reader to help you migrate your feeds. Unfortunately, Google changed last night and is returning HTML instead of JSON and the feedly mobile client 16.0.522/530 has trouble digesting that, showing a error card instead[1] (note: if you are already logged in, you are safe as long as you are not logging out).

We fixed the problem in version 16.1. This new version has been already published to the Google Play store and the Amazon App Store – so please upgrade and you will be fine. This new version has also been submitted to Apple for review. It will take a few days for Apple to review it. We are very sorry for the inconvenience.

Work around? The third party apps are not suffering from this bug so If you are an iOS user, now might be the perfect time to try some of the new apps which integrate with feedly: Reeder, Newsify, Mr Reader and Byline

Like this:

The dev team has put together a new migration path which will help users who are missing feeds to re-build the feeds and categories by importing the subscriptions.xml file which is available in their Google Reader takeout archive.

Steps:
1. Go to http://cloud.feedly.com
2. Shift+reload to make sure that you are running the latest 16.0.548 version (The version is available at the bottom of the left selector).
3. Login if you are not already logged in.
4. Click on the Import OPML link available at the bottom of the left panel. This should load http://cloud.feedly.com/#cortex
5. Select your subscriptions.xml (which is available in your Google Reader Takeout).
6. Import – Note: if you have a lot of feeds, the import might take up to a few minutes. Please wait. If you get a 504 error, do not worry. Just wait a few more minutes and go to http://cloud.feedly.com and you should see all your feeds imported.

You should see all your feeds and categories get seeded into your feedly account. Note: This is not going to remove any feeds you already have into your account. Just add the additional feeds and categories.

We are here to help:
Sorry for the inconvenience. If you run into an issue during the import process, we are here to help. Please send an email to care@feedly.com with [import failed] in the title and some description of which of the 6 steps failed. If there are still feeds missing, it is possible that those feeds are dead/dormant or that feedly is having trouble fetching them. Please list the URL of those feeds in the email body.

/TheTeam

Share this:

Like this:

We discovered today that some of the feedly users were not successfully migrated to the feedly cloud. After a couple of hours of investigation, it seems that it was related to the feedly extension /app not correctly getting updated to version 16 and therefore not triggering the automatic migration.

We spent the rest of the day thinking about what we could do to fix this issue and deliver on our promise.

Given that all the feeds and categories information is available in the Google Reader takeout information, we decided to do a sprint and add a page to feedly what would take as input the subscription.xml file included in the Google Reader takeout and build the corresponding feedly. Our goal is to have that new migration option available in cloud.feedly.com tomorrow afternoon.