Reading https://baturin.org/blog/code-hosting-needs-federation/ and I'm wondering how this could be improved for things like the IndieWeb. Granted, there's a weird notion that in order to “join the IndieWeb” that you need to add yourself to https://indieweb.org/chat-names, which helps for sure with the distributed chat that's hosted at https://chat.indieweb.org, but it's not a requirement. But without something like https://indieauth.net/, then it's nigh impossible to interface with the ledger of the IndieWeb, its Wiki. It's where the community keeps its “permanent” record. Granted, it's not difficult to add IndieAuth support to a site whose HTML you can edit and some silos to serve as an identity warden. But I always how much easier we can make it for people.
Getting back to the point, the IndieWeb doesn't really have a mission of “world domination” - which I think is good. But it does make advocacy a bit more difficult since it does require upfront re-programming (literally and mental) and potentially a complete reconfiguration of what it means to be online in a social way. Outside of tools meant to be used by many people like https://micro.blog and https://brid.gy, you'd be hard-pressed to find something that works to increase the number of sticky IndieWeb members.
Engagement is powered by Webmentions — a premier standard of the Web to let other sites know you've mentioned them. Learn how to reply from your own site. or from a supported silo Aaron has an interactive post about this. If you've mentioned this URL via another one, use the form below to submit it.
If you don't currently own your replies, then you can click below to do so.