Skip to main content


What's up with mastodon.social instance @Gargron?
Yesterday it was cdn.concert.io and today it's admanager.concert.io.

There is absolutely no explanation over why they are integrated with the instance. Once again thanks to #TrackerControl which exposed these integrations.

It's time to ditch the mastoson.social instance.

#Fediverse #Ads #Tracking #AdsInMastodonSocial

in reply to Prasanna | பிரசன்னா ⁂

I don’t recognize these domains. There is also no mechanism by which our server, through the API, could make your app connect to these domains. The only circumstance is if you click on an embedded video player, like YouTube, within a post, which would open a web page we do not control, such as YouTube; or if the app itself integrates with these domains. By all means, inspect the traffic from our server to your device.
in reply to Eugen Rochko

hey, thanks for the clarification. I found the reason why it happens. It appears that mastodon.social and concert.io are depending upon fastly.net for CDN services and hence there is an overlap of IP address which #TrackerControl identifies as an outgoing request to the Advertising portal concert.io.

Apologies for the trouble @Gargron. I will take this as an issue with #TrackerControl to see what can be done.

Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.