Unknown variables

Incorrect. The app was baked into the Pixel firmware from Google, not a manufacturer specific OEM.

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

The number is real you guys

For small apps, generating it in the backend, trying to insert it, and then catching the exception should be totally fine. The odds of collision are quite small.

I personally feel UUIDs are overused unless you happen to be running truly distributed systems that are all independently generating IDs.

In this case where the ID is also going to be in the URL, you’ve just added 32 characters to the URL that don’t need to be there. Since OP is apparently concerned with the look and feel of the URLs, I thought that UUIDs wouldn’t be the best option.

You could also just use a random non-numeric primary key. For example you could generate a string of 8 random characters + numbers. That would give you well over 2 billion possible IDs.

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.

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.

All words you spell must include the central letter, adjacency doesn’t matter.

The design is a bit of a visual joke combining the concept of a “spelling bee” competition with the honeycombs of literal bees.

Losing my religion

The OMNY system in NY doesn’t require you to install an app on your phone. It’s tap to pay with any credit or debit card, even apple or Google pay. If you want you can still get a physical OMNY card and refill it, but it’s not required.

Sounds like a skill issue on the author’s part tbh.

Also fuck physical checks, online payments are 100x better. Writing all of your baking information on a slip of paper and handing it to someone is probably the least secure way to transfer money.

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.

Jetbrains Phpstorm is probably best in class, but you’ll have to pay for it.

None of these words are in the Bible

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

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.