Mmm. Given that you didn't bother reading the article in order to have the context to respond to, I'm not inclined to take your word for it over the source.
The article even takes theft of a Picasso as an example. In that case you know it's not being stolen to melt down. That's not the case here.
For your first (long) journeys, definitely plan in advance. And don't rely on searching at a certain SOC without scoping out the frequency of chargers on your route. Where I am, this would never be a disaster, but it may end up with having to take a long detour, or being stuck on a very slow charger to be able to make progress. I guess you're in Germany, where I don't know the situation - probably decent. But there will be less densely populated areas which may still cause issues. In North America there are major routes with no chargers for more than a hundred miles which then requires a lot of care.
What I'm just getting it is that this level of care is often not necessary once you're familiar with an area. And then perhaps the impetus for OSS solutions is lowered.
“Stolen to order is something from the Hollywood movies,” he said. “Nobody would touch this. It’s all around the world and in all the newspapers. If you buy this, if you get caught, you end up in prison. You cannot show it to your friends, you cannot leave it to your children.”
I am (still) reading The Scar by China Miéville. It's dead-tree edition which means I read it slower than otherwise.
I agree with flesh man
sorry I was talking imprecisely; I meant "extra steps" in the code, rather than as a practical workflow to follow.
For now I just use ABRP. It may be different for you, but I find that most journeys I do I only really need consider a subset of chargers - we are aiming to stop approximately every 2h to change drivers as my partner starts gnawing on the steering wheel before then. Those stops suggest a rough geographic area in which to look for chargers, and very often there are chargers exactly where we are stopping anyway. So I no longer feel like I need a really solid route-planner.
A model for energy usage at various speeds that you can apply across a route would still be really useful - I still use ABRP to tell me whether I can make a certain distance from a given state of charge. This will then probably not be as good on open data, as I don'tthink there are good open datasets for average traffic speeds (given time of day). The car's own model of this is somewhat opaque so I don't trust it too much.
If you can block access to commercial VPNs and render anyone else using VPNs liable to prosecution you achieve what they want.
This comment could go on any Calvin and Hobbes strip, but I just got a memory of getting the 1996 Collection as a family at Christmas and reading them all, when I was a kid. I felt immersed in a world like my own but slightly more adventurous - I would imagine that I could go and ford the river down in the woods, or ride a red cart down hills, even though I never did, and we hardly ever got enough snow to go sledding.
I mean literally noone is born lactose intolerant. You'd just starve.
Genetic lactose intolerance develops some time later through a variation in gene expression. But the effects of lactose intolerance also vary more than that, because if you continue to consume milk your gut biome changes to reflect the abundance of nutrients.
I don't know of one, but it sounds like something that could make use of the route-planning ability of Osmand with extra steps...
Ok, and how are you going to tell people that it exists? Not through YouTube sponsor slots, because you'll get deleted quicker than you put it up.
So only a tiny number of people will know that your VPN exists. That's "good enough" for the censorious.