What if you could buy off the shelf a box based on #opensource software and hardware that you could plug into your internet connection. You could connect to via Wifi and it would allow an average person to fairly easily configure, via a guided setup, a self hosted Cloud Drive, Social Media server, home automation service, VPN end point, email server and other commonly useful software?
What if that box allowed that person’s friends to authenticate and to that box and link a box they own, either close by or remotely. It could extend connectivity and estabilish a chain of trus, provide a level of encrypted backup of content from that box and make assertions about the users on that box such as - This user account is owned by this person, this user account is over 18?
This is a dream. I know I’m rambling. #openwrt, #yunohost, #seflhost, #chainoftrust, #fediverse
@Onomatopoeia I think in this case redundancy could be better delivered through a degree of distribution / modularity - perhaps through keeping compontents separate (I have an issue with an application but that doesn’t knock out router features) but also through chain of trust with friends and family - you can’t access your device (network, power, application ) then you could access backups stored with others - But I do take the point - and discused it in another comment - that perhaps modularity is the answer (e.g. Having a battery backup component that cound support a router component and an app server component ) but perhaps I’m over thinking this anyway - I have no practical way of implementing such a solution / framework myself - perhaps I’m just provocatively discussing it so that people like #Netbox and @bananapi see the discussion and think - hmm perhaps we should have closer relationships with Openwrt or Yunohost - or encourage them to come together somehow…
Exactly, keeping components separated, especially the router.
Hardware routers “cost money because they save money” (Sorry, couldn’t resist that movie quote). A purpose-built router will just run and run. I have 20 year old consumer routers that still “just work”. Granted, they don’t have much in the way of capability, but they do provide a stable gateway.
I then use two separate mesh network tools, on multiple systems. The likelihood of both of those failing simultaneously is low. But I still have a single failure point in the router, which I accept - I’ve only had a couple outright fail over 25 years, so I figure it’s a low risk.