Lack of channel moderation causing unmanageable sprawl and spam
Problem
Parley's global channels lack modes and operators, forcing every server admin to moderate all channels individually, which makes it impossible to effectively block harassment and spam, rendering scaling and moderation unworkable.
Pain points
- Global channels lack modes and operators, forcing each server admin to monitor all channels individually
- Spam and malicious servers created dynamically make the system unscalable
- Reliance on shared blocklists, which have proven unreliable historically
Questions to verify
- Would you be willing to adopt automated shared blocklists to reduce admin burden?
- Can you accept that each server admin must manually moderate all channels?
- Are you willing to register each new server's identity and join the federated network?
Evidence
quote · @Anonymous
No channel modes and no channel operators, which is a decision rather than a gap: a global channel is owned by nobody, so there is nobody to be an operator of it. Blocking is per person and per instance instead. That's completely unworkable. Let's say I create #some_minority, and people from many different servers join. Some shithead comes and starts screaming slurs at us. Now the admin for every server must block that person. Multiply that by every channel, and every admin is responsible for moderating the entire ecosystem. The only way they can do this is with shared blocklists, which have been a nightmare on mastodon.
quote · @Anonymous
How do you plan to handle bad actors creating biblical amounts of servers dynamically and then spamming at line rate from all of those servers?
quote · @Anonymous
So rooms are "global" between whatever hosts your host happens to know about? So it's one giant netsplit party forever and only your server admin can ban someone?
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.