Conversation
Notices
-
@rugk ["Also if privacy issues are caused by websites..."] which, if your are talking about http referrer, is wrong. It's caused by your browser, which follows www agreements which don't take privacy into consideration. GNUsocial can't protect you from it. GNUsocial can't protect you from your ISP knowing you are visiting GNUsocial neither.
GNUsocial protects your privacy where you have absolute no control: not sharing your data with 3rd parties, not feeding logs into analytics services, not leaking your private data with external APIs and making the website fully functional if you configure your browser with privacy in mind.
Of course, those headers are nice additions but you can't sorely rely on them as a replacement for a properly privacy oriented browser.
As for youtube, most nodes store themselves the preview picture so no leakage until played.
-
@rugk HTML has nothing to do with http referrer leakage. As for Youtube & the users:
- Most don't care
- Most who care already took measures browser side
- Those who care and didn't, are comfortable as it is now
- Those who care but no B no C will at least read the FAQ, you can place a warning there
- No one wants popups (even less on mobile), nor an additional click as the price to pay to protect that ultraexceptcional case not covered above
-
@rugk http://www.technipages.com/firefox-enable-disable-referrer
This still applies https://quitter.im/notice/746476
-
@rugk as I said placing Referrer-Policy and/or CSP headers is enough and easy to implement. But no one should consider GNUsocial as a privacy heaven by itself
Kermit Unchained
All Bobinas P4G content and data are available under the