The recent vote quota has been a hot topic and I’m curious about its effects on the site, the feature seems to target power users but I’m wondering about the knock-off effect on content in the platform, since we know about the 90-9-1 rule that applies to most online communities where 90% lurk, 1% post and 9% engage with the posts, I’m concerned that having implemented a feature specifically designed to limit that 10% minority that create the content that the rest consume, have you noticed any issues with content dropping? is there any way to track that? do you know of users who have left because of it? I myself used PieFed before but now I’m using Reddit more, I would understand rate limits but vote quotas are a deal breaker for me whether or not I reach the limit, something about it rubs me the wrong way, and the fact it’s enabled by default on every instance? it feels like we’re punishing away the people who actually keep the platform alive and I wonder if anyone has data on whether this has measurably changed posting behavior or if it’s just a theoretical

CAPTCHAs and sign‑up quizzes annoy real people and barely slow down determined bots. As the fediverse grows, we need smarter, more humane defences, ones that don’t push away genuine newcomers. What creative, non‑intrusive ideas do you have? Trust‑based vouching, proof‑of‑humanity protocols, behavioural signals… what feels both effective and aligned with the open social web? I’m building a social media platform and I’d love to hear your thoughts on this topic.

I’m aware of Photon and Alexandrite, but since Alexandrite is now unmaintained, Photon seems to be my only viable option at the moment. I’ve also been searching for an old Reddit–style UI, but so far I haven’t been able to find one that fits the bill.

Does anyone know of any active alternatives, or ways to achieve that classic look with current tools?

For example this search I did was supposed to limit results to last week and showed something 11 months old:

https://programming.dev/search?q=webml&type=All&listingType=All&page=1&sort=TopWeek&titleOnly=false

Building a small social platform. I want users to post complaints/ideas, upvote the top issues, and have devs tackle the top 3, transparently with tags, milestones or kanban to show what stage each issue is at.

Need one self-hosted FOSS tool (or two that integrate well) for both discussion and voting/prioritization.

What’s your recommended stack? Zulip, Fider, Discourse, Forgejo…? Something else?

Thanks!

One of the main features of my site will be Discourse-style trust levels, the higher your trust level, the more moderation privileges you gain. I’m also considering either a jury system, where multiple users collaborate on moderation decisions, or a meta-moderation system, where users can vote “fair” or “unfair” on moderation actions taken.

Someone mentioned to me in another post that Bluesky also has a very good moderation system, but the best one I’ve found so far is Discourse. What I really like about it is that you earn trust levels by reading posts, not by taking moderation actions. I definitely don’t want to gamify moderation the way Stack Overflow did, that was the worst I’ve ever seen.

The pattern is always the same:

1. Someone passionate creates a community
2. Early members are deeply invested — high-quality discussions, strong norms
3. Community grows, hits the front page / “all”
4. New users flood in, post memes, low-effort content, drive-by hot takes
5. Old-timers get drowned out
6. Mods either burn out and quit, or become dictators ruling their own fiefdom

Reddit’s model accelerates this. Any subreddit that gets popular enough hits the All feed, and at that point the incentives shift from “quality contribution” to “what gets upvotes from the broadest audience.” The people who built the community lose control of it.

I’m working on a social platform and I’m trying to design communities that don’t go through this lifecycle. This is what I have in mind right now. A user’s voting power within a community is proportional to their tenure in that specific community. So if someone’s been there for 2 years, their vote counts more than someone who joined yesterday. No matter how many new users show up, they can’t swing the community away from the people who built it.

The weighting wouldn’t be dramatic, maybe a logarithmic curve where the first month gives you baseline power and it grows slowly over years. The goal isn’t to create an aristocracy, just to make sure the signal from committed members isn’t buried by a flash mob.

Implementation-wise I’m thinking:

• Each community membership has a joined_at timestamp
• When scoring a post within that community’s feed, each boost/vote is multiplied by log2(days_since_join + 1) / log2(30) — so 1 day = 0.05x, 30 days = 1x, 1 year = ~1.7x, 5 years = ~2.1x
• The algorithm still surfaces new content to everyone, but the ranking is weighted toward longer-tenured members’ tastes
• Also considering: a slow-boot period where new members’ posts are held for review by existing members (like a probation phase)

But I’m second-guessing myself. Some concerns:

• Does this just create a gerontocracy where old members gatekeep forever?
• How do you handle the first 30 days when no one has much weight?
• Would this actually prevent the decay, or just slow it down?
• Is there a simpler/better mechanism I’m missing?

Curious what other approaches people have seen work (or fail). Has anyone implemented tenure-weighted voting before?

Edit: I appreciate the suggestions. A few of them actually align with features I’ve already built:

• Trust graph: The platform already uses directed trust edges, with vouching and inviter accountability (if an invitee misbehaves, the inviter is penalized). I can extend this model from the platform level down to individual communities.

• Invite-only mode: I already have trust-based monthly invite limits for the whole platform, so adding the same option for communities seems like a natural extension.

• Slow-boot / probation: This is already in place, new members’ posts are held for curator review before being published.

• Different interaction types: The system already supports multiple interaction types (like, comment, share, gift, emoji). I’m not sure how to expand these into Slashdot-style categories (e.g. agree/disagree, insightful/funny, quality/shitpost, high/low effort, etc.), but it’s something I’d like to explore.

• Moderation limits: I like Slashdot’s approach of limiting moderation to prevent burnout. I’m less certain whether meta-moderation would be a good fit here, but I’m open to considering it.

I previously let an AI agent build an entire social media site in one day. It worked, but then it introduced a bug that neither I nor the agent could fix because I had no idea what the code did.

Now I want to rebuild it. I want to use AI again, but this time as an assistant – I’ll review every change, write tests together, and keep a clear plan.

Which AI tool would you recommend for this hybrid approach? How do you structure prompts to force the agent to explain before coding?

Also, do you think a couple of weeks is realistic to rebuild the site that has feature parity with Lemmy and a few extra features that the AI managed to build in a single day? Should I switch to a more manual approach with the agent only for boilerplate?

Any advice is appreciated. Thanks!

I’d like to be able to navigate text in a pager with Vim-style modal editing (moving with hjkl and yank/paste with y/p). Is there a way to enable this in the default pager, or is there an alternative pager that supports this kind of modal behavior?