0cfd614f6c
|
||
|---|---|---|
| Dockerfile | ||
| docker-compose.yaml | ||
| readme.mdown | ||
readme.mdown
federation
In regards to ActivityPub, a big problem is a lack of clarity on what instances are blocked and why by various instances. This is a documentation and accessibility issue as I doubt most instances create or publish either. Much like users picking an instance to join because of a theme or the moderation policies, instances could join a federation because of a grand moderation policy.
decentralized authority
The other big problem is having central authorities like Google or Apple as moderation. You can see a similar problem on the internet with certificate authorities. If a CA is compromised, which they have and they will, then the trust is broken at the root and anything that inherited that trust needs to have it reestablished. I’m not eager to apply blockchain to something that is a governance issue. An alternative is notaries.
proxy consensus
The general idea is trusting more than one authority, polling them for a consensus on which instances are filtered/restricted. Many nodes would simply proxy their inherited filters but can change what node they would inherit trust from.
Much like users pick an instance to join because of a theme or the moderation policies, instances could join a federation because of a grand moderation policy.