Well, everyone, you can now submit a comment to let the FCC know what you think about SpaceX asking for 1 million satellites for "AI datacenters" whatever the fuck that means.

https://docs.fcc.gov/public/attachments/DA-26-113A1.pdf

Comments due March 6.

I am having a very hard time believing this is really happening. Fuck you, SpaceX, and fuck you, FCC. This is not regulation, this is a fucking joke, that will destroy our ability to use satellites for centuries.

If anyone has time and energy to set up instructions for how to submit a comment to the FCC (it's really fucking complicated, on purpose, I'm sure), I would very much appreciate it! Otherwise I'll do it in the coming days.

@sundogplanets

If somebody wants to venture into this, please test all steps.

The first one involves sending an email to [email protected] with "get form" and your email address in the message body.

The reply I got was trying to strangely gaslight me:

"Delivery has failed to these recipients or groups:

[email protected]
Your message couldn't be delivered. The Domain Name System (DNS) reported that the recipient's domain does not exist."

There seems to be a strange subdomain falstaff.fcc.gov involved. The attached error log says:

Diagnostic information for administrators:

Generating server: SJ0PR09MB11735.namprd09.prod.outlook.com

[email protected]
Remote server returned '550 5.4.310 DNS domain falstaff.fcc.gov does not exist [Message=InfoDomainNonexistent] [LastAttemptedServerName=falstaff.fcc.gov] [SA2PEPF00003023.namprd09.prod.outlook.com 2026-02-05T12:30:46.776Z 08DE6078A5284768]'

@katzenberger @sundogplanets

This is boring stuff, but when your server tries to deliver mail, the first thing it does is look for the MX records for the recipient's domain.

It looks like they're using Microsoft to run their email system.

My first guess is that they're changing their mail servers, and somehow your message got stuck during the transition.

1/2

@katzenberger @sundogplanets

Then it looks up the numerical address of the mail server. That's working as well. I think that if you try again, it will work.

The caveat is that when you query a DNS server, the answer gets cached for a while. So you might have to wait for your server's cached copies of the data to expire. But the data that's live now is good.