I imagine bicyclists must be æffected as well if they’re on the road (as we should be, technically). As somebody who has already been literally inches away from being rear-ended, this makes me never want to bike in the US again.
Time to go to Netherlands.
No, that’s really not how this ecosystem works. I’ll give an example based on the Retroid Pocket 5, just because that’s what I own and am familiar with. The company ships it with Android 13 by default. So this already has a full desktop environment, full suite of available app stores - everything that any other Android device can do, plus built in game input. No extra hardware needed. I can outright install Signal, Briar, Matrix, any of those kinds of things on it right now. Retroid never did any testing or development for that use case, it’s just what happens when a device has a full, open Android experience from all of the development that has gone into Android and apps over the years.
However, they also chose to use a chipset that has support for Linux as well. At least two projects have already ported their variants of Linux to the RP5 - Rocknix and Batocera. While it’s true that porting, testing, fixing, and maintaining operating systems has a labor cost, you’re trying to apply standard business logic to something that doesn’t operate that way. Batocera accepts donations, and Rocknix doesn’t even accept any financial compensation. These are volunteer projects, labors of love. They are not subject to capitalistic incentives, and nor is it entirely accurate to call open-source projects like these “products.” The processes involved are more organic, more democratized. It’s a commons, and anyone can get involved.
The reasons they’re designed the way they are is because that’s what fits their motivations and project goals. It’s the appliance model - they want the device to do one thing, and do it well - to play games, particularly retro games. So they put in only enough software to make that happen, and then try to make it as much of a polished experience as possible.
I am only trying to point out that the only thing getting in the way of more general purpose systems being available to these devices pretty much comes down to whether more people feel like trying to compile them.
An increasing number of these devices have touchscreens, so Phosh could work quite well. And for me it’s more about how these devices are leaving a lot of potential functionality off the table. When hundreds of thousands or more people are all using something, you can never predict all the different use-cases they’re going to have. So it’s strange to me that these frontend developers are putting so much effort into turning them into dumb single use appliances, when the entire world of Linux software can just as easily be made available.
But yeah I was thinking about a hypothetical search scenario. I don’t see it being useful for anything more than average local-level forces. Some of them support dual-booting, so those stripped down emulation frontends could come in handy in that case. Have one distro, ideally complete with full disk encryption. Then have another that actually is for the games. If somebody turns the display on and sees it demand a password, they’ll demand further investigation. So they would need to be met with an open menu with an obvious, full list of games ready to play, with no indications there is anything else to search into.
The Retroid Pocket 5 runs Android 13 and I could probably install Signal (or any other Android e2e messaging apps) on it right now. There are also other devices with similar specs and software.
A microphone can easily be added with headphones or earbuds. I’ve updated the post to include relevant info.
I’ve updated the post in response to yours and other comments. No need to rely on poor outdated solutions. Some of these devices, like the Retroid Pocket 5, almost are Android phones just with built in gaming inputs and no cellular chip. I can probably install Signal on it right now if I wanted to, though as it currently is, I would not trust Retroid as a company enough to rely on their firmware.
I’ve updated the post with relevant links and info. My first thought here is that your laptop is not pocketable, and if you were ever in a search and seizure situation, your laptop would be more likely to be one of the first things confiscated.
While a person probably could spin up a very hacky solution on a DS or PSP, there’s really no need to do anything so painful. I’ve updated the post to go a bit more into detail about this.
Maybe? All I know is the other day I used my Debian pc (gnome) to format a usb drive as fat, thinking that’d be the most compatible and hassle free fs for storing and transferring files. Then I got an error that I couldn’t store Champions of Norrath on it because it couldn’t store files over 4 gigs. So for now I just am using ext4.
I wish we could just get one good open, unified filesystem that all OS’s support. It sucks that if I want a usb drive to function on both Android and Linux, I have to format it to FAT. That pos fs can’t even store files over 4 gigs.
I normally prefer copyleft licenses, but this is one case something more permissive seems appropriate.
I mean yeah, I just said above that someone almost killed me. They were probably a human driver. But that’s a “might happen, never know.” If self driving cars are rear-ending people, that’s an inherent artifact of it’s programming, even though it’s not intentionally programmed to do that.
So it’s like, things were already bad. I already do not feel safe doing any biking anymore. But as self driving cars become more prevalent, that threat upgrades to a kind of defacto, “Oh, these vast stretches of land are places where only cars and trucks are allowed. Everything else is roadkill waiting to happen.”