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.

Not sure myself, I’m trying to get into some IT jobs (not necessarily programming) that aren’t anywhere near social media and are more focused on internet infrastructure, but getting any job is hard when you’re starting out and I would like to avoid the evil ones at all cost.

But just as there is no ethical consumption in capitalism, there’s no consensual work, so the values of wherever you end up working won’t align with yourself or the other workers fully, it’s just a question of degree.

Hmm, you could probably extend the protocol to do eventual consistency across instances if that ever becomes a problem, remote instances could keep their own counts and only send aggregated updates.