I much prefer the latter, especially since I get the choice.

Unicode takes backward compatibility like this very seriously.

Maybe with time, as more counterexamples are needed for things "you can't just..." in rust.

Blocking CS6 from accessing the internet in your firewall and using a key somoene posted online was a common practice back in the day.

Like email, I'd expect recieving to be more secure since it uses hardware the user isn't in control of.

There are free sites offering recieve-only SMS numbers, but they're almost universally at their rate limit for most services.

e.g. a server connects to the gmail MX server, and gets a response like "example@gmail.com now found at foo@example.com"

There's probably a ton of issues with this approach, but it would make switching email providers simpler on the user-end.

I tried entering ?utm_source=foo on Chris's site when it was posted the other day, and was surprised it didn't trigger the page. Pretty sure one or more of my firefox extensions remove that specific one from URLs before making the request.

Facebook combining tracking and IDs into an opaque UUID in URLs so they can't be removed is a level of user hostility beyond this.

I'd guess that the average person doesn't know that the GDPR applies even when you're taking details from people by hand with a pen on paper.

Can be self-hosted, if that's a concern.