louis ,
@louis@emacs.ch avatar

The Mastodon developers started to implement telemetry for everything you search for: Posts, Accounts, Tags

https://github.com/glitch-soc/mastodon/commit/acc77c3836974473e7c6a423cbd1138479ae197a

I'm not so sure if I like what I see in this commit. But we all knew it would be coming eventually.

So important that we build Mastodon-compatible server alternatives.

BeAware ,
@BeAware@social.beaware.live avatar

@louis I thought this already exists...😳

fbievan ,
@fbievan@alpha.polymaths.social avatar
fbievan ,
@fbievan@alpha.polymaths.social avatar

@BeAware @louis

This seems to be mainly about logging

https://tech.lgbt/@becomethewaifu/112525684774147445

In the original PR, they said why it was done.

https://github.com/mastodon/mastodon/pull/30350

I dont get what the author is doing tbh.

ross ,
@ross@rossabaker.com avatar

@louis I don't think this is recording anything identifiable about the search. Just timings, counts, etc. See https://github.com/mastodon/mastodon/pull/30350.

Furthermore, Otel doesn't by itself share anything with third parties. It's quite common to pipe it into a local monitoring solution. This data can be invaluable for keeping a service running.

This could be extended and configured for evil, but looks useful as it stands.

becomethewaifu ,
@becomethewaifu@tech.lgbt avatar

@louis FYI, this isn't implementing "traditional" telemetry at all. It's simply adding more granular logging to the instance itself, so they can track down which search terms take longer. It's not generating any 'extra' requests, or reporting anything to .social (unless you're on .social, of course) or even reporting client-side behaviors. It's just a fancy way of adding logic akin to print(account, searchTerm, requestDuration) to the search endpoint, which any admin can already do easily if they wanted that info.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • test
  • worldmews
  • mews
  • All magazines