2 ms·
The big problem with browser-as-server is that users typically want to power off their browsing devices, while they typically want servers to be always-on. Tyi
by dllthomas 13y ago
The big problem with browser-as-server is that users typically want to power off their browsing devices, while they typically want servers to be always-on. Tying it through a cloud-hosted VPS or some local dedicated device (those wall-wart computers, or something else lightweight and low power but sufficiently capable), but then having the browser talk to it smartly (potentially from several devices simultaneously), would seem a better plan.
- abvdasker 13y agoOne possible solution is to distribute the hosted content to peers, so that when one person's browser is offline, hopefully someone else's is online to act as a server instead. That doesn't serve as a guarantee, but with a centralized fallback it could work. There are some very clever people already doing this with WebRTC.
- dllthomas 13y agoRight, that works great assuming static content.
- icebraining 13y agoPeople interested in privacy and Free Software are already working on it: https://freedomboxfoundation.org/learn/ https://freedomboxfoundation.org/learn/
- dllthomas 13y agoRight, certainly related - the vision may or may not be precisely what I described (I'm not sure one way or the other about browser integration) but certainly a great starting point to build off of if not entirely what we want.