How many of these bots existed on Twitter and were used to illustrate the point that the API being open was important to have a thriving ecosystem?
But this is not even why I am calling out the parent. I just find it ridiculous that OP brings a whole list of more-than-reasonable issues with Mastodon (and by extension the Fediverse):
- Federation does not work (Federation is wrong structure for decentralized social media)
- Account migration does not work (Coupling of identity to server)
- Direct messaging does not work (Messages are not really private, and Mastodon pretends to make them so)
- Content moderation does not work (Relates to #1)
- **Live feeds do not work **(Much like “browsing by all” in Lemmy, it’s a really bad execution to try to solve the issue of content discovery)
- Mastodon development does not work (Slow, opinionated on the “wrong” things, failing to respond to user’s requests)
- Mastodon culture does not work (The stereotypical user is just anti-everything, most instances are full of school-hall monitors, reject anything that resembles mainstream and end up becoming incredibly reactionary, boring people cross-playing as armchair revolutionaries)
And to all of that, the first response that we find here is some completely irrelevant pontification about how one “shouldn’t be using a microblog to send notifications”?
Like, really? This is the type of things that we should be concerned about?
What’s next?
People shouldn’t write a “match threader” bot because “following sports updates is not the place for a discussion forum”?
For crying out loud, have we completely forgotten how to have fun here?
rglullis@communick.news 1 week ago
You really made me look…
There are 98 bots, each one was posting exactly once a day. That’s an average of one post every 14 minutes.
poVoq@slrpnk.net 1 week ago
Not one for sunset and another one for dawn? But ok, I overestimated it a bit, but 4 posts per hour is still bot spam.
rglullis@communick.news 1 week ago
4 posts per hour on an instance with 12 thousand active users, and the only reason the mas.to admin found to complain about it is “it pollutes the local timeline”.
I’m sorry, this is beyond stupid. The bot was not abusing any hashtags, the bots were split among different locations precisely to make them relevant only for the people in a certain location. Yeah, OP could’ve changed the bots to “quiet public” listing, but (a) this is a new “feature” from Mastodon and (b) relevant only for people who are anal about the “local timeline”, which in an instance of 12 thousand people is as useful as any random firehose.
poVoq@slrpnk.net 1 week ago
This is not a new feature, it was only renamed from “unlisted” to “quiet public”, and setting bots to that is an entirely reasonable demand, especially if they are only ment for location specific subscriptions.
I agree that on a 12k user instance the local feed is less useful (and that the instance is way too big), but this is probably why they are especially “anal” about bot spam making it even worse.