In my (non-expert) opinion, there are a few reasons
This works until you scale the team beyond 1 person and someone else needs to decipher the 30 line awk | sed | xargs monstrosity you created. Give me a real programming language any day.
Mods of communities can already see votes in communities they moderate. Admins of instances can already see votes on all content.
There are a few ways that the court can get this money. Disclaimer I am not an expert in bankruptcy law.
The most obvious one is what you said. The court can order the company's assets to be liquidated and then the proceeds of the sales would be distributed proportionally among the creditors.
Next they can go after the perpetrators like Sam Bankman-Fried and his crew. If they have any personal assets that they acquired as a result of their criminal activity at FTX, the court may be able to take some of that money to pay creditors.
Lastly is "clawbacks". Let's say you invested $1,000,000 in FTX and you were one of the lucky ones and happened to withdraw $10,000,000 in proceeds during the height of the scam. The court could claw back up to $9,000,000 from you since all of those proceeds were the result of a scam, even if you had no idea that FTX was shady. This is typically how the courts recover money from ponzi schemes like Bernie Madhoff
This has nothing to do with email as a protocol. The court order discussed in the article asked for the recovery email address of an account. No actual email data was transferred.
For most transmissions of digital information (even those here on earth) there's a concept of a "checksum". Basically at the end of every message, there's a special number, and you can do some math on the rest of the message to get that same number. If anything happened to change or damage the message in transit, the math doesn't work out and so the checksum fails.
I would assume Voyager works in a similar way so every time it receives a message it will compute the checksum and see whether it matches
You should definitely set up a DMARC record to prevent other people from using your email domain to send spam. If you don't have DMARC configured, other email servers will give any senders the benefit of the doubt and accept mail that claims to be from your domain.
You can just set the DMARC record to reject 100% of unverified mail and call it a day. Since you aren't sending anything it won't affect you.
These ads only appear in the "promotions" section of Gmail, the section that is by definition for advertising emails. It's not great, but this is the least intrusive place to put ads.
And then, because you were never in a classroom and never took a class on security, you probably have no idea what a buffer overflow attack is or how to use tools like valgrind to check for them.
Then you put your C code on the internet and get your server pwned inside of an hour.
Slightly hyperbolic? Yes definitely. But there is a reason we don't teach C to beginners anymore. Generally you want them to understand the mindset of coding before throwing them in the deep end. And I would bet nothing has caused more people to quit programming then
Segmentation fault: core dumped