Page 1 of 1

visually identify feeds not using HTTPS

Posted: 11 Apr 2016, 14:29
by tls
Hello,

I would like to suggest a feature where in the feeds list under preferences there is a way to visually identify the feeds you are subscribed to that does not use HTTPS

example

Code: Select all

Feeds
 + Group
    +  Feed1 
    +  Feed2 (http)
 + Group 2
   + Feed4 (http)
   


Another example of this would be how ublock identifies its 3rd party filters that use "http"


I think this would be a useful feature so people can easily make sure their feeds are served over https instead of http and so improving their privacy. having the "http" identifier would make it easy for someone to go though their feed and check if those sites are also available over HTTPS and if so manually update the feed instead of having to click every single feed to see if it is http or https already

Thank you for listening.

Re: visually identify feeds not using HTTPS

Posted: 11 Apr 2016, 14:42
by fox
yes lets perpetuate the whole https == security or w/e myth by adding horrible UI bloat

no

Re: visually identify feeds not using HTTPS

Posted: 11 Apr 2016, 14:46
by tls
How is it a myth?

Re: visually identify feeds not using HTTPS

Posted: 11 Apr 2016, 15:12
by fox
this really isn't a forum for this discussion

suffice to say the whole user conditioning browser vendors are forcing atm with http being RED AND BAD is p dumb if you think about it for a minute or so and i'm not going to perpetuate it

nobody is going to MITM your furry porn feed, it doesn't matter, get over it

e:

>having the "http" identifier would make it easy for someone to go though their feed and check if those sites are also available over HTTPS and if so manually update the feed instead of having to click every single feed to see if it is http or https already

this is literally 1 babby's first SQL query

Re: visually identify feeds not using HTTPS

Posted: 11 Apr 2016, 15:39
by tls
well thanks for being an ass about it from the get go instead of just you know politely saying no.and giving valid reasons why it's not a good fit for the project

Re: visually identify feeds not using HTTPS

Posted: 12 Apr 2016, 00:50
by sleeper_service
tls wrote:well thanks for being an ass about it from the get go instead of just you know politely saying no.and giving valid reasons why it's not a good fit for the project


it's obvious that you're both new, and stupid, here... but fear not, that won't gain you any slack for your poor judgment and bad behavior...

run along now, and take your stupid ideas and butthurtness with you... buhby now.

furry porn feed.. *snicker*