You are viewing a single comment's thread:

RE: Announcing hive.micro: A New Microblogging Platform on Hive

The moderators is a comma separated list of accounts, and you can set it to anything starting with single mod (1/1) to any amount (it just count number of mods that agree post should be hidden) (x/y) all the mod attempts are logged and there is a control panel with options. e.g.

image.png

image.png

The idea was that anyone could spin up a feed based on their custom_json tag (if i change the env for hive.micro to bob.place it changes everywhere in the app and only reads those custom_json) and each group could set their own moderators etc.

Originally I was against adding moderation at all, but then, not that I'm aware that it has ever happened, I don't want to be responsible for CSAM or anything like that.

RE: the routing tags, I might look into that e.g. sending #NSFW to its own page. Always looking for input, thanks for the idea!

0E-8 BEE
1 comments

That quorum setup makes sense, and the audit log is a solid call. Could the threshold be set per group and include an unhide path, like a separate vote type or timed review, and are those logs available via a public endpoint so others can audit decisions? For routing, you could let instance owners define simple rules in env or a JSON file to map tags to streams, plus user level filters so people can auto hide or divert tags they pick. Also curious if you plan a soft hide that collapses posts in the main feed while keeping them reachable on the author profile.

0.00023701 BEE