Here's your moment of Zen for the day (2 of 3, pick the one you like best). Sound up! You'll have to imagine the ocean air, I can't post that.
#Ocean #Beach #SalisburyBeach #Massachusetts #MomentOfZen

Here's your moment of Zen for the day (1 of 3, pick the one you like best). Sound up! You'll have to imagine the ocean air, I can't post that.
#Ocean #Beach #SalisburyBeach #Massachusetts #MomentOfZen

“But if there are no Cybertrucks anymore, how will I know whom not to date when I grow up?”
How to Talk to Your Child About the Cybertruck’s Demise - The Atlantic
https://archive.ph/Wl9rx
#humor #funny #Cybertruck

There are a lot of things Dems should do for the next two years, but one of the most important is to pass bills that we need even if Trump vetoes them. Make the GOP publicly vote against what people actually want over and over, against the bills and against overriding Trump's vetoes. Then the Dem presidential candidate in 2028 can point at all the bills and say "Congress will pass all these laws again when I'm president, and I'll sign them all." And then they should do that too.
#politics #USPol

I'm working the polls today in #Boston, and now, my lunch break, is the first chance I've had to post since the polls opened. Very busy, lots and lots of people voting. I hope that's what's happening everywhere!
#BostonMA #politics #USPol #voting #vote

A scammer registered a typosquatting domain mimicking my employer's and started sending out emails impersonating our head recruiter, offering people fake job interviews / jobs.
After a lot of effort we managed to get the domain suspended, and the scammer moved on to another domain.
I'm thinking about what to put as the "root cause" in the post-mortem for this incident.
#infosec #breach #postMortem

Yet another example of why we do not want or need #GavinNewsom in 2028.
https://techcrunch.com/2026/10/01/california-governor-vetoes-bill-banning-use-of-pervert-glasses-to-secretly-record-people/
No-adwall version: https://archive.ph/Q5Xif
#privacy #politics #USPol #CAPol #PervertGlasses

I’ll give DHCF credit for one thing: they didn’t hide the breach notification page on their website from search engines.

Hey @zackwhittaker, you’ve probably already seen this, but just in case, here’s one for #TWIS.
3/3

I don’t know if y’all have your eyes on The DC Department of Health Care Finance ( #DHCF) incident that just went public. The breach notification from DHCF — https://dhcf.dc.gov/page/dhcf-data-incident — is disappointingly short on technical details, but judging from a little bit of digging at archive.org, it looks like they had links to publicly accessible #PowerBI reports on their website that allowed anyone to click through to the underlying data.
#infosec #breach
1/3

The breach notification of course claims they have no knowledge of anyone doing that, but of course it leaves ambiguous whether that’s because (a) the logs that would tell them never existed, (b) the logs no longer exist because the exposure lasted three years, or (c) the logs exist and they checked them and found no malfeasance.
2/3

The insurance company denied approval for the procedure. My doctor called them and tried to provide them enough additional information to get them to approve the procedure, but that didn’t work.
2/3

At this point I would’ve followed the process to appeal the denial, but before I could do that, without my knowledge or consent the doctor’s office canceled the procedure. So now I’ve lost the already-rescheduled-once slot for the procedure in the hospital’s calendar, and it’s going to have to be rescheduled again, with more delay.

I’ve had it up to here with all these people. Like, does the doctor’s office not understand that insurance denials can be appealed? What the actual fuck? 😠
3/3

RE: https://federate.social/@jik/117241540120221188

Remember how the hospital didn’t submit my procedure for approval until one business day before the procedure, and then it couldn’t be approved in time so the procedure had to be canceled and rescheduled, and the earliest available slot was two and a half months later?

Well, it just got worse.
#healthcare #healthInsurance
1/3

So I start over, a third time, and this time I say yes, I do want to encrypt the backup, and give the Time Machine configuration window the same passphrase I had already given to Disk Utility. It reformats the drive, but this time it keeps the encryption.

You have got to be fucking kidding me with this shit.
13/13

When Time Machine asks me if I want to encrypt the backup with a password, I say no; the backup drive itself is encrypted with a long, random passphrase, so there’s no reason to encrypt to add a second layer of encryption.

But then, when the first Time Machine backup starts running, a notification pops up: “Time machine is backing up an encrypted disk to an unencrypted disk.” Hmm, that’s weird, I definitely formatted the drive with encryption.
8/13

But as I’m doing that I form a suspicion about what happened to the encryption the first time, and once I save the Time Machine configuration, my suspicion is confirmed: when I turned off encryption in the Time Machine configuration, Time Machine _reformatted the filesystem on the drive and removed the encryption_. Wow, _that’s_ certainly completely intuitive behavior that I would totally have expected!
12/13

I open open Disk Utility and check the properties for the mounted drive. It says the drive isn’t encrypted.

So I need to try again to erase the drive with Disk Utility and reformat it with an encryption passphrase. I don’t know why I’d be any more successful this time than I was the first time, but let’s give it a go.
9/13

I repeat the same steps I went through last time. This time I check after erasing the drive in Disk Utility and confirm that the drive is encrypted. Then I once again accept the prompt to use the drive for Time Machine backups and once again disable encryption in the Time Machine backup config since the drive is already encrypted.
11/13

To do that I need to stop the Time Machine backup, which by this point has been running for about 15 minutes (with a “minutes remaining” counter which started out at 15 minutes and has been steadily _increasing_ for the entire time the backup is running, such that it now says “About 54 minutes remaining”), remove the drive from the Time Machine configuration again, and start over.
10/13

Once I manage to extract the drive passphrase from 1Password, I remove the drive from the Time Machine config and then tell Disk Utility to erase and reformat it as an APFS encrypted drive. That seems to work just fine. Not only that, but as Disk Utility is finishing up, Time Machine pops up a notification asking me if I want to use it as my backup drive! I have to admit that’s clever.
7/13