How so?
4,359 karma · joined October 7, 2020
How so?
Whether that is more or less efficient than a zero-power coast followed by some kind of braking exactly at the end... I assume the difference is so tiny that it makes no difference.
Unless you spend upwards of 40% of your battery daily, you'll be good.
If you own a parking spot in your apartment complex, and depending on your jurisdiction, you can install your own charger.
Even if the idea doesn't outright gain traction, enough insistence will shift the overton window.
Navigate to a website of your choice [1]. Let's assume its privacy banner is served by onetrust.
The text at the top of their "Privacy Center" says, verbatim, "We share this information with our partners on the basis of consent and legitimate interest. You may exercise your right to consent or object to a legitimate interest"
If you then unfold the "Manage Consent Preferences" you will notice that you can, _separately_, provide your consent for a given purpose, by sliding the switch to the right to enable it, and also, _at the same time_, "Object to Legitimate Interests" by clicking on the button labeled so.
Of course, this is a dark pattern to make it as cumbersome as possible to object to Legitimate Interest purposes.
[1] (I took vox dot com as an example.)
The outage was never about renewables, it was caused by bad dispatch of reactive power.
https://www.abc.es/espana/andalucia/cordoba/via-l10717-salto...
Does this mean a guy is running new separate physical wires every time a new tenant joins?
The root cause was insufficient dispatch of reactive power due to non compliance of some power providers, and ultimately traceable to outdated procedures for the dispatch of reactive power.
Whether that principle should have been sustained in the special case of "B = localhost" is a valid question. I think the consensus from the past 40 years has been "yes", probably based on the amount of unknown failure possibilities if the default was reversed to "no".
Spend that money in reorganizing your management and training your staff so that everyone in your company is onboard with https://owasp.org/Top10/2025/A06_2025-Insecure_Design/ .
Something is seriously wrong when we say "hey, respect!" to a company who develops an unauthenticated RCE feature that should glaringly shine [0] during any internal security analysis, on software that they are licensing in exchange for money [1], and then fumble and drop the ball on security reports when someone does their due diligence for them.
If this company wants to earn any respect, they need at least to publish their post-mortem about how their software development practices allowed such a serious issue to reach shipping.
This should come as a given, especially seeing that this company already works on software related to security (OpenAuth [2]).
[0] https://owasp.org/Top10/2025/ - https://owasp.org/Top10/2025/A06_2025-Insecure_Design/ - https://owasp.org/Top10/2025/A01_2025-Broken_Access_Control/ - https://owasp.org/Top10/2025/A05_2025-Injection/
Also, you seem to skip other notable changes like enforced spam and enforced Copilot and enforced online registration.