Given the general Lemmy guideline that users should avoid posting more than 5–10 times per hour in a single community (to prevent flooding the overall network), would it make sense for Lemmy to implement some kind of Hourly Post Counter?
For example, a small indicator that shows how many posts a user has made to a given community in the past hour—like “3/10 posts this hour”—maybe visible when posting or on your profile.
Perhaps have it so that if users go over the limit, they get an error message.
It could help users stay within the community norms, especially since Lemmy doesn’t have as many active users as Reddit, and frequent posting can have a larger impact here.
Do you think this is a helpful idea?
Or would it just take up space?
Would love to hear your thoughts.
Why not just fix the algorithm so you don’t get spammed with those posts? Limit posts from one community to 1 or 2 per page so it’s at least spread out.
It’s kind of a growing pain issue honestly. As lemmy grows and more people post in more communities it shouldn’t be as much of a problem. I don’t know if self regulation like that will really affect the serial posters though.
Yeah I just wished there was more cross posting intelligence so we don’t have duplicate posts filling up pages. Like if they creates checksums of the posts that clients can use to filter out duplicate posts.
I hear Piefed has the cross posting intelligence. It’s hard to tell when using it though because… Well hard to notice a fix like that. I using it on my PC but haven’t found a good android app yet.
While the issue of the inter-server protocol being overly chatty is very much real, putting the burden on the users isn’t a good solution.
The focus should instead be on improving the protocol itself and its implementation with better algorithms, batching, etc. I’m not super knowledgeable about the inner workings, but I feel like there’s still some relatively “low hanging fruits” in the protocol design (are activities properly batched? are they sent as linear broadcasts to all federated instances? could we use some alternative broadcast distribution, like binomial? etc) and implementation (is the data model leading to some expensive operations? are the SQL queries well written? could we speed them up some other way?).
I say this as someone who’s been running an instance for many years now, and can tell you for sure it has been a rather bumpy ride, as a small server. Running a good and fast server with lots connections is not cheap; not as much as it should, at least imo.
How would people have intense and verbose arguments then? No, they should implement a system like in /r9k/ back in the day, where every post had to be an original combination of symbols or else you wouldn’t be able to post it. Reset the filter every week more or less, depending on traffic, and that should take care of repetitive nonsense!
