Hacker News new | past | comments | ask | show | jobs | submit login

Ah, got me there. I've gone ahead and updated it with the relevant info!



I would "encode" it as abc at my domain which is google.com or something not to get your email grabbed by bots.


At this point that is such a common tactic that I would imagine many bots already account for that.


The particular address is filtered to a sub-inbox, so I don't generally see emails there unless I'm looking for them.


Base64 would be better: unlikely to be automatically checked by bots, easy to decode, and guarantees that the decoded form matches the true email.


Because an email address scraping bot that can handle "foo at bar dot com" won't ever figure out what base64 is? Srsly?


When did I say that?

Maybe someday address scraping bots will learn base64. Maybe it will be at about the same time you learn to read.


No need to be insulting.

I replied to your claim that base64 should be preferred over "foo at bar dot com" since it would be "unlikely to be automatically checked by bots". I find that claim unlikely since a scraper that is adjusted to handle the former will easily be adapted to the latter and likely already is today.

I'm happy to hear a counterargument to that position, but please don't include an insult.


> and likely already is today.

This is the claim that requires backing up.

Since offering emails in base64 form is not usually done, I consider it pretty unlikely that bots have been specially modified to go around checking everything which looks like base64 to check whether them codes have an email inside.

If you don't want people to be insulting, maybe you should think through your arguments more carefully before treating someone else like the idiot.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: