Skip to content

Content moderation #19

@mrusme

Description

@mrusme

As this seems to be a topic many people are interested in, here's a rough idea of how this could be implemented in future. I've detailed this on Superhighway84 already and just copypasta it here for the sake of documentation.

BBS were centralized, USENET as well (in that sense that there were moderators
who could decide what goes and what not), so it was basically just a thing of
having someone around to do the job. However, even these platforms struggled
eventually, e.g.

https://www.techdirt.com/articles/20200918/15082545338/content-moderation-case-study-usenet-has-to-figure-out-how-to-deal-with-spam-april-1994.shtml

I believe a viable solution for Superhighway84 would be client-side filtering,
maybe with the help of distributed lists that people could subscribe to if they
felt like. Think of it as how e.g. uBlock Origin works in your browser.

That way users could also create their own lists and publish them for others to
subscribe to. OrbitDB allows for entities to be restricted to writing from
certain peers, meaning that these lists could be restricted to just a handful of
people that maintain them. But each user would basically have the possibility to
start their own list if they'd be dissatisfied with the filtering they get from
others.

Just an idea. Basically like reddit but you can decide on your own who you
want your platform moderators to be.

Feel free to discuss/suggest other approaches and ideas.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions