3 ms·

I'm not a big fan of hiding my traffic from youtube, twitter, medium et al by sending all my traffic to https://farside.link https://farside.link. I use https:

by rakoo 4y ago

I'm not a big fan of hiding my traffic from youtube, twitter, medium et al by sending all my traffic to https://farside.link https://farside.link. I use https://addons.mozilla.org/fr/firefox/addon/libredirect/ https://addons.mozilla.org/fr/firefox/addon/libredirect/ , which does the same but only in the browser, allows me to use other instances (such as my personal one) and has a button to switch instance if one doesn't work.

OJFord 4y ago
Both of these need to 'access [my] data for all websites' - I suppose I'm not really sure what my 'data' amounts to, (it sounds like anything I might input?) but surely they only need the URL, is that really as fine-grained as Firefox allows?
- noirscape 4y ago
  It's a really generic warning unfortunately (something which Mozilla admitted back in 2018, the warning is mostly "technically" accurate rather than literally so). Basically enabling almost anything in the WebExtensions API related to actually loading in webpages will cause Firefox to start displaying that message if I recall. What it means is that the browser is loading in extra javascript before the page has fully loaded. Basically unless you're making some extremely niche & domain specific extension (that is unrelated to page content), it ends up in that popup message.
- rakoo 4y ago
  Libredirect, the extension, needs access to my data but it remains in the extension. Farside, as I understand it, sends clicks to https://farside.link https://farside.link, which will redirect to the appropriate proxy with the full URL including the path. I can't really tell because the source code of the extension isn't linked. This behaviour can only be acceptable if I set the extension to query an instance I trust (my own, for example), but at this point it's just easier to do everything in the extension itself.
- dredmorbius 4y ago
  I share your distrust. As a conversation here a couple of months back revealed, the problem is rather thorny, once an extension has the capacity to modify page content, virtually anything is technically out of the bag: <https://news.ycombinator.com/item?id=33726116 https://news.ycombinator.com/item?id=33726116>

by rakoo 4y ago

OJFord 4y ago

Both of these need to 'access [my] data for all websites' - I suppose I'm not really sure what my 'data' amounts to, (it sounds like anything I might input?) but surely they only need the URL, is that really as fine-grained as Firefox allows?

noirscape 4y ago
It's a really generic warning unfortunately (something which Mozilla admitted back in 2018, the warning is mostly "technically" accurate rather than literally so). Basically enabling almost anything in the WebExtensions API related to actually loading in webpages will cause Firefox to start displaying that message if I recall. What it means is that the browser is loading in extra javascript before the page has fully loaded. Basically unless you're making some extremely niche & domain specific extension (that is unrelated to page content), it ends up in that popup message.
rakoo 4y ago
Libredirect, the extension, needs access to my data but it remains in the extension. Farside, as I understand it, sends clicks to https://farside.link https://farside.link, which will redirect to the appropriate proxy with the full URL including the path. I can't really tell because the source code of the extension isn't linked. This behaviour can only be acceptable if I set the extension to query an instance I trust (my own, for example), but at this point it's just easier to do everything in the extension itself.
dredmorbius 4y ago
I share your distrust. As a conversation here a couple of months back revealed, the problem is rather thorny, once an extension has the capacity to modify page content, virtually anything is technically out of the bag: <https://news.ycombinator.com/item?id=33726116 https://news.ycombinator.com/item?id=33726116>