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

Nicely implemented screen layout. Curious if you've thought of reporting metrics showing how many guesses it's taking people? (I got 'volatile' in 9)

I have a decade's worth of guess statistics per word.

Unfortunately, I just converted it to a frontend-only app to eliminate hosting costs, so I have no good location to keep tracking these stats.

Theoretically, "Oxford English Dictionary estimates that there are around 171,476 words currently in use in the English language", the log2() of which is around 17.38 - I have no historical data for 'volatile'

Hmmm, but the shortened dictionary being used is presumably less than that, so my best-so-far of 17 is probably below optimal...

Their hosted Exchange email has been having "issues" since December.

But today their "Rackspace Email" (hosted Webmail/IMAP/POP/SMTP) has been disrupted since 2pm ETS.

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.

At one point, I owed a balance of $0.57 to AWS and started to get warning emails about my account being suspended. Just out of morbid curiosity, I waited to see what would happen.

2.5 years later, after dozens of automated mails, they finally suspended it.

The challenge is that there is a lag between consuming the resource and counting the price.

Seems like yet more "let perfect be the enemy of the good" thinking.

If you want a cut-me-off set to $X, and some lag might allow charges to reach X+Y before the cutoff took effect, which is the customer-centric answer:

a) don't offer ANY cap, simply let the customer's out of control charges just keep racking up to catastrophic levels that put them out of business?

b) cut it off as soon as you DO detect it exceeded their cut-me-off threshold even if by that point it has reached X+Y?

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).

Great little story!

> 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.