You could swap out the Pixel+Graphene for say a FairPhone+LineageOS. I ran misc-secondhand-phone+LineageOS for over a decade. Still selfhost everything I need. My family have all their photos upload to my nextcloud instance instead of Google.

My switch to Pixel+Graphene is because ultimately the problem is political not technical. A banking app I needed for work refused to run without the real Google services. It also refused Custom ROMs. I tried a lot of tricks. Also GoogleMaps is the only satnav with traffic information in the route planning. There is other things, but Graphene allows you a compromise of running the Google services, but sandboxed.

The problem is not technical, it’s political. Most people don’t understand the difference between a standard and a monopoly. The law makers are asleep to monopolies and the need for competition in the tech world, so have allow this tech dystopia to happen. Some that are more awake know big monopolies are easier to get things like this story from. Multinational corporation are money machines, they won’t really fight for their users. But they miss the bigger picture.

If you care about all this stuff, there is groups like:

https://openrightsgroup.org/

https://fsfe.org/

Maybe also https://openuk.uk/ , though they more work with big tech.

It rules!

It’s vendor lockin. Office file formats are not properly open. There is a “temporary” closed bit that they promised to open to get through ISO, but then never did. The whole ISO thing was a massive exercise in corruption. Let alone the fact the reference implementation is closed. Shame Groklaw isn’t as easy to search and link now.

Their wealth is going to end up with a lot of “stranded assets”.

I don’t need it and neither do the other EV owners I know. But we can all charge at home.

Exactly. I want things, especially expensive things, built to be repaired and upgraded. Not vendor locked and with built in obsolescence.

See, for me, I rapid charge like once a month. All the rest of the time I use my home charger or even a granny lead. 10A granny charging is absolutely fine overnight. But for the size of the E-Berlingo, the battery is a bit small and I know all kind of new batteries are coming. More kWh for the same weight/size, less degradation, safer, etc etc. If I knew the car was designed with battery replacement in mind, I’d worry a lot less about it being obsoleted prematurely. These cars are all black boxed stuck together. It’s not built with repairing and upgrading in mind.

Oh totally, I have a E-Berlingo which basically an ICE converted to an EV, so there is all kind of compromises.

But batteries do improve and an old existing EV can be improved battery. Example: https://evsenhanced.com/aftermarket-battery/

But the economics is much harder if batteties aren’t unique to each EV. (They aren’t completely of course, the guts of my E-Berlingo are shared across a number of others.) EVs, like a lot else, should be designed with maintaining and upgrading in mind. Especially with parts like batteries which are in such evolutionary flux.

Yes and no. No need to hot swap massive EV batteries. Rapid is fast enough. But yes so the EV can be upgraded. The batteries go obsolete quicker than they degrade. So make it so we can swap the batteries and keep the rest running. In fact, just right-to-repair the whole car. In fact, the whole everything!

The problem is when Docker is used to gift wrap a mess. Then there are rotting dependencies in the containers. The nice thing about Debian packaged things is the maintainer is forced to do things properly. Even more so if they get it into the repos.

My preference is Debian Stable in LXC or even KVM for services. I only go for Docker if that is the recommended option. There is stuff out there where the recommend way is their VM image which is full of their soup of Dockers.

Docker is in my pile of technologies I don’t really like or approve of, but don’t have the energy to really fight.

Your probably should if your interested in digital rights. Pretty good author too.

Problem is it is used to clean out copyleft too. Copyleft is a social good version of copyright. Using AI to wash it away, along with authorship, is not ok. Lots of open source wouldn’t have taken over if it wasn’t for stickiness of copyleft breaking “the tragedy of the commons”.

Things that reduce consumption are frequently successful in capitalism. Generally, using less, costs less. There are always those selling a thing who are trying to increase the consumption of that thing, but often at expensive of those selling a competing thing. One successful way of doing that is to be cheaper to buy or run or both, by doing more with less.

However, sometimes we want something to be made with more a bit more to last longer and be repairable.

Raw capitalist won’t do all this on its own. The invisible hand isn’t very good at planning long term. Governments need to structure markets for outcomes they want, and keep measuring and correcting.

Sounds like you were given a mess alright.

The whole point of docker is to solve the “work on my computer” by providing the developer hacked up OS with the app. (Rather than fixing it and dealing dependencies like a grown up)

Bit special for it to still be broken. If it flat out doesn’t work, at all, then it may well be “sunk cost fallacy” to keep working on it. There is no universal answer, but there is a developer tendency to rewrite.

I hope it continues to be a non issue for you. Without you having to take any measures. Just saying it can be an issue. Search “zigbee 2.4ghz wifi interference” if you don’t believe me.

Programmers love to rewrite things, but it’s often not a good idea, let alone good for a business. Old code can be ugly because it is covered with horrible leasons and compromises. A rewrite can be the right thing, but it’s not to be taken lightly. It needs to be budgeted for, signed off on and carefully planned. The old system needs to stable enough to continue until the new system can replace it.

You have any 2.4 GHz WiFi problems? In theory there is a problem, and I know a dude with a lot of ZigBee and a lot of 2.4GHz problems, but without going over with work equipment and spending some time doing work for free, I can’t be sure it’s ZigBee. It’s just my best guess.

You already married to ZigBee? If not, maybe don’t. It causes 2.4Ghz interference. You’ll need to think about WiFi channels and avoid ones that overlap with ZigBee. Either that, or use 5Ghz WiFi and repeaters to make up for the lower penertration (if an issue).

Academic. The EU has already done it and so we in the UK already have it. Our market just isn’t big enough, relative to it’s locality, to do something different. Whatever the EU does just washes over us. Only now we have no say in the what that is or how it is implemented.