Getting a bot to spam out 12 posts in a minute is not the way to make me want to engage.
This is where I believe that other site did a decent job with their front page: they created filters that divided it into most popular, what’s trending, and what’s new. I like seeing posts from the variety of different communities, but I do not necessarily want to see every single post. Especially the ones from the same community, in succession. Having a way to only see the ones that are considered “popular” would be nice.
Lemmy has 3 different feeds with 8 different ways to sort them, atleast my viewer does…. What more do you want?
Curating a feed is best left to yourself, not someone who can tweak the algorithm to avoid certain posts showing up since they have an agenda.
I live in my happy bubble with my subbed communities.
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?
flip those and double them
An external server can simply fake the timestamps. If I cared, I could make this comment appear as if it were posted in the 1800s.
Individual servers may want to rate limit (non-bot) accounts, but for federated systems that’s merely a small roadbump.
There is a solution to this problem, and that’s quick and decisive action from the moderators of the server being spammed. Block the user, or defederate the entire instance if that doesn’t help, and purge all the old posts.
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.
There is an option you csn toghle in settings that stops showing bot account and posts
I generally sort by everything:12 hour and feel that I get a pretty good and relatively ‘clean’ cross section of the content.
