I'm thinking of @aral's small web ideas (which are very good! Go read about them!), but there are two forces in play that I never see discussed well in the context of small web, decentralization, and federation:
- quite a lot of existing stuff takes quite a lot of know-how to make go, and all the simplifications take quite a lot of power from people, or at least _raise_ the barrier to learning how to manage it more deeply
- a lot of stuff is better at the community or family level than the individual. Lots of software affects multiple people.
How do we manage community software in a healthy way too?
And how do we keep that technical know-how required from giving the nerdiest among us either a ballooning responsibility ... or some possibly undeserved (or at least unhealthy) power over others?
We're running into this on the fediverse: single user mastodon instances are not as useful as multi-user ones in many cases, and there's a much bigger curve to making it work well.
We see "admin drama" and "defederation drama" regularly: but this is not just a symptom of bad federation decisions and controlling mindsets, but power structures that concentrate power and responsibility on people quite likely unable to bear it. (the legal landscape does this even more, but most instance admins are at this point ignoring that. The risk _is_ acceptably low to do so, I think. Not ideal, but workable.)
What _are_ the healthy structures, covenants, and responsibilities?