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.”
Source: https://digital-strategy.ec.europa.eu/en/library/broadband-coverage-europe-2021
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.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Upvoted, but I feel horrified by the notion. I’d much rather have a headless server
@MigratingtoLemmy use a hammer to break the screen, control via adb :vlpn_happy_blep:
Wait are you messaging from mastodon?? Is that why the emoji won’t render
@Omniraptor ah yes! Probably that’s why.
Actually the whole original post was sent via Mastodon.
I tend to write posts that I share to my Mastodon followers and then at the end I mention a Lemmy community if I believe the community would also find it interesting.
That is so cool I didn’t realize lemmy and mastodon were different views into the same database, assumed they were different services with no overlap except some underlying tech (I don’t know much about fediverse structure). But how does that work with like, character limits? Iirc lemmy can have much longer comments
@Omniraptor @Wander Probably user is limited during writing by own instance limit and longer posts of others could be displayed. I saw this between mastodon/misskey instances with various limits, probably it could be similar for lemmy/kbin federation. Currently I am writing this on small mastodon server with 20k limit (never used this fully yet…)
@Omniraptor in theory Mastodon will show a “read more” button for longer comments. Top level posts sent from Lemmy often require clicking the link to view them in full and content isn’t ordered by votes because they don’t exist.
So, it’s a bit messy to read Lemmy from Mastodon, but posting something and then replying to comments on that thread is really easy.