

Forbidden take
Forbidden take
I thought this article was complaining about something that no-one used, but here you are recommending alternatives… alternatives that are not curl
Your reply implies the article is critical of this, but it isn’t
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.
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.
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…
I typo’d “undirected” if that affects anything.
My point is, people talk about this as if it’s the plants having a nice chat and a cup of tea and talking about politics. It isn’t - it’s more like a dog being able to smell some dog piss and understand something about the dog that pissed there.
What other understanding of sentience would we fucking use?!
The mycelium network thing is way overblown - it allows some crude, undetectedundirected signals to pass.
The administrative overhead and the overhead of engineering everything to with multiple vendors is what is massive
Dividing between providers is not what people would be doing if the resilience of cloud services were as is being memed about.
Doing so is phenomenally expensive.
I don’t believe it’s easier than rsync
.
If you want to know more, look up Multiple Round Simultaneous Impact
It’s easier to just refer to “multiple round simultaneous impact” than to try to explain succinctly, especially since I already got the term kinda wrong (time on target is more of an umbrella category/earlier version)
That is not how this concept, time on target, works
The diagram is about normal unpowered shells. They use different amounts of propellant to achieve different projectile speeds
New matter being created with extremely low probability fits perfectly with our observations.
On these scales, the accuracy of our observations should reduce our confidence though. It doesn’t make sense to confidently say that, in 200 trillion years there will be no stars, because our observations of the rate of new matter creation (approximately zero) have a margin of error which allows for there to still be some
But… they’re sharing an image? Where else would you like it to go, in the EXIF metadata?
Like in a radio advert, you just remember the URL and type it in!
I’m trying to make “twinkle twinkle star-whose-angular-size-from-earth-appears-small” scan but it’s proving a challenge…