The potential demise of the Feneas.org 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

Follow

@strypey
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
1000% this would make self hosting available to the masses! IMO this should be priority number 1 for any efforts at decentralization, without it, it's all just talk, since centralized services are just easy...that's why they win:(
@strypey @PINE64 @yunohost

@Blort @strypey @PINE64 @yunohost there is this shop.nitrokey.com/shop/product but it's waaaaay too expensive for what it is:( Plus it's only nextcloud, which is a good start but a yunohost install would do so much more!

@lps @strypey @PINE64 @yunohost

It's definitely part, and an important part, of their success. We can't ignore that they successfully communicate their unique benefits through wide communication channels, while piggybacking off other successful projects with adoption and then following up with well funded distribution channels. Much of this we can do too, but only if we're thinking about these parts as well.

@lps @strypey @PINE64 @yunohost

For example, we can communicate the unique benefits of a box like this as well, but only if we as a community get past the ideas of marketing being some sleazy manipulation technique we want nothing of, and focus instead on clear, honest and simple communication of the benefit of what we offer in the language of the people who would benefit the most.

@lps @strypey @PINE64 @yunohost

We can piggyback of other successful projects, especially if we collaborate with projects that have gotten larger adoption while holding values shared by the community of a project like this (eg Nextcloud, VLC, Ubuntu, Wikipedia, Firefox - still). Even if any of these projects aren't your personal favorite, they all have a voice that can reach people, and sympathy with the values of a project like this.

@lps @strypey @PINE64 @yunohost

And as to funding, while probably the most divisive of what the centralized models do effectively, We have opportunities, too. There's selling the hardware itself, including upgrades. Donations. Opportunities for paid support a la . Referral fees for things like domain purchases and maybe a VPN. Crowdfunding to add full time developers (a la / / ). These are just some ideas (not all need to be used) but many others exist.

Not everbody has a public IP Adress. It would be cool, if there would be a privacy friendly cheap service the homeserver could connect to via wireguard VPN, so the homeserver would get a real IP adress.

@linus I'm not sure if by "public IP address" you mean static IP address, in which case, you are definitely correct. I personally don't have a static IP address. I need to install ddclient to regularly update my dynamic IP address. Once again, this should be something setup and executed automatically, which is entirely possible.

@Blort @linus I think he means public IP address. Some ISPs are doing carrier-grade NAT (CGNAT) where customers only get internal IP addresses, and the ISP's NAT has a pool of public IP addresses shared by hundreds, if not thousands, of customers.

@bortzmeyer @Blort @linus if full DualStack, then yes.
If DualStack-lite, then no.

@Blort
I have a Turris Omnia. I don't know if yunohost could be installed easily but it is possible to have a debian container
@strypey @PINE64 @yunohost

@strypey @freedomboxfndn @PINE64 @yunohost

While @freedomboxfndn and @yunohost are critical pieces of the puzzle, they can never be an entry level solution by themselves. Why? Because if you want to make it easy enough for the average person, you can't expect them to need to learn about port forwarding on their specific model of router before they can even get started. The server needs to be plug and play which means being able to modify the router's ports and firewall automatically as needed.

@strypey @freedomboxfndn @PINE64 @yunohost

I've loved and . They do great things. Both took me considerable time learning about modifying my router configs, opening up ports, port forwarding etc, to a level people outside tech circles just wouldn't bother with. What I wished for was something I could just plug in and have a webpage I could share with others. The strength is not a server, but a server and router working together to make the experience easy and automatic.

@Blort
Even with plug&play server combined with router, one have to buy and configure domain, dns etc. There is no way to use selfhosting without ANY knowledge.
@strypey @freedomboxfndn @PINE64 @yunohost

@miklo
Yunohost already has a feature to auto-config domains, with a couple of registrars, and a plan to expand to others. Many registrars already have apis that let you purchase domains through them, often offering a referral bonus. Choosing the right registrar and then using the api, the project could let users register a domain through the interface and then set up the dns automatically.

That tech already exists. It's just gluing it together.
@strypey @freedomboxfndn @PINE64 @yunohost

@miklo
The more difficult part is that everyone has a different modem with different interfaces for enabling pass through. That's just a single on/off setting though, that people's ISP support could walk them through.

Perfect zero knowledge needed may not be possible, but that doesn't mean we can't make something great that only needs a tiny fraction of the knowledge needed now. already did it once. We can take it even further.

@strypey @freedomboxfndn @PINE64 @yunohost

@Blort @miklo @strypey @freedomboxfndn @PINE64 Theoretically we also do support plugging a VPN from the FFDN folks (through the .cube format and also now .ovpn). This allows to entirely bypass commercial ISP restrictions and have proper internet connectivity and exposure for your server, no need to configure the router. The drawback though is that you have to subscribe and pay a fee to a VPN offer (though not just any random VPN, gotta be a dedicated IP etc)

@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.

@wolf480pl
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 @wolf480pl @Blort @PINE64 @yunohost Having an IPv6-addressed server could make it difficult for IPv4 clients to connect, that's the best I can understand. Can't stuff an IPv6 address inside IPv4...

Glad to hear the IPv6 transition is continuing though, once we're through it things'll be much easier!

@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
Mastodon

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