The future of selfhosted services is going to be... Android?
The future of selfhosted services is going to be... Android?
Wait, what?
Think about it. At some point everyone has had an old phone lying around. They are designed to be constantly connected, constantly on... and even have a battery and potentially still a SIM card to survive power outages.
We just need to make it easy to create APK packaged servers that can avoid battery-optimization kills and automatically configure an outbound tunnel like ngrok, zerotrust, etc...
The goal: hosting services like #nextcloud, #syncthing, #mastodon!? should be as easy as installing an APK and leaving an old phone connected to a spare charger / outlet.
It would be tempting to have an optimized ROM, but if self-hosting is meant to become more commonplace, installing an APK should be all that's needed. #Android can do SSH, VPN and other tunnels without the need for root, so there should be no problem in using tunnels to publicly expose a phone/server in a secure manner.
In regards to the suitability of home-grade broadband, I believe that it should not be a huge problem at least in Europe where home connections are most often unmetered: "At the end of June 2021, 70.2% of EU homes were passed by either FTTP or cable DOCSIS
3.1 networks, i.e. those technologies currently capable of supporting gigabit speeds."
PS. syncthing actually already has an APK and is easy to use. Although I had to sort out some battery optimization stuff, it's a good example of what should become much more commonplace.
It's a really cool idea, and the internet would probably be a better place if more people took ownership of their infrastructure rather than relying on ad-supported "free" services, and it's easy to criticise an approach that I've spent maybe 10 minutes actually thinking about - I've got my reservations, but if you can make it work it would be awesome
It is possible nowadays: I'm hosting quite a few services on an 5 years old Android. Just with Termux, no root required.
Of course connectef it's just to the internal network due to all the security concerns mentioned in the post.
To solve all the bandwidth/connection issues, I've bought a usbc-ethernet dongle that works like a charm.
To mitigate battery issues I've limited the charging to 85%.
I would never host Jellyfin there, but with webdav and Kodi I can get my media served easily to all my devices at home
The risk that @regalpotoo mentioned is still unmitigated though, single user instance or not. At worst, the personal data can be exfiltrated. At best, the server can be used as a part of a botnet. Even if the software (nextcloud) would be patched, that doesn't help against exploits on a OS level.
Granted, one could run services inside a vpn and have some kind of preventive / monitoring controls, but you're still need to implement some kind of defense in depth in order to protect it.
I mean, android is fine I guess, but it's being pushed to be less and less able to be separated from Google. I think for a lot of people interested in self hosting, there's a low amount of interest in it because of that.
@southsamurai Oh that's definitely a huge concern, but not just for self-hosting but for privacy in general.
But still, if the average joe wants to self-host something using an old phone is probably the easiest way to get them to try self-hosted alternatives and drop corporate / commercial services.
Maybe not the 'average average joe' such as my parents, but anyone who is minimally curious enough to do stuff such as registering a domain, setting up a game server for friends and maybe has opened the CMD windows console once or twice in the past following a tutorial. That kind of demographic (IDK if it has a name) might be much more inclined to self-host if it was as easy as installing an APK and letting your phone one somewhere at home.
Overall as long as Android doesn't become straight out malicious spyware itself, the benefit of dropping commercial alternatives might very well be a net positive. In a worst-case scenario, any tunnel / vpn configuration necessary to expose a service to the internet could also add an automated step to blackhole requests to google's tracking servers.
IMO, more like Linux. Android for such old devices is unmaintained, but if you're able to run Linux on it you'll still be able to apply kernel updates and security updates for software will continue to exist. Many things are opensource too and you should be able to recompile them on the android device to make it run.
Hmm I think my main concern would be lack of kernel/firmware updates, running something like postmarketOS could partly solve that and still be nearly as easy to set up (just unlock and flash a prebuilt image)
But firmware is still almost entirely dependent on the vendor, since it's all signed and unpatchable.
Next issue would be lack of connectivity on a lot of phones, which have gone backwards and include USB 2.0 now. WiFi is an option, but less stable, I personally decided to just go 100Mbps and suffer.
As for the battery, it would help a lot if phones were designed to boot without one and they were removable, it all worked well for about half a year until I found out I had a spicy pillow and had to replace it with direct power to the board, which made the whole setup much less elegant and required soldering.
It all comes down to how devices are designed in the end. If someone took the time to make a computer instead of just a phone, and included features that make it useful past its initial life that aren't that popular (display output, microsd, headphone jack), mainlined all the drivers and maintained firmware, that would be a different story.
But that's not a very profitable model, because it's all about reducing waste and thus selling less. A lot needs to change.
I feel like Android is adding some new power saving "feature" with every version to kill all the useful stuff I want to keep running in the background.
Last stupid thing I remember was when it removed my CalDAV synchronisation because I haven't been "using" the CalDAV app for some months.
Not to mention all the times it decides to kill something you want to use because it thinks the RAM would be more needed elsewhere. Honestly my 128 MB RAM Nokia N900 could run more apps at the same time than my 4 GB RAM Fairphone.
Yeah, android is a lot like Windows in that they make choices that might benefit users who don't know what's going on but interrupts or harms things power users are doing. They are just better at not being as annoying with it and don't beg people to use their default programs.
You're right, that's a feature if you're a regular phone user and a bug if you want it as a server.
Also, even if the application is still running you can have the os almost fully shutdown even if it's charging. Again, it's a behavior tuned for a typical user.
Big problem: updates for something that is directly exposed to internet
Some low end devices will stop getting security updates 6 months after launch because the OEM launches a new model every two weeks and obviously doesn't have resources to dedicate to it
In some cases, even high end devices don't get updates and are discontinued internally shortly after launch, for example the Xiaomi mix 3 5g
Yes, root and custom ROMs could solve the problem, but not as easy as regular Linux where you just use a package manager to update. First issue is needing to wipe after updates and you have to reinstall and reconfigure everything
@Wander@selfhosted this whole “We are walking about with entirely reasonable servers in our pockets for reasonable scales - why doesn’t it feel like that?” thing is in my brain quite a bit.
@benjohn@selfhosted 6-8 GB of RAM with powerful CPU and GPU that was designed to run games and can in some cases run small AI models is nothing to scoff at imho.
Pretty cool concept actually. upcycling old tech does seem to be a selfhosting hobby. I see a lot of criticism that I think doesn't really see the value proposition. You should be able to root the device and install a new OS. I wonder how limited the bandwidth would be though, and whether it'd be worth the cost to get adapters, if they exist, to allow more throughput. I do like the concept though.
If I'm just using them as a glorified small Linux box it could work pretty well. If you're going to host services that don't require a ton of bandwidth you don't need a hard line or anything. Hell my Plex server is using WiFi (802.11ax but still) and it delivers 4K just fine.
Shit, I run plex of my synology ds1621+ and it chokes on 4k regularly. This is with a cabled connection. It's almost certainly the CPU though. These things are weak as hell. What're you running plex on ?
I run 4 mail servers, 2 game servers, 3 directory/auth servers, a firewall/router, a NAS, a security system server, a media server, a monitoring server, and a couple others. Android ain’t gonna cut it.
Who provides the software and firmware updates for my antique Samsung S4 and Galaxy young?
I hope you will give me some firmware for the old snapdragon.
Don't forget the loads of Exynos CPUs and loads of GPUs from different vendors.
Just to clarify, the the whole point is that Android makes it easy for less tech oriented people to host small single user / family services.
It does not need to be perfect, have massive throughput or allow for massive amounts of read/write cycles.
If people can host their own media server like Jellyfin or note taking apps like Joplin instead of using commercial services by simply installing an APK on an old phone they can leave connected at home, that's already a big win.
Regarding device longevity, Android 13 apparently supports / will support full KVM emulation. Windows can be run if you have root while android based VMs are expected to be possible without the need for root. Since this type of virtualization allows VMs to run their own kernel, keeping the "server app" updated should allow the user to be protected even if the host OS is outdated as long as these server-app-VMs are trustworthy themselves.
Pass, I'll take the cluster of raspberry pis for the same cost... For the purpose of self hosting my cluster is going to out perform your x86. Like why are you going to spend hundreds of dollars for an x86 that will do fine when you can spend $50 for a pi that will also do fine?
Then you can just cluster those pis and get redundancy
@ahoyboyhoy@selfhosted Nice. I remember trying it out once. Actually I might use that to follow my own advice and self-host at home once I retire my current phone.
True, I haven't had the need because I know how to run stuff on a server, but for personal files it's probably better to host things at home.
@Wander@selfhosted I have old Pixel phones with LineageOS installed, but I haven't found a good way to prevent battery inflation. I'd love a way to limit charge to 50% or to bypass the battery altogether.
@ahoyboyhoy@selfhosted How old is the phone and what version of the OS are you using? I was under the impression that modern phones bypass the battery when connected to the charger and having full charge.
Regarding limiting the charge, I believe there's some software calibration you can do which would allow you to set it to 50%. I'm no expert in battery or repairs at all, so someone else might have a better idea.
The latest pixel devices (since 6 I think?) already provide accees to a /dev/kvm device, so maybe you could even run a normal Ubuntu server VM on your phone for hosting these services.
@Wander@selfhosted This sort of setup is very attractive IMO because of the low power usage. Android phones use much less power than old PCs.
The main con I see is not having ethernet (maybe there's some sort of MicroUSB/USB-C to ethernet adapter, but I didn't look into it yet). That, and there being only one port.
@herzenschein@Wander@selfhosted with a cluster, even in WiFi you could mitigate some of those problems, but for home use clusters is potentially asking too much
@Wander@selfhosted Sounds like a great way to kill you phone's battery. But maybe if you created an ad-hoc stack... Have you ever heard of @veilidnetwork ?
I think there's some truth to it. But I imagine it will be more AOSP than what android is with google services.
AOSP is really a great operating system with very good security and built in features.
And with neural engines and high bandwidth emmc, it is mostly just lacking a large amount of storage to make it all complete, but the latest SOCs are most probably powerful enough.
Is there something like docker for android? :)
Edit: I do recognize what someone else said, which is that one big challenge would be software updates. We are not that limited by hardware when we consider servers, they can easily run for years with regular software updates.
I was going to host pihole on an old android until I noticed it getting quite warm while continuously connected to power. Realised I didn't know the lifespan of the battery and didn't want it tp start a fire.
@Wander@selfhosted Unlikely, the biggest issue android devices have is hardware support due to the ARM CPU architecture. It's just not as useful as old x86 hardware, you're stuck with old outdated and vulnerable firmware. My opinion is that one of the selling points of ARM hardware for device vendors is it's relative impossibility to get open source driver support. You may see some use of Apple M1 and M2 simply because it's a smaller FOSS support target, but android devices vary too much.