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.
That’s definitely a good call. Before I even had a NAS, I’d just throw some movies and stuff on my macbook when I had to travel. Problem is that when you’re loading it up, you think you know what you’ll want to watch and then later you just wish you had different choices.
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.
I thank all the people who have worried about me, I know that we all have bad moments at some point in our lives, I just hope that my bad moment ends soon and I can't stand so much suffering again💔
If it’s going in something (e.g. dahl) I use the frozen stuff. If it’s to munch on raw or as leaves then I abandoned fresh spinach ages ago - Kale is much more robust and (IMO) tastes better.
#Writers – send your work to NEW WRITING SCOTLAND 42!
We want poetry & prose in English, #Gaelic, & #Scots from writers who are Scottish by residence, birth, or inclination. Submission is free & all successful contributors are paid – deadline 31 October!
This week we've got a series of updates for you after being hard at work...
First up is some research we've carried out to help us get the most out of low-powered TV platforms - which we hope will make it easier for us to create high quality user interfaces for our services:
@BBCRD unexpected and interesting. I'd feel like this is more of a suggestion that the WebGL implementation wasn't sufficiently optimized, WebGL optimization is kind of a bottomless pit. Though maybe there's a way that WebGL taxes the system that makes frame drops unavoidable regardless of implementation. Embedded systems are another world.
1973 #Ethernet as one of the defining information technologies in modern communication was developed at #PARC by Chuck Thackers for #Alto#Computer s. What Bob Metcalf, Butler Lampson, and Dave Boggs built for the #ARPAnet is connecting us all today— via the #Internet, & @fediverse.
You are conflating layer 1 technologies (shielded or unshielded twisted pair, CAT3 through CAT7) with layer 2 technologies (Ethernet).
Layer one is the physical media itself. Alternatively some modern-day L1s are MoCA, Powerline, WiFi, fiber, and of course, 1000BaseT, whose standard specifies CAT5e or higher STP.
Layer two is how those bits get sent in that media. Ethernet is, by and far, the most familiar L2.
And then layer three is where we get to networking and start talking about IP addresses (IP being the most familiar L3).
I don't understand why #memory chips are still separated from CPUs. Any #computer programmer can tell you that memory access is slow. We put all sorts of things on the same chip together.
@schizanon A number of reasons, simplifies the CPU design, improves cooling, maximises flexibility to match cpu+ram to use case, no expert on this next one but I think optimal/maximum frequencies differ enough between cpu and ram speeds that trying to match them (for compatibility) would inevitably impede the functioning of one or both systems.
There's a really long answer here which might help ... https://electronics.stackexchange.com/questions/175615/why-is-ram-not-put-on-the-cpu-chip
from the Autistic members of the Kentucky Advisory Council on Autism: we're seeking input from all Autistics who have experienced thoughts of suicide, whether or not you live in Kentucky we want to hear what you have to say