If you are not aware, sportbots is a project that mirrors Twitter accounts from popular sport reporters, players and the leagues themselves. These bots are presented as regular ActivityPub actors, which means that they can be followed from Mastodon and any other AP service that is oriented towards microblogging.
With my work on Fediverser and the ActivityPub Toolkit, I'm realizing that we could do something similar for Lemmy. The Fediverser system could keep a database of these bots accounts and then map them to the relevant Lemmy instances/communities.
I'd like to get some opinions on how best to do this. Here are some of my ideas, in order of preference:
- Reach out to the developer behind sportbots.xyz and ask them to add this integration directly, to make sure that the bots post not just to Mastodon-like systems, but to groups as well.
Pros: it can be very straightforward. No new bots being created on the Fediverse.
Cons: the code seems to be closed, so we have to rely on the dev to implement this.
- Add the functionality to Fediverser to map mastodon/twitter/bluesky accounts to Lemmy mirror bots, and also map these accounts to the specific communities where they should be posting.
Pros: Accounts could be eventually be used by the real owner. Open source.
Cons: More bots in the Fediverse (not at alien.top scale, though). Not that many Lemmy admins seem interested in deploying Fediverser so far.
- Create a separate project from Fediverser that does what sportbots is doing, but focused on Lemmy.
Pros: most flexible. Could be easier for other people to run it if interested. I would be sure to open source it.
Cons: It's yet-another project that I would be taking on, and I don't have any more bandwidth for new projects unless they are guaranteed to bring some revenue.
Please, let's avoid any "who cares about sports?" or "I only want organic content here" type of discussion. We need content here if we want to get more people to stay active and if you don't care about sports or the bots, just feel free to block them.
What I am saying is that the ActivityPub protocol is inherently built towards a server-centric system, where identities are owned by the server. Go read the spec: even the "Client-to-Server" specification assumes that the server owns the keys and dictates that the client (i.e, users) must do everything through the API provided by the server (i.e, the client's outbox).
Anything that is built with a design where the client owns the keys may even be able to interoperate with ActivityPub, but is not ActivityPub.
It's the other way around. We shouldn't be looking for "Mastodon on ActivityPods", but "ActivityPods applications that can talk with Mastodon servers", and those do exist.