[arrrg]

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.

[siddboots]

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.

[briandear]

Let's tell Heroku to stop charging for the SSL endpoint.

[thisishugo]

There are plenty of reasons to prefer secure browsing by default. Perhaps I subscribe to feeds that would be flagged as "suspect" by programs like PRISM[1] and XKeyscore[2], and would like to make the NSA work at least a little bit to find that out.

[1] http://en.wikipedia.org/wiki/PRISM [2] http://en.wikipedia.org/wiki/XKeyscore

[pionar]

So, then if it's that important to you, give the people giving you the cover of HTTPS some money, stop being a cheapskate.

[thisishugo]

It so happens that I consider HTTPS by default for all users a requirement. A problem which a pro subscription does not solve.

[deong]

And you can pay for that feature. I have no real stake in the game here, but I'm failing to see why that is a must-have feature for every user of the service.

[thisishugo]

Feasibly, the lack of HTTPS for a subset of users could be used as an attack vector against Feedly, which could surface information about me that I do not want revealed even if I were a Pro user using HTTPS.

[cenhyperion]

Security shouldn't be a premium.

[arrrg]

Huh? Isn’t this about privacy, not security?