bit1993 8 hours ago

Good stuff, but I think the title should be Email address obfuscation. Thank you for sharing I guess, but spammers can now learn from this too (:

▲

ghywertelling 6 hours ago | parent | next [-]

https://www.gregegan.net/

Contact details: [any mailbox] [at] [the domain name of this web site]. Please don’t ask me to give interviews, sign books, appear on podcasts, attend conferences or conventions, or provide feedback or endorsements for works of fiction, scientific theories, or slabs of text disgorged by chatbots.

I have no idea how to decipher this obfuscation.

▲

0x3f 6 hours ago | parent [-]

What's difficult about it? You know the domain, gregegan.net. You know the @ symbol, presumably. Then put literally any valid text before the @.

▲

0xEF 6 hours ago | parent | next [-]

Completely unrelated to the conversation, but our user names are remarkably similar.

▲

ghywertelling 3 hours ago | parent | prev [-]

Is that even possible? Shouldn't the recipient email id need to be created first to be addressable?

	▲	cyberlimerence 2 hours ago \| parent [-]
		Of course, the technical term for that setup is 'catch all', you can set this up with your email provider. You can send your email to "ghywertelling@gregegan.net", for example.

▲

layer8 4 hours ago | parent | prev [-]

Yes, people using “email” for “email address” in contexts where it could also mean “email message”, which “email” more frequently means, is really annoying.