Since building AP enabled software seems to be the hip thing to do, let's do so.
Stage: Researching.
Ideas: Efficiency. UX.
UI: Hopefully prettier than Pleroma 1... (they did that deliberately 2, lol)
Stack: I'm leaning away from Node.js, Rails, Elixir.
Questions: How to avoid centralization (and HOA drama)?
1 https://en.wikipedia.org/wiki/Pleroma "Pleroma (Koinē Greek: πλήρωμα, literally "fullness") generally refers to the totality of divine powers." The word Pleroma is likely a reference to this.
2 https://wedistribute.org/2018/04/blushy-crushy-fediverse-idol-a-chat-with-lain-about-pleroma/
I think that HOA type drama and inter-instance censorship is a really difficult thing for someone to wrap their minds around. This presents a significant challenge in UX and user expectations (although, it's not the only UX challenge). It also presents a threat to the expansion of the fediverse.
There isn't even a reference to necessity or proportionality there, or any human rights standard, it mainly comes down to unilateral decision making.
It's totally possible to ignore this and to just focus on getting out software with strong UX, but this really is a large part of someone's experience.
At the same time, I can kind of see the argument for being able to effectively deal with harassment.
Multiple standards can be useful.
Someone might opt for a far more free speech arena (particularly, if not everyone wants to be housed in with the shitposters).
That said, the existence of multiple standards doesn't really excuse arbitrary policymaking, petty high school drama, a lack of consideration of free expression, or the poor UX around this.
