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

Pick a popular online service with a public API and write some scripts that integrate with them. Learn by doing.

In my (non-expert) opinion, there are a few reasons

1. NPM is more popular than those other services by an order of magnitude, especially among new developer and startups.
2. NPM allows for code to be executed while you install the package which is different from maven or nuget and allows for easy exploitation paths

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.

Unknown variables

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

So long as you have robust data sanitization on the backend to prevent XSS and HTML injection attacks…

If you can get away with just using Markdown, you should definitely use that instead of full HTML.

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

What a brain-dead take. If your threshold for true safety is “literally no one can force you to decrypt it or affect the system in any way” then of course it’s insecure, and so is everything else unless everyone writes their own crypto implementation yourself locally.

“oh I compile my binaries from source so I’m safe”

Someone could compromise the source repo and have it serve a compromised version to your machine. I guarantee you aren’t reading the entirety of the open SSL source code before you compile it.

Anyone that takes this article seriously should read On Trusting Trust. It’s a very short essay that states the point much more eloquently than the post author that you eventually have to trust someone. Whether that’s Apple or Signal or some random maintainer of your crypto implementation library, you have to trust someone that it hasn’t been backdoored.

It’s perfectly normal for your computer to have daemons.

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.

The ideal solution is to have one identity provider and then use Single Sign-On (SSO) to authenticate your users to all of their other apps. All of the big identity providers (Microsoft, Google, Okta, etc) support security keys.

I recognize that it might not be feasible to use SSO for all of your apps as a small business; a lot of SaaS platforms unfortunately charge extra for SSO. That being said my advice would be use SSO whenever possible for your apps and include SSO availability in your decision-making process for purchasing new software.

For those apps that do not support SSO, my advice would be to either compensate employees for using their personal devices for work or give them corporate devices that are only used for work things.

According to all known laws of aviation, there is no way that Dumbo should be able to fly. Its ears are too small to get its fat little body off the ground. Dumbo, of course, flies anyway. Because Dumbo doesn’t care what you think is impossible.

“Embargo” sure is a funny way to say “launching pirate raids and missiles”.

The term is metonym. It is when you use a characteristic or associated attribute of a thing as the name of that thing. A classic example would be “the crown” when talking about the monarch or “The Whitehouse” when talking about the president.

“I learned participant observation from watching you” is such a phenomenal line