Post #2324156

2023-07-03 17:41 UTC

@YourGodSatan@evil.social @flup@mastodon.scot Every online service has rate limit. Which is the number of requests that can be sent from the user. Like loading posts, liking, commenting, posting. This is part of the software and its disingenuous to claim that. Of course what has happened on twitter is that this limit is drastically increased, which has caused issue. While in normal condition, it won't be noticed by normal users. Also iirc, you can only scroll back up to 400 toots in timeline on Mastodon.

Replies (2)

@YourGodSatan@evil.social 2023-07-03 18:01

@hirad@mastodon.hirad.it @flup@mastodon.scot I tried to lookup the rate limit for mastodon and the one I am finding is 300 api calls every 5 minutes I dont see anything about the post limit I did see other people running into the rate limit issue maybe the defualt setting should be raised. I assume each server can change the rate limiting.

Open ##2324157
@TobiWanKenobi@kolektiva.social 2023-07-03 18:49

@hirad@mastodon.hirad.it This does make sense, if you run your service on a single server farm/complex, since they will---no matter how many you add---have a physical limit to how much traffic they can process. But, Mastodon is decentralized, so the traffic and server access is being spread out across many different server farms in different locations. So while your argument definitely holds true in the sense of physical limitation, it's unlikely to occur here, unless one of the instances gets totally overrun without having the capacities to handle all the inflow of new users. But even then, people can simply migrate to other instances to mitigate the limitations. Something they obviously can't do in Elmo's sandbox. @YourGodSatan@evil.social @flup@mastodon.scot

Open ##2324159