Is there really any scenario where a normal user should NOT be rate limited on posts or comments to some degree? Say, no more than 3 posts per minute? No more than 10 replies?
This is why Lemmy needs to keep tweaking it’s feed algorithm. I understand why many people rightly have a distaste of social media algorithm fuckery, but Lemmy doesn’t have some of the same bad incentives that an ad driven site like Reddit or twitter might have. A better algorithm will help Lemmy grow and surface interesting posts organically.
The recent feed change to boost smaller communities in 0.19 is a good start, and not showing too many posts in a row from the same community will be another welcome change.
But when anyone can run an instance, you can’t control it. Someone has an instance which allows them to make as many posts as they want, and then all that content is federated to connect servers
Really though? You can implement the same limits for federated posts, and just drop the ones exceeding the rate limit. Who knows, might be frustrating for normal users that genuinely exceed the rate limits, because their stuff won’t be seen by everyone without any notice, but if they are sane it should be minimal.
The notice might still be able to be implemented though. idk how federation works exactly, but when a federated post is sent/retrieved, you can also exchange that it has been rejected. The local server of the user can then inform the user that their content has been rejected by other servers.
There are solutions for a lot of things, it just takes the time to think about & implement them, which is incredibly limited.
I can think of a couple. For events like the NFL or some expo where you want a bunch of different topic discussion threads all at the same time. But even then, it would very limited.
Is there really any scenario where a normal user should NOT be rate limited on posts or comments to some degree? Say, no more than 3 posts per minute? No more than 10 replies?
deleted by creator
This is why Lemmy needs to keep tweaking it’s feed algorithm. I understand why many people rightly have a distaste of social media algorithm fuckery, but Lemmy doesn’t have some of the same bad incentives that an ad driven site like Reddit or twitter might have. A better algorithm will help Lemmy grow and surface interesting posts organically.
The recent feed change to boost smaller communities in 0.19 is a good start, and not showing too many posts in a row from the same community will be another welcome change.
But when anyone can run an instance, you can’t control it. Someone has an instance which allows them to make as many posts as they want, and then all that content is federated to connect servers
Really though? You can implement the same limits for federated posts, and just drop the ones exceeding the rate limit. Who knows, might be frustrating for normal users that genuinely exceed the rate limits, because their stuff won’t be seen by everyone without any notice, but if they are sane it should be minimal.
The notice might still be able to be implemented though. idk how federation works exactly, but when a federated post is sent/retrieved, you can also exchange that it has been rejected. The local server of the user can then inform the user that their content has been rejected by other servers.
There are solutions for a lot of things, it just takes the time to think about & implement them, which is incredibly limited.
[This comment has been deleted by an automated system]
Those numbers seem high for a normal human being. 1 a minute is even high for quality content.
I can think of a couple. For events like the NFL or some expo where you want a bunch of different topic discussion threads all at the same time. But even then, it would very limited.
flip those and double them