I would rather pay a monthly/yearly fee.
"feedly pro will be generally available this fall for $5 per month (or $45 per year)."
51–60 of 68 posts
I would rather pay a monthly/yearly fee.
"feedly pro will be generally available this fall for $5 per month (or $45 per year)."
Earlier quoted context omitted.
Only 5,000 lifetime accounts. Tiny in comparison to the 12 million+ users they have. http://thenextweb.com/insider/2013/06/19/feedly-launches-sta...
Will they even last 20 months at which point lifetime account becomes advantageous? The Old Reader sure didn't.
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.
FWIW, I'm a big fan of Feedly, and have upgraded to Pro.
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.
Personally, think we should encourage an ecosystem where https is a given, rather than feature. I would prefer that companies saw this as part-and-parcel with being a responsible service provider. FWIW, I'm a big fan of Feedly, and have upgraded to Pro.
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 )
> Will extend it to everyone when we have a way to fund it. Is it really that expensive for them to run? Last time I heard it was a a minuscule amount per request, and peanuts for the certificate itself.
Earlier quoted context omitted.
> Will extend it to everyone when we have a way to fund it. Is it really that expensive for them to run? Last time I heard it was a a minuscule amount per request, and peanuts for the certificate itself.
Does $5/month sound a lot for a product/service from a real business? How much do you charge for your product/service?
Since Google Reader went down, I've found I waste less time. I used to use Reeder as my front-end, but they've been slow to update their desktop app. I realize I'm "missing" things I used to keep up to date on, but the net gain is a lot more time I used to spend consuming what I suppose was superfluous content. For me - it's been kind of a nice change.
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.
Don't want the NSA reading my I can haz cheezburger feed