4 ms·

I wish all website would wait for the user to turn on social features before offering them. I'm not interested in any of them, the scripts shouldn't be loaded f

I wish all website would wait for the user to turn on social features before offering them. I'm not interested in any of them, the scripts shouldn't be loaded for nothing. Take a look at this way to do it: http://panzi.github.io/SocialSharePrivacy/ http://panzi.github.io/SocialSharePrivacy/

em3rgent0rdr 10y ago
that looks great! I like how the buttons are originally grey, which is a clear visual indicator that they are not enabled.
__derek__ 10y ago
Agreed. I use PrivacyBadger[1] to block the download of assets from third-party domains. That way I can selectively enable anything that I want from the blocked domains. [1]: https://www.eff.org/privacybadger https://www.eff.org/privacybadger
dylanfw 10y ago
Bruce Schneier's security blog implements something like this, providing an on/off switch for each social network's "Like", "+1", etc. https://www.schneier.com/ https://www.schneier.com/
- reitanqild 10y ago
  h-online used to do something like this as well.
WA 10y ago
Heise now uses a new tool they developed called Shariff. Looks better imho and is easy to use. It also shows a like counter if you proxy requests to FB's Graph API through your server. https://github.com/heiseonline/shariff https://github.com/heiseonline/shariff Would recommend this over their old two click social share. Your link is a fork of the old Heise tool. It looks dated on mobile.
K0nserv 10y ago
As a user I use uBlock Origin to block all 3rd party JS by default. This protects me from loading ads, social widgets(trackers), and trackers. A lot of the web is completely broken when you don't run 3rd party JS so each site requires a bit of whitelisting before it will function correctly. As a website owner I try to lead by example by not including any 3rd party JS(or any JS at all for that matter). Specifically avoiding trackers from Google or Facebook.
- gorhill 10y ago
  Even without going as far as blocking all 3rd-party js/frames (which I do personally), one can use the dynamic filtering pane to at least block the most ubiquitous domain names and allow only on a per-need basis. I do use facebook.* in one of my tutorial about reducing privacy exposure[1], but of course this applies to any ubiquitous 3rd-party servers out there (of which Disqus qualifies in my opinion, same for Gravatar, etc.) This approach will minimally break the pages with nice benefits in return: reducing the ability of ubiquitous 3rd-parties to profile browsing history, faster page load. [1] https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-to-easily-reduce-privacy-exposure https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-to...
SkyMarshal 10y ago
Use ScriptSafe, Ublock, Privacy Badger, Ghostery or any number of script blockers to block 3rd party scripts.

em3rgent0rdr 10y ago

that looks great! I like how the buttons are originally grey, which is a clear visual indicator that they are not enabled.

__derek__ 10y ago

Agreed. I use PrivacyBadger[1] to block the download of assets from third-party domains. That way I can selectively enable anything that I want from the blocked domains. [1]: https://www.eff.org/privacybadger https://www.eff.org/privacybadger

dylanfw 10y ago

Bruce Schneier's security blog implements something like this, providing an on/off switch for each social network's "Like", "+1", etc. https://www.schneier.com/ https://www.schneier.com/

reitanqild 10y ago
h-online used to do something like this as well.

WA 10y ago

Heise now uses a new tool they developed called Shariff. Looks better imho and is easy to use. It also shows a like counter if you proxy requests to FB's Graph API through your server. https://github.com/heiseonline/shariff https://github.com/heiseonline/shariff Would recommend this over their old two click social share. Your link is a fork of the old Heise tool. It looks dated on mobile.

K0nserv 10y ago

As a user I use uBlock Origin to block all 3rd party JS by default. This protects me from loading ads, social widgets(trackers), and trackers. A lot of the web is completely broken when you don't run 3rd party JS so each site requires a bit of whitelisting before it will function correctly. As a website owner I try to lead by example by not including any 3rd party JS(or any JS at all for that matter). Specifically avoiding trackers from Google or Facebook.

gorhill 10y ago
Even without going as far as blocking all 3rd-party js/frames (which I do personally), one can use the dynamic filtering pane to at least block the most ubiquitous domain names and allow only on a per-need basis. I do use facebook.* in one of my tutorial about reducing privacy exposure[1], but of course this applies to any ubiquitous 3rd-party servers out there (of which Disqus qualifies in my opinion, same for Gravatar, etc.) This approach will minimally break the pages with nice benefits in return: reducing the ability of ubiquitous 3rd-parties to profile browsing history, faster page load. [1] https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-to-easily-reduce-privacy-exposure https://github.com/gorhill/uBlock/wiki/Dynamic-filtering:-to...

SkyMarshal 10y ago

Use ScriptSafe, Ublock, Privacy Badger, Ghostery or any number of script blockers to block 3rd party scripts.