Back in 2022, I wrote this rather grumpy post on Mastodon, the federated social media platform. @Edent@mastodon.socialTerence EdenMastodon enforces a "noreferrer" on all external links.I have mixed feelings about that.As a blogger, I want to see *where* visitors are coming from. I also like to see (and sometimes join in) with the conversations they're having.But, I get that people want privacy and don't want to "leak" where they're visiting from.Is it such a bad thing to tell a website "I was…
That doesn’t sound good? They are privacy invasive.
FWIW they should be configurable in your browser, either directly or with a plug-in.
The post makes a pretty reasonable argument as to why it’s a good idea.
Yeah, browser vendors think the same thing, since they are part of the commercial web. Anyway, at minimum, sending referer should be opt-in rather than opt-out.
According to ths post it will be opt-in, on the instance side.
So smaller instances where there-might be risks associated will be opted out by default, while large instances that might want the attention and where individual users stand out less can opt in.
It’s the instance admins’ decision whether they want it or not.
Talk to your admins or move to another instance if you disagree with them
I’m not personally affected since I don’t use Mastodon. That doesn’t make it a good idea.
I guess it depends on what you want. If you want to be totally anonymous on the internet, then it’s a bad idea. If you want people to use Mastodon, then it’s probably an OK one, since the way people use microblogging is to follow famous people, and famous people aren’t using Mastodon unless there’s evidence that there’s an audience there for them to play to.
It’s less a matter of anonymity as wanting to maintain some basic privacy. If you want to tell someone where you learned about something, that’s great, go ahead and tell them. To have them extract the info from you without your knowledge is dystopian. Referers should have been banned as soon as the web became commercial.
Having info “65 people visit this site from Lemmy.world” doesn’t seem to be that invasive tho.
I can see blogger and other creator utilize this to connect with community.
The referer header tells the site which specific users and which specific clicks came from lemmy world. That’s flat-out invasive. Revealing the number of users (as Mozilla wants to do) is also invasive even if it doesn’t single out the user (of course that’s much less direct and people usually tolerate it until they become attuned to the issue).
The thing to ask yourself when site X wants information Y is “what does X want to do with the information?”. If the answer can possibly be “something bad”, then X should not get the information unless the user opts into sending it. That is even if it’s statistical or aggregated information. Being included in the count is like casting a vote for X, which (as we see with Trump getting elected) can have significant effects even with no identification of the individual voters.
I see. At least making them optional is good, especially for political context.
For creator related stuff, I can see instance like Misskey.design community benefitting from this tracker.
Unfortunatly its a cost we must accept since the justification makes it worth it.
That’s for the user to decide. The devs should not presume to make it on the users’ behalf.
Is that not how this is already being implemented?
It’s not entirely clear, but it appears to be up to the instance operator.
This is not a democracy
Better ask whose benefit the system is being run for in that case. If I want a system run by Elon Musk then I already know where to find one.