Regarding Android Auto being slow, it could just be due to your phone. It has to stream the whole interface as video to the car's infotainment system over USB (or Wi-Fi on newer models), then handle taps and stuff that it receives back, if you're using an old or budget android phone then that can be pretty laggy.
You have to choose one timezone to be authoritative here, which one you choose depends on the situation, but if you don't choose one, then a change like the one happening in BC will cause the consumer and provider to be using mismatched times.
If the consumer booked something for 12PM Dec 1 2026 PST, and this booking was made before BC's changes were announced, and the provider saved this using their local time (say EST), then they would have saved it as 3PM EST. But now with BC's changes, when the consumer shows up at 12PM their time, that will be 2PM EST, an hour before the provider was expecting.
Was the consumer correct for showing up at the booked time according to their wall clock, or is the provider correct with their saved the time that was an hour later? The answer probably depends, but whichever you choose is the authoritative time.
Another comparison: if you count the "solar system" as ending at Neptune's orbit (obviously it extends much further, but just for the sake of comparison), then you could fit ~4465 "solar systems" in between our sun and the closest star, Proxima Centauri.
There's also the Openbu or LanBu android apps if you just want a basic app for monitoring from your phone like Bambu Handy did. Although if you want to access your printer from a remote network you'll still need tailscale or similar.
I have no issues with OrcaSlicer and interacting with my printers or starting prints remotely as long as I have LAN and Developer mode turned on. The only catch is that you need something like Tailscale set up for remote printers so you can access them over your "local" network. You can also get remote management/monitoring on your phone with apps like Openbu or Lanbu.
"they" being Huawei, and their phone suffers from the same problem, the main display can be easily damaged by dust, dirt, or just your fingernails pressing into it. Notably Samsung's trifold kept the folding display entirely inside when folded, presumably to avoid this problem.
The whole display is plastic, including the part on the front that doesn't wrap around. Yes the part behind the glass panel on the back would be protected, but the front of the phone wouldn't be.
Additionally, the flexible screen is on the outside which will quickly get damaged since it is made of soft plastic. It's too fragile for something that lives in your pocket every day. All modern foldables have the folding screen on the inside to keep them protected, and a standard glass screen on the front.
I assume this will just be using Window's dynamic refresh rate feature, which you can turn on and off in the display settings, and when it's off you can set the refresh rate manually. I guess the question is whether they will let you set it as low as 1hz manually though.
All your comments are painting archive.today as an innocent victim in all this, but in addition to the DDoS, they have been caught modifying archived pages as well as sending actual threats to Patokallio [1] which in my opinion seem far worse than the "doxxing".
Just the fact alone that they modified archived pages has completely ruined their credibility, and over what? A blog post about them that (a) wasn't even an attack, it is mostly praising archive.today, and (b) doesn't reveal any true identities or information that isn't already easily accessible.
From my perspective at least, archive.today seems like the unhinged one, not Patokallio.
There are only two posts about archive.today on the blog, and one of them only exists because archive.today started DDoSing them. I fail to see how you could consider the entire blog to be a "harassment campaign", especially considering that the original blog post isn't even negative, it ends with a compliment towards archive.today's creator.
I believe that is why "escalating safety" and "secure" were written in italics in the comment. Those are the terms Google would use, not necessarily the truth.
Are you saying that opting for a beyond burger patty instead of a beef patty is going to "poison and destroy" your health? That's a bit of a stretch no? Are they really any worse for you than a regular burger from a fast food joint or something?
"here" in that comment is not referring to any specific scenario. It is referring to the problem discussed in the sentence immediately following it, that public prediction markets can shape the outcome of the events they are predicting.
The "magic" of React though is in its name, it's reactive. If all you're doing is creating static elements that don't need to react to changes in state then yeah, React is overkill. But when you have complex state and need all your elements to update as that state changes, then the benefits of React (or similar frameworks) become more apparent. Of course it's all still possible in vanilla JS, but it starts to become a mess of event handlers and DOM updates and the React equivalent starts to look a lot more appealing.
Transcribing locally isn't free though, it should result in a noticeable increase in battery usage. Inspecting the processes running on the phone would show something using considerable CPU. After transcribing the data would still need to be sent somewhere, which could be seen by inspecting network traffic.
If this really is something that is happening, I am just very surprised that there is no hard evidence of it.
The vast, vast majority of Windows users don't know their laptops are encrypted, don't understand encryption, and don't know what bitlocker is. If their keys weren't stored in the cloud, these users could easily lose access to their data without understanding how or why. So for these users, which again is probably >99% of all windows users, storing their keys in the cloud makes sense and is a reasonable default. Not doing it would cause far more problems than it solves.
And the passphrase they log in to windows with is not the key, Microsoft is not storing their plain text passphrase in the cloud, just to be clear.
The only thing I would really fault Microsoft for here is making it overly difficult to disable the cloud storage for users who do understand all the implications.