There is a new setting for server operators in #Mastodon 4.4, under Administration -> Server Settings -> Discovery, called "Allow external sites to see your Mastodon server as a traffic source". If you're running a server for a larger group of people there is no privacy downside to enabling this, and it will help make the fediverse more visible as a traffic source to the rest of the web.
@dev_ric By default, Mastodon tells the browser not to send a referrer header when users navigate away to other websites. This allows the server's hostname to be sent.
@ThaMunsta Some website owners may see e.g. nervesocket.com in their traffic logs and if they check it out it may identify you if you're its only user. If you don't mind this, there is no downside.
@Gargron Will this enable analysts to group all Mastodon domains together as ’Mastodon’ traffic source, or as social network ‘Mastodon’? Or will every server still show up as its own unique traffic source?
At work we are looking at ways to make Mastodon visible, but its distributed nature makes that hard right now.
When will the native apps adopt this? Unlike web apps, Android apps can set their own referer when opening links.
For example, the official app could attribute its navigations to a fixed referer like mastodon.social or joinmastodon.org/apps regardless of which instance the user is logged into.
Hi @gargron this is really concerning me. Feels like, this is a start of enabling content creators to make business here and Mastodon can be misused for commercial purposes by websites. I'm irritated, that we get a flood of toots, that advertise and suggest to enable this feature, without technical reference. Searching for it, does not really lead to an Blog or specification with technical background, I only find https://www.fediscovery.org/ but here we have server-to-server communication, right? "to see your Mastodon server as a traffic source" to me could be multiple things: URLs are passed through Mastodon instances; users lose control or personal web browsers do magic; users must disable this on their own or URLs are transformed when being published, users have workarounds by copy'n'paste