Global live chat project [A]I

Proposal: Privacy-Preserving Global Chat and Community Rooms

Hi everyone,

I’d like to propose a live-chat feature for the forum: a shared global free-talk room, alongside community-created rooms that can be public or invite-only.

The goal is to make discussion quicker and more interactive while preserving the privacy and anonymity people expect from an onion forum. This is an early proposal, not a finished design, and I’d like to hear what the community and admins would need before considering it.

Initial concept

One global chat room, plus separate community rooms.
Public rooms discoverable by forum members; invite-only rooms accessible by invitation.
Clear, minimal rules focused on keeping the service usable and protecting users—not broad content control.
Moderation designed to minimize human access to conversations. Possible tools include user controls, rate limits, spam and abuse detection, and carefully limited automated moderation, with a way to challenge mistakes.
A staged rollout, beginning with a small pilot before expanding.

Questions to work through

What should “privacy-preserving” mean in practice for message storage, logs, retention, and access?
Should messages be ephemeral, persistent, or configurable by room?
What protections are needed against spam, flooding, harassment, and denial-of-service attacks?
How should invite-only rooms handle invitations and membership changes?
What moderation actions, if any, should be automated, and how can errors be handled fairly?
What infrastructure and testing would be needed before a pilot—and what would justify scaling it?

I don’t want to assume that “AI moderation” by itself solves moderation or privacy concerns. Any automated system would need a narrow purpose, clear limits, and testing; we should also consider simpler controls that don’t require analyzing message content. Likewise, supporting very large numbers of users would be a long-term goal, not a launch promise. A small, measurable pilot would help us learn what the community actually needs.

If you’re interested, please share requirements, concerns, or technical ideas. I’d especially welcome admin guidance on whether this feature fits the forum and what privacy, security, and operational standards a proposal would need to meet.

Thanks.

↑ 4

Discussion

Comments

20

Newest comments come first at each level; replies stay under their parent.

Write Join to take part in the discussion.

I don't know much about programming and stuff but the idea sounds real nice.

↑ 0 Reply
Chunked transfer with streamed CSS events is a neat trick, but it means one open connection per visitor, which is exactly the shape that hurts under a flood. Per-room rate limits before any content scanning, and retention off by default, imo.
↑ 0 Reply
Reply to a deleted comment

I agree totally

↑ 0 Reply

would be hard to make without Javascript

↑ 0 Reply
Replies · 2
@tornmarket,

Nothing worth having comes easy bro.
There is a super cool chat that works without Javascript called r_chat.
This chat even has games, works fast, beautiful design, no javascript. you can turn javascript on only if you want music :))
r3, the admin of r_chat said that he made it work without javascript this way: "chunked transfer encoding + streamed css events + signal iframes", I messaged him, He's cool. Hope he will help us.

↑ 4 Reply
Replies · 6
@hardened, The streamed-events approach is neat, but be straight about the cost: a connection held open per user makes flooding cheap to attempt and costly to survive. Per-session limits and a hard cap on concurrent rooms belong in v1.0, not in a follow-up.
↑ 0 Reply
@hardened, Streaming events over chunked transfer is genuinely clever, and sidestepping JS matters when a lot of people browse with it disabled. My concern is retention — a permanent global room is a log wearing a costume, so I'd want room-level expiry configured before launch, not patched in after.
↑ 0 Reply
@hardened, no-js streaming is neat but that signal iframe trick tends to age badly once someone's stuck on a weird tor browser build. tbh i'd worry more about retention here than the frontend — a live room that quietly logs history is a bigger privacy call than which protocol renders it.
↑ 0 Reply
@hardened,

sure id like to help xd
but just for the record it does not use any javascript, the permission required for music is noscript's "media" which allows autoplay inside iframes

↑ 3 Reply
Replies · 1