I wonder what the drawbacks of standardizing a GET body would have been. CoAP already has it (which creates friction in building CoAP<->HTTP proxies).
All in all, I dislike the overall focus on the HTTP method when designing "RESTful" interfaces. If all we're building is, effectively, an RPC, why would the cacheability meta-information be the first thing we specify?
Please do write an article! I've wanted to get into reusing old android hardware for quite some time now, but never knew where to look for good instructions to get started. Especially PostmarketOS seems very interesting, but rather underdocumented in some places.
When I was at school in Germany, I read both "The Cloud" and "The Last Children of Schewenborn". At the time (I'm young), I was also reading the ".ausgestrahlt" (a quarterly anti-nuclear magazine) right around the time the Fukushima disaster happened.
As is obvious, I was anti-nuclear myself (and still am, to a degree, but not related to fear of radiation). Looking back, it's clear to me, that there was little scientific understanding, but much fear, of the danger of radiation in the anti-nuclear movement. The books catastrophizing nuclear meltdowns and nuclear war certainly didn't help. The interesting aspect, to me, is, that the effects of radiation are correctly and quite graphically described in the books, but overly exaggerated in proportion and scale.
Being against nuclear power provides a shared identity, a sense of righteousness and there are other strong groupthink effects. Putting things into context gets really hard when everybody is either constantly reinforcing your biases or, alternatively, obviously shilling for the nuclear industry (which I also did see a lot of!).
It seems to me that the anti-nuclear movement is currently dying off. The recent protests against transports of used-up nuclear fuel have been rather small. Since Germany decided to phase out nuclear energy, there hasn't been much of a reason to protest against it and attention has shifted to other matters.
esim.me, 9esim and "sysmocom eUICC for eSIM" are eSIMs in the SIM card form factor that you can load the SIM profiles onto and use them in any device with a SIM card slot (and of course transfer between devices). In my opinion, that's the best of both worlds.
Technologically, eSIMs are pretty nice. The electrical interface between the phone modem and the eSIM is the same as with a real SIM card, and the eSIM can run the same applications as a real SIM card, so at this point you can buy smartcards that can be swapped between devices and run eSIM applications. esim.me, 9esim and the "sysmocom eUICC for eSIM" (seems to be the most open/friendly at this point) are some of the options. Most of them offer an app for management, but there are also standardized interfaces.
SIM cards have always been secure elements that the provider trusts. With an eSIM, you can already own that secure element and the provider can provision it with their application. You can even have the applications from multiple providers on the same physical secure element.
The major advantage is now that the expensive and time-consuming part of provisioning a new mobile service (sending out a physical SIM card) can be replaced with a few standardized API calls. This is cheaper (which makes the extra cost some providers charge for an eSIM look quite silly) and a lot quicker, which enables new business models for short-lived cell connection services.
A world where all cell service providers offered eSIMs would be slightly nicer. But manufacturers removing the option of swapping the secure element is very annoying at the same time.
My last interaction with the German medical system was about lyme. The doctor I consulted didn't think it was lyme at first (apparently, the rash isn't always circular and it doesn't always move). If you know you have been bitten by a tick and later you get an unexpected rash (significantly more than usual), go see a doctor (or two, as I learned).
Also: Amoxicillin is better than its reputation. Three doctors might literally recommend four different antibiotic dosages and schedules. Double-check everything; your doctor might be at the end of a 12-hour shift and is just as human as you. Lyme is very common and best treated early.
I have an unusual EV made by a relatively small company of which only a handful got to private customers, so if I want to fix something, I have to reverse-engineer it first. Most of the time, I will find out that the components used in my vehicle were also used in other cars.
Regarding the difference between EVs and ICEVs, only the powertrain components are relevant and between those, some are more exchangeable and some are less so.
As with ICEVs, most manufacturers have "platforms" that are shared between multiple makes/models. Having shared components with other vehicles of the same platform is the rule rather than the exception.
In the cars I have seen, the whole battery often only fits that specific model, sometimes also for other cars within the same platform. The modules that make up the battery are often exchangeable with other cars made by the same company/group. The cells that make up the modules are almost always generic, but very hard to replace. The battery management system is usually specific to the battery.
I don't know about the current state, but for early EVs the motor and inverter (which converts battery DC to AC for the motor) were often made by external suppliers. Especially EV variants of otherwise ICE-based vehicles like the Fiat e500, VW Golf/Jetta, and some french cars all use the same motor and inverter made by Bosch. If an inverter is connected to a different type of motor, it needs to be tuned for it which is not trivial.
Onboard Chargers (OBCs), that convert AC line voltage from AC chargers to battery voltage are often quite generic and developed and manufactured by suppliers. They are almost always interchangeable within the same platform, but I haven't yet seen completely unrelated OEMs use the same OBC. The same applies to fast charging communications equipment, which is often integrated into the OBC.
DC/DC converters (the alternator equivalent) are rarely separate components anymore and often integrated into either the OBC or the inverter.
Voltage-wise, all these components are often surprisingly flexible and can be used with much lower voltages than their maximum rated voltage.
Other components like contactors and connectors are very generic and I haven't yet seen one that only one OEM would use. There are likely exceptions to this. Often, the base components like the OBC or the inverter are almost identical, only using other (also generic) connectors.
While technically all these components could be replaced in the "old school" style, almost all of them require either coding the components to the specific vehicle, or flashing an OEM-specific firmware. While the former is only doable with OEM-specific software (that is far too expensive for both indiviuals and most independent workshops), I haven't yet seen any example of the latter, at least not for swapping components between unrelated platforms.
As of now, there are almost no "official" aftermarket replacements for these major components. I don't know of any major supplier that will directly sell parts in small quantities and OEMs likely won't sell you as an individual replacement parts either. For DIY repairs, finding used parts from wrecked cars and coding them with cracked software or having it done in an authorized workshop (if even possible) often seems to be the only option so far. Also, everyone will discourage you from working on your EV for "electrical safety" reasons (actually, it's more profitable if they do the work). Working on an EV is quite safe, if done right (which is not hard).
Most of these limitations do not only apply to EVs, but to almost all modern cars. Often, the necessary work of reverse-engineering and cracking software has already been done for ICEVs for tuning purposes.
All in all, I dislike the overall focus on the HTTP method when designing "RESTful" interfaces. If all we're building is, effectively, an RPC, why would the cacheability meta-information be the first thing we specify?