Everything in moderation, including moderation
Everything in moderation, including moderation
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.
Incorrect. The app was baked into the Pixel firmware from Google, not a manufacturer specific OEM.
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.
That mismatch between DMARC verification domain and the domain of the “from” header is called DMARC Alignment. Any modern spam filter is going to mark unaligned messages as spam. Especially if one of the domains is completely non-routable like .onion.
And even if you sent the email and it got through with your .onion address, no one would be able to reply to you because the replying mail server can’t even look up the MX record for your .onion domain.
TL;DR you can send emails from .onion addresses if you want, but no clearnet server is going to accept them.
So when you send an email, you can actually put whatever you want in the from
header. I could send an email that says from “made.this.up@website.doesnotexist”. The protocol doesn’t care.
Do you know who does care? The email server you’re sending messages to, because spammers and scammers love to try and send email with fake from
addresses.
So, there’s an entire verification system in place that involves looking up public keys from the website that the email claims to be from. (this is a gross over simplification. Look up SPF, DKIM, and DMARC for more info). The problem is you can’t even reach .onion
sites from the clearnet to do the lookups. So no email servers would be able to validate your address is legitimate and so would drop it as spam.
Racoon is the chaotic energy choice
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
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
Greatest character select menu of all time
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.
Pick a popular online service with a public API and write some scripts that integrate with them. Learn by doing.