4 ms·
> People don’t want to run their own servers, and never will That's one believably accurate summary. But here's another: rather than focus on trying to make it
by PaulDavisThe1st 5y ago
> People don’t want to run their own servers, and never will
That's one believably accurate summary. But here's another: rather than focus on trying to make it easy, cheap and simple for everyone to run their own servers, the tech world spent 1996-today instead focused on offering to take care of this for everybody else, for a price.
Everybody concluded in the late 90s that the "nobody wants to run their own servers" claim was self-evidently true, and so all the tech development went into extending server capabilities, extending browser capabilities, building hosting services and infrastructure, and almost no effort went into making running a web server as easy as, oh, I don't know, running Excel.
Imagine a version of things where the server was almost a toy-like appliance. Hard to do? Yeah, I know, it's hard. But then again, in 1996 browsers with Web USB, Web Workers, Web Assembly and the like would have seemed impossibly hard and yet here we are.
We don't have it because we chose not to build it.
- PragmaticPulp 5y agoThe personal server space is littered with failed startups. Not because it's difficult to make turnkey personal servers. Embedded Linux hardware is unbelievably cheap. They fail because they don't bring any benefit against real-world threats, but they come with significant downside risks. If your house floods or your home server is burgled, your data is just gone. So your home server ends up backed up to the cloud anyway, and now you're maintaining a home server and a cloud server when you could have just used the cloud service for everything without the headache.
- PaulDavisThe1st 5y ago> Not because it's difficult to make turnkey personal servers. It's crazy hard to make turnkey personal servers that will be usable by ordinary people. > They fail because they don't bring any benefit against real-world threats, For a vocal contingent online, real-world threats involve lack of control over hosting, over their data, over encryption. Your own servers would address (at least partially) all these problems, but of course, these are not problems that most people in the world using walled gardens even consider to be problems. > So your home server ends up backed up to the cloud anyway, and now you're maintaining a home server and a cloud server Utilizing an online/network backup service as part of running your own server is qualitatively different from running a server in the cloud.
- solarmist 5y ago> For a vocal contingent online, real-world threats involve lack of control over hosting, over their data, over encryption. Your own servers would address (at least partially) all these problems, but of course, these are not problems that most people in the world using walled gardens even consider to be problems. Vocal? Yes, but my no means the majority. I'm in tech running my own software company and I don't even want to upkeep centrally maintained hardware like my PlayStation. It's just a pain (often enough) and for the non-tech people in my life it's just barely tolerable. Apple TV is the best, but it still has really problems that pop up now and then.
- shagie 5y agoI was a webmaster back in the days when one could debate cern vs ncsa and which provided a better server and for a while, I ran my own web servers at home on some static IPs from Speakeasy... The issue is that the complexity of the modern systems have gone beyond what one person can keep in their head and maintain. This is doubly true when one considers the amount of time investment to keep on top of patches and CVEs. The simple servers are still there. Grab a web server and put static files for it to be served - but people don't want that. They want a fully functional web application with persisted data with a maximum outage window less than the duration of a good night's sleep. Those things aren't easy. Keeping a few servers up and running and the databases behind them backed up and the servers load balanced with failover so that if one of them goes down you don't need to wake up at 2am to fix it. Making a Raspberry Pi web server in a box wouldn't be too hard. Put it on your home network. Open up your device on the home network (note: if the home network isn't to be opened up, advanced network configuration to establish a dmz or putting the device external to the internal network is needed) to the world. And then you've got to find some way to keep that device patched and the ISP not unhappy with the traffic you're getting when your home blog page shows up on HN. For me, even imagining the work that I'd need to do to my home network to set up that... I can't see it making sense anymore to get what I could get by creating a GitHub pages site and doing it there - and then I don't have to worry about all the other parts of my home network. While I can't find my copy of it now, I have a memory of reading a quote from Ansel Adams about the darkroom and that it was a necessity for photography - but he'd rather be out there taking photographs than in the room making the print. So too, I would rather be writing a program or writing a blog post than dealing with maintaining the infrastructure that maintains that. There are too many concerns and too many things where I know that I don't have deep enough knowledge anymore to keep a modern web server in my home network secure when facing the world. Consider all the people on HN who are skeptical of having an Amazon echo, Google Home, or Apple HomePod because they're concerned about a small appliance from a company on their network is possibly listening with an open microphone but only communicates to one Big Tech server... imagine a device on the network that is accepting all incoming traffic and talking to anyone who listens. Spin up that server as an instance on AWS instead and then the worst that will happen is you'll rack up a large bill when it's compromised and someone runs a crypto miner on it.
- 5y ago
- walterbell 5y agoFreeNAS has ~1M deployments and the recent migration of upstream ZFS development to Linux will continue to increase the availability of ZFS-based storage. > Imagine a version of things where the server was almost a toy-like appliance. Odroid HC4 (Arm SBC, dual SATA drive slots, HDMI output, Kodi compatible) is about $100 USD, can run Armbian and LibreElec, https://www.hardkernel.com/shop/odroid-hc4-oled/ https://www.hardkernel.com/shop/odroid-hc4-oled/
- PaulDavisThe1st 5y agoThe odroid seems to be at best only the h/w side of the sort of thing I was suggesting/imagining. It's a funky little box, and that's great, but what about the software? "Mom, nginx is gunked up again, do you want me to restart it or just reboot the server?" "Sam, did you put my new portfolio pictures on the site yet? Sorry Jan, ran into some size and format problems and am still working on it". Etc. etc.
- walterbell 5y agoFor those who have more money than time, Synology NAS devices include mobile apps for common use cases, e.g. photo sharing. There's apparently an open-source clone called XPenology. For simple photo backup, Photosync works on all major desktop/mobile operating systems and can sync to a wide range of local or cloud storage. After 2 decades and billions of investment in web services, it's not realistic to expect a generic "home server" to serve all possible use cases. Those that work best are usually based on an open protocol (e.g. WebDAV, SSH/SCP, SMB). > did you put my new portfolio pictures on the site yet? As an example, the UX for client-side workflow for blog publishing (WordPress, Jekyll, Hugo) is likely independent of the infrastructure for blog hosting (VPS, self-hosted, WordPress.com, GitHub Pages, etc.
- PaulDavisThe1st 5y ago> After 2 decades and billions of investment in web services, it's not realistic to expect a generic "home server" to serve all possible use cases. Those that work best are usually based on an open protocol (e.g. WebDAV, SSH/SCP, SMB). Surely HTTP is the common, open protocol here? Other than email, at least. Is anyone using SMB-from-the-cloud for network file systems? Are they serious? :)