The potential demise of the services reminds me again that the success of federated networks depends on reliable instances, and avoiding re-centralization requires more instances, not bigger ones. This means server-side software needs to be as easy as possible to set up and maintain, and we need easy access to ways for people to learn how to host servers.

#fediverse #decentralization #SelfHosting #CommunityHosting

It seems to me that what would make a huge difference would be if someone like @PINE64 would sell a reasonably priced router with enough power and storage to be a basic family server with @yunohost pre-installed. Just plug it in, set your ISP modem to pass through and you have a working server. It could automatically open the right ports, use the new auto dns setup. Referral fees from in device domain purchases through a privacy friendly registrar could help fund.

Easy is a must here.

@Blort @strypey @PINE64 @yunohost sounds great in theory, but nowadays, many ISPs are switching to DualStack-lite, where you don't get your own IPv4 address, only IPv6, and you can't switch your modem to bridge mode (at least that's how UPC does it). You'd need to ask the ISP to switch you to IPv4-only first, and only then activate bridge mode. It's starting to become complicated.

Why do you need IPv4 to run a server? I'm showing my ignorance here, but that seems as counterintuitive to me as needing an older version of HTTP to run a webserver.

@Blort @PINE64 @yunohost


@strypey @Blort @PINE64 @yunohost IPv4 and IPv6 are basically two separate Internets. An IPv6 server is only reachable for IPv6 clients, and IPv4 server is only reachable for IPv4 clients.

That's what makes the transition so difficult.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!