mirror of https://gitlab.com/bashrc2/epicyon
readme updates
parent
72ed55e0ed
commit
7011f1d7d2
|
@ -50,5 +50,5 @@ The following are considered anti-features of other social network systems, sinc
|
|||
* Collaborative editing of posts, although you could do that outside of this system using Etherpad, or similar
|
||||
* Anonymous posts from random internet users published under a single generic instance account
|
||||
* Hierarchies of roles beyond ordinary moderation, such as X requires special agreement from Y before sending a post. Originally delegated roles were envisioned, but later abandoned due to the potential for creating elaborate hierarchies
|
||||
* Federated blocklists. Initially this seems like a good idea, but the potential down sides outweigh the benefits. eg. Two allied instances share their global blocklist. Some time later one instance is transferred to an adversary, or gets hacked. Adversary can now control your global blocklist and trash your instance very quickly that way.
|
||||
* Federated moderation. Again, seems like it might be beneficial initially. Share the burden of moderation. But under realistic conditions people could be pressured or bribed into giving federated moderation access, and the consequences could be very bad. Individuals going on power trips, controlling multiple instances and heading back towards centralization.
|
||||
* Federated blocklists. Initially this seems like a good idea, but the potential down sides outweigh the benefits. eg. Two allied instances share their global blocklist. Some time later one instance is transferred to an adversary, or gets hacked or sold. Adversary can now control your global blocklist and trash your instance very quickly that way.
|
||||
* Federated moderation. Again, seems like it might be beneficial initially. Share the burden of moderation. But under realistic conditions people could be pressured or bribed into giving federated moderation access, and the consequences could be very bad. Individuals going on power trips, controlling multiple instances and heading back towards centralization. Avoid creating technical routes which easily lead to power consolidation and centralization.
|
||||
|
|
Loading…
Reference in New Issue