xmddmx

^F Latency - no hits found.

Latency is one metric by which computing has gotten noticeably worse over the years.

Daily, I encounter multiple situations in which I take some action (click a button, type text in a text field, etc.) and the response is visibly delayed - from several hundred to several thousand milliseconds.

This used to happen only on websites, but lately is also happening on apps installed on my computer. The cause? My theory is that everything is now some sort of monstrosity of React or similar web app, running inside a browser process, and possibly even that local apps are sending data round-trip up to the mothership for tracking, surveillance, synchronization, etc.

And the UX is terrible - often while this is happening, stale data is showing, or there is no visual indication a process is underway.

Agree. And this is all made worse by the fact that there seems to be a bug in iCloud keychain syncing - I can change the password on my mac, verify it works, but when I go over to iPhone or iPad, the old password is still being used. Not sure if there's a way to force the sync process on both ends?

Sure, but it also took them 7 hours to email their own customers on the email infrastructure run by DreamHost themselves. Since they run the IMAP and SMTP servers, seems like they could have done that in seven seconds.

Of course, if they are nuking everyone's email password that doesn't help for notification purposes -- but as of this morning, all my email logins are still working fine, so it seems they didn't actually do that? Confusing.

Super displeased with DreamHost's handling of this. I have multiple master accounts. One of them got the email around 12pm today (over 48 hours after the incident started) saying...

"As a precaution, we have expired the passwords for some email and FTP/SFTP users on your DreamHost account. Their old passwords no longer work, and no new password has been set."

But none of those email passwords were actually expired - all were working. This is confusing - did they only expire passwords that were under threat? If a password wasn't expired, should it be trusted?

The same email suggests you change all email passwords you control.

Another account received no email warning from DreamHost so I assumed it was fine, but 7 hours later it also received the same generic email.

My complaints:

- sucks that it took them 48 hours to identify the breach - perhaps understandable

- but once the breach was identified, how the fuck does it take them over 7 rolling hours to email their customers? That's terrible.

- confusing messaging: DreamHost are claiming that passwords are expired, but in testing multiple accounts, all of them are still working. Do I need to rotate these? (I probably will just for safety).

I'm a 25+ year DreamHost customer and generally satisfied, but this feels like amateur hour.

If only Apple computer had employees that would fix this system (that they are 100% responsible for building) :-)

Even if Apple is too cheap to pay the $0.00001 to get me real time temperature updates, you would think there would be an OS API to query the temperature, and that the various apps and complications would query this to get the source of truth.

But from the actual UI/UX, it must be that every App, and complication, and UI element are caching their own value.

That's the only way I can explain seeing 3 different temperatures displayed within a few seconds.

(NB: these are all Apple apps, I'm not using any third party apps)

Right, that seems to be what is happening.

The question I'm asking is "why" - why would Apple ship code that is so horribly broken (from a UI/UX) perspective.

I thought for sure that this slow-temperature-update bug would be fixed in WatchOS 27, but it's just as bad as in 26 and before.

Sometimes the temperature UI will show "--" instead of a temperature, until it finally updates, so clearly they do have code for the "no temperature data" case.

It just boggles the mind that "6 hour stale temperature data" doesn't trigger this same behavior.

I've seen bugs like this which have led me to wonder if apple has a problem with generating UUIDs which aren't really unique.

It's the only way I can explain some of the totally bizarre Siri (and other iOS and macOS) bugs.

Agree - I've had almost all of these problems with Siri.

Another thing I've noticed is the horrible lag with updating the UI. An example: On Apple Watch I have the temperature complication bottom center. It sometimes shows the current temperature, sometimes it hasn't updated in minutes or hours (bug #1). For example right now, it shows 66 which I know is incorrect. I tap it to go to the Weather app, a different temperature will be shown (56) (bug #2) and then about 10 seconds later (bug #3) it finally updates to the actual temperature (72).

If I go back to the home screen, finally the complication shows the correct temperature (72).

These kind of async refresh bugs are not unique to WatchOS, it's endemic throughout the Apple ecosystem.

Why? Is this poorly coded JavaScript web view apps? Is this React? Some sort of other async framework that works fine when you are testing on the Apple campus but doesn't work in the real world?

Would running the unit in Fahrenheit improve the sensitivity?

Even more confusing. Do we know which data is in which keychain?

Disturbing if true, as it suggests my "everything" backups aren't really full backups at all.

I wonder, if you have enabled iCloud keychain, does that provide another way to get your passwords back?

Suppose my MacBook is stolen, but I still have my iPhone. Could I use the passwords app on the iPhone to retrieve my passwords. Would that include all of them or only a subset?

Another way (which happens to be correct) to say tenth of a second is 100 000 000 (one hundred million) nanoseconds. You were off by a factor of 1000!