Enderboi

And that dedicated soul (dreammaster) would really like to know who wrote the final star map puzzle, because there was sooo much matrix math his head almost exploded :)

This is the comment I came here for :)

We first discovered this while troubleshooting why we were receiving logins with an old password.. after updating the settings in Outlook. They had no other email clients, but the 'New Outlook' didn't actually send the updated password to the Microsoft cloud due to a bug :P

Imagine my surprise discovering that this little banner in their Outlook settings that said "Using Microsoft sync technology" actually means "This is no longer really a local IMAP client".

As an email host... I've been turning New Outlook off for clients for weeks trying to explain this.

Apart from the security issues, it's also very annoying to have to explain that I can't actually troubleshoot any IMAP connectivity issues when your machine isn't the one thats actually making the connection.

Now we've been internally discussing whether we should just firewall off whatever Azure ranges are connecting to our IMAP backend servers and intentionally "break" the functionality. Not my first choice, but users keep seeing the "New" toggle and turning it on, causing all sorts of other uncontrolled chaos!

Cloud-first, in all the wrong ways. It's supposed to be a local app..

But my Commodore 16 probably still doesn't have enough memory to run this :)

Back to playing Berks I guess :P

I often have people complain after comparing my works instance pricing to other cloud providers...

Then try to explain that rotating a few dozen TB of data offsite to cold offline storage every week isn't cheap. Because unlike some vendors, we take pride in data integrity and ensuring that our DR plan is actually.... you know, recoverable :P

Literally just deployed a pair of new OmniOS NFS servers last night, for high-availability hosting. We also serve VM storage from a pair of Illumos ZFS boxes over iSCSI.

We switched most of our primary NFS storage pairs from Linux to Illumos a good five years ago due to a bunch of locking issues and race conditions with high-volume NFS traffic. Solid as a rock as long as you have the right HBA heh

FTA: // Infallible: We've definitely consumed 4 bytes

... erm, wasn't the original issue created by an undocumented change to File API semantics?

Not that I know how their backend works, and I'm sure their consume function is all super robust with every edge-case possible covered in the test suite..... but "Infallible" oh dear... :P

Ah the good ol' New Direction announcement.

Immediately following this was one of the most chaotic times to ever post on an LambdaMOO ARB (Architecture Review Board) *Ballot.

(Mines the one with the prog bit stucking out of the pocket, and 50 poorly parented instances of yduJ's Rubber Duck Tutorial in my inventory).

I was more of a TRSI Demo Maker kinda guy :)

First, tell Nokia you intend to contact the ACCC about this refund, as the device isn't "fit for purpose" if it can't store files greater than 4GB.

If they don't instantly change their tone (as many vendors do once you mention certain four-letter agencies like ACCC or ACMA...), then lodge a complaint with the ACCC.

Ingram in this case are just acting as a warehouse/drop-shipper, same as they do for Microsoft and various other OEMs.

... although our (Australias) Data Retention and 'Lawful Access' legislation is crap, at least the Consumer Guidelines still generally favour the public! :)

Phew.

I'm happy they're just discontinue the free Cloud version, rathert than changing the licensing for On-Prem :)

... better than Atlassian!

Every few months I keep telling myself I need to buy one of Cliff's Klein bottles to go alongside my (very dogeared) paperback copy of The Cuckoo's Egg :)

Learning all the default VMS passwords definately didn't get me in trouble during High School with the state's herd of Vaxen... I mean the book was right there, in the library! Wink wink :P

This bot is stupidly broken - we've had to block a whole swathe of Azure ranges on our load balancer.

This particular 'bot' would start crawling in-line Javascript on a customer site, and then get stuck in an infinite loop requesting things like:

  /page/window.open
  /page/window.open/page/window.open
  /page/window.open/page/window.open/page/window.open

We opened an abuse report with Microsoft last week, but haven't really heard anything back. Over 500 IP addresses involved hitting dozens of our hosted sites, le sigh.

Unfortunately, we do see enough legitimate requests with that UA that we had to resort to the IP blocking. A bunch of /16's and a few smaller ranges... it feels dirty :(