@dalias I feel that a bit of a stretch / bad faith reading of things. Web 'refer' headers have existed for a long time and while they have been curbed in scope (some contexts don't send it at all, some don't send the URL path), it feels a bit extreme to compare this to experimentation on human subjects when if anything the current default was out of the norm
@dalias There is nuance here though? _some_ (obviously not you I suppose?) fedi users would like there to be better integrations with publishers (for example, I would prefer that the BBC have their own bots rather than RSS re-publishers), but ️🌈️we live in a society🌈 where you do need to justify doing work, stats help that, and I don't really see a issue if I click a link on mastodon dot social, the BBC knowing that I came from anywhere on mastodon dot social, as @Edent said, there are nuances where you would not want something like that, but generic servers I don't really see the harm, and it does good for a ecosystem (aka, people typically like nice things, this is one of the ways you get nice things)
I just dont understand the threat model of letting the BBC know I came via mastodon.social
@jeff I have a CRS317-1G-16S+ in production for bgp.tools in the NL as a low power "port expander", it's fine, it's just tagging VLANs and it's been fine, I however have hit weird shit ™️ with 'tik's OSPF/BGP and a bunch of the other Layer 3 stuff.
Tik is likely fine if your entire estate is tik (a lot of WISPs fall into this class) but it can be dicey otherwise. But the less things you are doing the better it all tends to go
(edit: woops, I didnt mean to boost you, but it seems I cannot un-boost now, my apologies)