lemmy_in

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

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.

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.

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.