My server is a phone now(seg6.space) |
My server is a phone now(seg6.space) |
without root, you also can't bind to ports on any android phone, and rooting often requires an unlocked bootloader and not all android phones support bootloader unlocking. You also need an unlocked bootloader to install postmarket os.
so you can't run a web server unless you run it through a proxy server which the author did, or containers at native speed on postmarket os because you will not be able to flash the phone with postmarket os if you have missing kernel syscalls on android nor root the phone for the speed increase on android depending on your kernel version i assume.
so with android containers may or may not work without emulating x86, and without root chances are it will be slow specially if you are forced to emulate it as x86 because it turns out you have missing syscalls, nor root to make them faster if they exist on android. again no chances to install postmarket os nor rooting to make containers faster without bootloader unlocking.
not all android phones can have their bootloaders unlocked unless you find an exploit. https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame
would've been better
--
> built in battery backup
Isn't it always recommended to remove battery if you plan to use a phone or a laptop as a server? ( Fire hazard )
or is it fine to just limit the charging to 80%?
By saying "my server is now ..." implies a change of server platform to a phone but not where it came from.
Your offering: "my phone is a server now" implies a change of phone usage but does not indicate where the server came from.
The article itself tells all.
Agree! But do get one or two of those "small automatic fire extinguisher" or whatever they are, that you can attach on stuff, for electrical panels and what not, and put right next to it together with a traditional fire alarm, and you're good to go :)
But in other hand, it is probably a pain in the ass to remove the battery and do some workarounds to make sure the phone correctly behaves without it.
iPhone hardware wise is like an amazing alternative to rpi (way better hardware)
But the software makes no sense at all for a server, with screen locking due to inactivity and whatnot, not to mention energy and network priority is designed around a consumer use case on the move.
If you run Linux on it and take advantage from the Apple hardware like the light sensors and accelerometer - maybe it makes sense for measuring wave height, sky color, attached to a buoy or oil rig or something, you can even show it on a map due to its GPS. Assuming the oil rig has WiFi or a cell phone booster.
Idk though, maybe for something that important you just get the right stuff - cool hobby nonetheless.
I’ve wondered for a while if they could be used as an extension to your laptop like the old 80s PCs where you would plug in hardware.
So ‘make it a server’ is the obvious way I guess, and then you could do things like render webpages on there and then stream them as images to your actual computer (like the now shutdown Mighty app), or run ffmpeg on there to convert a video, etc
I run kube in a VM, and it was ressource constrained.
I hooked an old samsung to my pc and have let claude handle everything.
I only had to unlock the bootloader, flash the image claude uploaded.
It rebuilt postmarketos multiples times to enable various flag, and now there is a kube node running on it.
Would have been a fun load test had you hosted your blog on the phone.
Any efficient blog software will handle HN fine on anything that you can call a smartphone, so like maybe not a Nokia with GPRS and 6MB on-board storage, but something like the Samsung S2 from 2011 that basically shipped as a Linux box -- just need to adb push ARM binaries for PHP and a webserver
> An open source anti-detect browser built for AI agents.
Sounds legit, circumventing the locks people are trying to add to their properties in an attempt to keep costs down and the service available for people that are actually trying to use the service rather than bots roaming around. Really happy for you that you managed to run ten of those. Not a nuisance at all.
People immediately see the cost of a tablet, the issues with charging, building the app and updating the data, customers not understanding the interface etc.
Yet, they don't seem to grasp all of these are basically the same for a QR code: you're now maintaining an online service just for your restaurant. People still need to understand your site. You'll be dealing with their browser, extensions, languages etc. And you still need the QR code somewhere on the table, visible, explain that it needs to be scanned (by one person ? everyone ? do they need to keep the tab open ? etc.). These will all be costs, you pay either upfront by hiring experts to make the experience good, or on the go with crappy customer experience, your staff spending more time than needed working around the system and explaining it to your customers, and those not coming back.
There are super cheap and simplistic ways to deal with all of that, and I assume GP has seen many of these.
PS: The weirdest experience I ever had was someone at our table scanning the code, to copy/paste it on the browser on their personal profile (default was work browser). They missed a digit in the url params and ended up opening the order menu of a table at the other side of the restaurant, and just started ordering, then waiting for a pretty long time while the other table was dealing with the mess.
1) It's optimized for the restaurant first, and the patrons second or not at all, and it shows.
2) Someone thinks "hey, we could sell ads on this", and now it's even more a piece of garbage. (This is also what happened with all the little kiosk-tablets on the tables at some restaurants. We just set them face-down on their screen and talk to a human.)
3) Most of them never anticipate unexpected problems. They might have an "order X" button, but they often don't even have a "call server" button. And when they do, it often doesn't work, because the other end isn't hooked up to something that gets people's attention.
The much lower-tech and more enjoyable solution I've seen used successfully many many times is a call button on the table. Press the button if you want service. Bonus if it has a "press this other button if you want to be left alone".