Aaaaand... still down a day and a half later. Moved to another provider yesterday but was curious and checked back. No acknowledgement of the issue, no status update, no blog post, no twitter post.
In early 80s when I was a wee nerd in college a gentleman named Ray who owned Laboratory Microsystems was nice enough to give a poor college kid a copy of his excellent Forth implementation for the then-nascent IBM PC.
I breadboarded a little EPROM programmer (driven by a parallel printer port with the programming code done in Forth because I couldn't afford a real one). Then breadboarded implemented a little Z80 system with a bunch of general purpose I/O and a Forth "OS" in EPROM.
Used that little setup as the basis for a number of projects, including a home alarm system with phone-based control plus voice synthesis phone-based alert calling (which a couple silicon valley VCs were gracious enough to take a meeting about).
Forth gave me wings. Despite it's reputation as a "write-only language". Good times.
Saw your link, did your test and here's my feedback.
No "share" or "download" button in the app? Sure, "apps are cool" and all that - but what about folks who want to archive or share their health data? AFAIK literally no provision to share all those nifty biomarkers with my doctor (except many, many screenshots)?
Nowhere in the "how to get blood test" email instructions does it bother to mention a urine sample will also be needed. Kinda useful to know if you should not pee right before heading to the lab.
A few comments claim the sensors can be triggers by non-smoking events such as hairspray, nail polish remover, perfume...
If that is accurate it seems to me one could exploit that sensor flaw by purposefully triggering a false positives with some benign action - and video record doing so - perhaps a couple of times.
Then if and when smoking is alleged, obtain a log of the alleged event times, then provide video evidence that debunks at least one alleged smoking event.
A relatively small number of activists could probably create a viral nightmare for Hyatt and anyone else implementing this system.
Yet more glossy 'form over function' nonsense from Apple in my opinion. Was hoping '26 would be the release that tackled their massive technical debt around broken/reduced functionality. I did see a Reddit post that summarized it nicely, a screenshot of a Youtube video where the play button overlaps the name so it reads Liquid*ass
Yes, cant even access https://dashboard-next.heroku.com/ so the problem seems broader than what they describe on their status page which seems to imply only issues related to updating DNS settings.
Email received today: "One of our updates involves how disputes are resolved between you and Amazon. Previously, our Conditions of Use set out an arbitration process for those disputes. Our updated Conditions of Use provides for dispute resolution by the courts."
And in the conditions themselves: "We each waive any right to a jury trial."
There ought to be a "emergency shutoff" threshold, period. And there's just no customer-centric excuse for not implementing it after these many years.
Here's how to implement it:
"Amazon, what do you do today if my credit card fails and all the retries fail?"
Do THAT if billing hits <my emergency off switch threshold>.
Will it disrupt the heck out of all my AWS services? Of course. That's the point, if something went so seriously wrong that my billing hits an absurd level that will put me out of business, I'd rather have downtime.
Best general explanation I've seen so far, thanks for posting the link.
Unfortunately, it still completely sidesteps any discussion of the relative risk of a vaccinated person (who is protected from a severe infection themselves) still a) getting infected and b) causing a severe case in someone else who is not yet vaccinated.
So while "efficacy" may not be relevant on one dimension (MY chances of severe infection) it still seems important in another dimension (the chances of ME nonetheless getting infected then giving a severe case to someone else).
> It shocks me that so many people want to run Docker on a platform it was never built for.
Yet, it works, and well, your shock notwithstanding.
If your goal is a SINGLE portable, virtualized platform for your developers, which does not require a persistent internet/SSH connection, and which is "fast enough" for developers to be effective, Docker on Mac is a pretty swell solution.
Thats IF your local Apple store is even taking appointments; none on Oahu are. Plus there's apparently significant parts delay no matter where you get the repair done.
It took Apple 32 days to get my MBP 16" repaired, returned under Crapplecare.
As annoying, to me, is that Godaddy lets you go through the entire transfer process without TELLING you it's going to be rejected.
So you have to the transfer get it rejected, THEN turn off privacy, then do it all again.
On the other hand, that just makes it that much sweeter once the domain finally lands at Route53 (etc) and you no longer have to play Godaddy Renewal Roulette and wonder if your next renewal will be 50% higher than normal.
(Oh, and BTW, I was happy to see that if your domain registration is a company, Route53 does quasi-private registraiton at no extra cost.)