Asklemmy

49160 readers

644 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 6 years ago

MODERATORS

Should Lemmy potentially add an hourly post counter to help users avoid flooding communities? (lemmy.world)

submitted 3 days ago by Teknevra@lemmy.world to c/asklemmy@lemmy.ml

5 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] tmpod@lemmy.pt 6 points 3 days ago

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.