Board Game Arena

That keeps it from rendering, but the tracking will still happen (except possibly for Safari users?)

Unless BGA gives us a way to opt out of putting it on the page, the only way to prevent facebook tracking via this iframe is to use a content blocker; I hear ublock origin is good, but i've never used it.

Vynce wrote: ↑24 April 2021, 03:31 That keeps it from rendering, but the tracking will still happen (except possibly for Safari users?)

Unless BGA gives us a way to opt out of putting it on the page, the only way to prevent facebook tracking via this iframe is to use a content blocker; I hear ublock origin is good, but i've never used it.

It's going to keep it from rendering.

Agreed. Get rid of it completely, BGA.

sourisdudesert wrote: ↑23 April 2021, 20:22

BobGod8 wrote: ↑23 April 2021, 19:36 Anyone have a CSS customization to make it go away yet? I can make it disappear with uBlock Origin by hiding it, but it doesn't persist, so at least the <div> element should be easy to identify and remove.

No need for that: we're going to change the way it is handled on next week.

thank you, looking forward to see it gone. It's been a rather unwelcome addition.

Just want to add my voice to those saying I don't like being tracked by Facebook.

sourisdudesert wrote: ↑22 April 2021, 17:38 This is a standard "Facebook sharing" button, like the one you can find on any other news article, blog article, including boardgaming news website (and including Board Game Geek).

If you ignore it, not info is sent to Facebook. So basically, you can just ignore it if you don't want it.

Presumably the script that runs for this button is hosted by Facebook and/or the image is? If so, the mere fact of running the script is giving information to Faceborg. So no, it is more than just a question of ignoring it. There are lots of people who dislike these buttons for exactly this reason.

I will note that the present implementation is broken in at least one respect. If you use a script/ad blocker that disallows loading of Faceborg scripts, you get a Javascript error instead of the button.

sourisdudesert wrote: ↑23 April 2021, 20:22

BobGod8 wrote: ↑23 April 2021, 19:36 Anyone have a CSS customization to make it go away yet? I can make it disappear with uBlock Origin by hiding it, but it doesn't persist, so at least the <div> element should be easy to identify and remove.

No need for that: we're going to change the way it is handled on next week.

So the facebook integration is still showing on the pages at the end of a game, but it has been hidden behind another button that says SHARE. Is that all necessary to hide the Facebook share button but still have facebook access the information on BGA? Why is facebook share needed ?

BobGod8 wrote: ↑23 April 2021, 22:28 Whatever, here's the fix for anyone curious:

.publishresult {
display:none!important;
}

Add to your advanced CSS preferences and the whole container block disappears. Enjoy!

Hello can you also share the code for stopping google tracking? great thanks!!

NoScript
It's easy to block FB tracking.
It's much much more difficult for g**gle, it prevents many site working...

lastwarningbeforeban wrote: ↑31 May 2021, 18:32

BobGod8 wrote: ↑23 April 2021, 22:28 Whatever, here's the fix for anyone curious:

.publishresult {
display:none!important;
}

Add to your advanced CSS preferences and the whole container block disappears. Enjoy!

Hello can you also share the code for stopping google tracking? great thanks!!

Er...can you point to which loaded element you want blocked? I can dig through the developer environment to identify it and then come up with CSS to block it on the page, but the previous posts are right, it just blocks it from being shown, not loaded. My largest objection is that it's ugly. Google will still track. Facebook is still tracking...though if you don't log in they get less useful results, so I'd encourage that. uBlock works, but I haven't set it up to block Facebook because I never log in to (or use) Facebook. But I imagine a rule that blocks *.facebook.co* would deal with most of it.