I just put up v2.0 of the Renegade Email Protector. It lets you publish email addresses on web sites without worrying about spambots harvesting them.

There are 4 versions of obfuscated/munged code generated, and each one is stronger than the previous one.

#4 is just pure nastiness. That's what I'm using

Anyways, it's free so I hope some people enjoy it and can use it.

Don't forget to tell a friend~!

Oh, and for those that feel like being skeptical... Yes - it is theoretically possible for a spambot to get the address, but very very far from practical. I can explain why it just isn't within the realms of reality if you like.

Oh heck... Why not now...

Browsers run on clients with lots of resources so they can "figure out" what the actual email address is relatively cheaply/quickly. Spamming requires maximum efficiency and parsing all the javascript and other stuff on a page for a spambot email harvester is just far too expensive to do.

It's not that doing it 1x is expensive. It's that doing it millions of times is far too expensive (CPU-wise).

Spam is all about numbers, not quality, so missing a few encrypted email addresses doesn't matter as it's easier and cheaper to get unencrypted email addresses.

Cheers~!

(Edited URL)


Edited by Bluefrog - 20 November 2005 at 4:51pm

Hmm... Do you have .Net 1.1?

Can you send me a screen shot of the error? You can get my email address on the product page

Mart is correct:

http://renegademinds.com/Default.aspx?tabid=68r:

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

http://renegademinds.com/Default.aspx?tabid=68 - no "r"...

typo...


http://renegademinds.com/Default.aspx?tabid=68