This is a convergence with other modules like UBlock Origin.

This makes me think that, "in theory", if you display social media buttons, this falls under the GDPR scope. Social Networks are collecting browser activity from both members and non members, when users visit site with these buttons. So, "in theory", you should obtain the explicit consent from visitors before displaying these social networks buttons. Or , you can build yourself these buttons, creating image, and using GET link to forward users to the appropriate pages if they want to tweet, like, share, etc...

Social media buttons are used for "profiling", by facebook, twitter et al and the profile data thus obtained is used ( amongst other things ) to target marketing..As such their use by websites ( via "inclusions, links etc directly to the social media sites which do the "profiling" ) is covered by the GDPR in various sections under "profiling"..If you search for the various uses of the word "profiling" in the text you'll find the relevant section ..Including those which state that the "natural persons" ( "website user or visitor" in this case ) must be notified when "profiling ( whether by the site directly or by the site facilitating profiling by third parties ) is in place..and be allowed to object to it..ie consent must be obtained ( consent may not be obtained by "scroll throughs" .."if you continue to use the site" , nor by "pre ticked "accept" buttons or their equivalent wording or methods )..it must be "explicit".

The definition of "profiling" from the text.
in Article 4

Definitions

(4)


‘profiling’ means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements;

‘profiling’ means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's.....personal preferences, interests, reliability, behaviour, location or movements

Pretty much covers ( slam dunk ) "social media" buttons..and any other tracking done by buttons, scripts, whatever by the site and or third parties buttons or scripts..

All buttons and tracking contravene GDPR..and you are not allowed to force acceptance..so you can only add them in if the visitor has been notified that you might, and they have explicitly agreed to be tracked by them..no theory..fact.

The text of the GDPR ( I referred to in the previous post ) is available here..
[eur-lex.europa.eu...]

Interesting to see where this goes. As webmasters and coders most of us here know what are those buttons for and their implications. I wonder how far this could go regarding privacy, data collection and telling the truth.

Talking about just one button, it says "Like".
Premise: allow the logged in user to Like the -item- with social and metrics useful consequences.

Reality, it's not about "Liking", it collects your data, creates a profile or profiles, useful for marketing (they don't care about who you are, they don't use it to tell if you are alive and well, it's to tune up ad campaigns and who knows what more), consumes bandwidth, etc, but basically there are scripts behind it (being logged in or not) that perform extra actions, far from the concept they sell, far from the premise. It's like people asking for a bit of sugar at your door but just wanting to walk in and get your stuff. It's not even as asking for a bit of sugar, they are offering it...

I'm aware about social media, links, traffic, etc. Used to have social buttons, last month I just removed them. Among the many reasons we all know I did it mainly due to bandwidth, making the websites slow and affecting user experience. Something as little as a Like button or alike has a big set of code behind. I encourage people to experiment with seeing what's behind, it's a lot. And no it's not just the code used to insert something, that code inserts a lot more of additional code.

Removed all those Share buttons when I pulled my business site off FB. Still have the G+ & FB share links on my personal site (mobile only) but I don't use their APIs, I host the code myself. I'll have to test with Adblock+ to see if it catches it.

Side note: NoScript has done this from the get go. And those who surf JS disabled, etc....

Why would any webmaster use the code from social media sites while knowing that they use it to spy on your visitors and you, providing them with all the information they need to get so big, taking your share away! In the past you could see the amount of likes/shares but the most social media sites has also stopped with giving that information.

I guess you shouldn't mindlessly paste code into your site, even if it comes from a "trusted" entity like a big social media network. In the end, you can always do most of those buttons and functionality yourself with a few lines of code...

They won't block my social media buttons because it's a single custom image with 3 buttons using an imagemap for just the basic URLs.

Maybe they're working on some way to block a URL in a page too though [snort].