@seldo you personally or some app account?
(Note that this kind of stuff is not well liked here on mastodon, I got browbeaten into shutting down just a search engine that worked that way, let alone exfiltrate a timeline into an LLM provider)
@aurynn from looking at it, seems that'd be pretty hard. It's authing using tokens into the users fedi account, and then pulling the feed from there rather than reaching out to our servers... as a result you'd only see the UA if a member of your server was using it - which seems unlikely... pretty crappy of them to do that.
Edit: What I also do not see mentioned on the site at all is that this can and will be able to see DM's if you auth with it.
@aurynn @seldo @janl The code is at https://github.com/seldo/zeitgeist.
It does not set a user agent when doing a `fetch()` so it'll just be the default that node has which is probably `node-fetch`.
@aurynn @seldo @janl Surprise! "Just a Mastodon client", so he doesn't set one, I imagine it'll just use the default Next.js user-agent header: https://github.com/search?q=repo%3Aseldo%2Fzeitgeist%20headers%3A&type=code
It looks like it uses 'Zeigeist' as a client name when OAuth'ing, but that would only let you block its use on servers you control - people who follow you on other servers (or who you've DM'ed who use it 😬) still have full access to your posts:
https://github.com/seldo/zeitgeist/blob/2cb6c49581c51161f82e6c94804419609aad7c30/app/api/mastodon/auth/route.ts#L25
@neoluddite @seldo @janl Well, we'll do a PR for it.
Ideally, if we get a sufficient quantity of admins on board with blocking the UA, we can stop the spread of this kind of insipid techbro slopmongering.