What about the users on mas.to who wanted to follow the bots? Why do they have to simply accept that they can not follow the solar bots because the admin is fussy about the local timeline?
If it was a remote instance they would not show up on the local feed, and only those bot someone local actually subscribed to would show up on the federated timeline. Hence it would be very unlikely that these bots would be have been banned by mas.to and thus their users would not have been effected at all.
alien.top if I remember correctly was way, way worse than 4 post an hour, so the comparison does not hold. And people can easily move to another instance that allows bot spam if they wish so.
But this entire argument is besides the point. alien.top did not abuse lemmy.world to publish their bots, so it can not be compared to the situation here.
As for those three points: that is not a “systematic failure” at all, but the system working as intended and defending itself against abuse. If people want to subscribe to bot spam they can start their own instance or register directly on alien.top.
db0@lemmy.dbzer0.com 1 week ago
Botsin.space existed for a long while and wasn’t widely defederated. Just saying…
rglullis@communick.news 1 week ago
Yeah, instead if closed down because it couldn’t support itself. What an amazing alternative you are proposing…
db0@lemmy.dbzer0.com 1 week ago
I wasn’t supporting an alternative. I was merely pointing the lie in your statement that having bots in one’s instance is grounds for massive defederation. Don’t try to divert.
rglullis@communick.news 1 week ago
There were plenty of instances that had botsin.space on automatic blocklist. On par with instances that block bird.makeup or any other Twitter mirrors.