61–68 of 68 posts
Great that they've settled on a business model, but I feel like if you are going to have a free tier that HTTPS should be part of it.
Why exactly is that? By far most people do not care at all that other people are (theoretically) able to see what they are reading. I certainly don’t at all. I do not think HTTPS is in any way a required feature for a feedreader. It’s pretty perfect as a premium feature.
Honest question: why do people pay for "pro" RSS services? There are enough out there that I don't feel I would ever need to - I was using oldreader until they shut it down to everyone and now use digg reader - is there specific functionality I'm missing out on by not using these premium services? There's always the whole adage of if it's free then you could lose it, but with the amount of readers out there it seems…
Because it would be nice to not have to periodically have to re-learn everything as the app you're familiar with dies and you have to switch to an unfamiliar one?
Because good software is worth something?
Earlier quoted context omitted.
Why exactly is that? By far most people do not care at all that other people are (theoretically) able to see what they are reading. I certainly don’t at all. I do not think HTTPS is in any way a required feature for a feedreader. It’s pretty perfect as a premium feature.
Security shouldn't be a premium.
Earlier quoted context omitted.
Seriously. You shouldn't have to pay to expect a reasonable amount of security as a user.
Security? Where do you see security issues outside of login data (which is already over HTTPS)? This seems like a privacy feature (something not necessarily everyone cares about when it comes to their feedreading), not security.
And as someone else mentioned, the session cookie is still transmitted in plaintext, which effectively compromises your Feedly account.
If anyone working for feedly reads this: SSL/https should not be a premium feature. Please make it available to everyone. Update: they tweeted "HTTPS is currently a pro only feature. Will extend it to everyone when we have a way to fund it." (see https://twitter.com/feedly/status/364292745487065088 )
Earlier quoted context omitted.
Shut down the free service and no one will get hooked to your product, and choose a another free service to start with, and maybe even pay for it later. Providing both free and payed tier is the way to go, especially in the commodity market segment like RSS readers, unless you are in a niche without too much competition.
I disagree. RSS readers have a significant long tail expense per user. I worked at Bloglines. Pretty much every one of those free users have extra little RSS feeds that nobody else subscribes to that you have to crawl, handle invalid rss/xml for, update and keep unread status on. At scale, that is the most expensive part of operating an RSS reader, and it's not worth it.
Earlier quoted context omitted.
Security? Where do you see security issues outside of login data (which is already over HTTPS)? This seems like a privacy feature (something not necessarily everyone cares about when it comes to their feedreading), not security.
Any site viewed over plain HTTP is susceptible to content injection by ISPs, public wifi providers, employers, etc, basically anyone between you and the server. At best it's annoying, at worst it's a security hazard. And as someone else mentioned, the session cookie is still transmitted in plaintext, which effectively compromises your Feedly account.
If anyone working for feedly reads this: SSL/https should not be a premium feature. Please make it available to everyone. Update: they tweeted "HTTPS is currently a pro only feature. Will extend it to everyone when we have a way to fund it." (see https://twitter.com/feedly/status/364292745487065088 )
Seriously. You shouldn't have to pay to expect a reasonable amount of security as a user.