Ariel Millennium Thornton @arielmt@computerfairi.es

@mavica_again Looking sharp! 💜​

It seems I'm late. The spam only just now found me.

Google's answer: "Manage invitations in Calendar: Control who sends invitations to your Google Calendar.", https://support.google.com/calendar/answer/13159188

👩​ -( The directions seem reasonable? )

Microsoft's answer: "Calendar Spam Entries", https://learn.microsoft.com/en-us/answers/questions/5904267/calendar-spam-entries

🤦​

🤦‍♂️​🤦‍♂️​🤦‍♂️​

🤦‍♀️🤦‍♂️🤦🤦‍♂️​🤦‍♀️​🤦‍♀️​🤦​🤦‍♂️​🤦‍♀️​🤦
🤦🤦‍♀️​🤦‍♂️​🤦‍♀️​🤦‍♀️​🤦​🤦‍♂️​🤦‍♀️🤦‍♂️🤦
🤦​🤦‍♂️​🤦‍♀️🤦‍♂️🤦🤦🤦‍♀️​🤦‍♂️​🤦‍♀️​🤦‍♀️​

I got a fake Geek Squad invoice, but instead of it being in the body of the email spam, it was in the description of an event.ics attachment. This isn't the first spammy event.ics attachment I've received recently. This is the new spam vector?

*quick event.ics search*

Wait, what? Do Microsoft and Google really add emailed event invitations to email recipients' calendars automatically? No recipient interaction required?

🤦‍♀️​

It's the ber of septem.

Twenty days until the ber of remem. 🎺​

Two bits of breaking news have reached my desk.

First, MapQuest is still a thing. It's owned by an ad firm now, but uBlock Origin works, & your parents can still print directions from it.

But more recently, MapQuest has refused to recognize Trump's powerless order changing the name of Lake Ontario.

Business Insider, 2026-08-27, "The 'OG' online map platform, MapQuest, says it won't change the name of Lake Ontario": https://www.businessinsider.com/mapquest-wont-rename-lake-ontario-lake-america-trump-canada-tariffs-2026-8

@mavica_again "No, I said 'borgs,' not 'bugs.' 'Borgs.'"

Suddenly remembering the one loose thread Star Trek never tied up: The Next Generation, season 1, episode 25, "Conspiracy." Yes, the one about the stop-motion creepy crawlies taking over Starfleet Command, and with the graphically gory third act.

@JennyFluff A microburst is what microFarad capacitors did during the Capacitor Plague.

I still think MDN should add a column for SeaMonkey in its browser compatibility list tables, but I now know the workaround:

Since 2.53.1, the SeaMonkey release notes say it uses the same back-end as Mozilla Firefox 60.x.

So if the browser compatibility number in Firefox's column is 61 or greater, then there's no support in SeaMonkey.