bobbingwide

vsgloik

Aoccdrnig to a rscheearch at Cmabrigde Uinervtisy, it deosn’t mttaer in waht oredr the ltteers in a wrod are, the olny iprmoetnt tihng is taht the frist and lsat ltteer be at the rghit pclae. 
The rset can be a toatl mses and you can sitll raed it wouthit porbelm. 
Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef but the wrod as a wlohe.
This plugin implements a version of an algorithm that will produce text similar to the above. 
Basically it changes each word by randomising the order of the letters, leaving the first and last letter of each word the same.
You implement this on your website using the [bbboing] shortcode.
The syntax is:
[bbboing 
 text=”seed|text – some text to obfuscate” 
 form=”N|Y – display form to allow changes” 
 both=”N|Y – display both original and output text”]
If you don’t specify any parameters you get a ‘bbboing’ed version of the original text.
Examples: 
 [bbboing text=”code is poetry”] may produce ‘code is peroty’ or ‘cdoe is pretoy’ 
 [bbboing text=’powered by WordPress’] may produce ‘prweoed by WrdsorPes’
It’s also feasible that the randomisation produces exactly the same output as input. 
So [bbboing text=’bobbing wide’] may produce ‘bobbing wide’
Of course, nothing happens for words with fewer than 4 letters so 
[bbboing text=’it is not a con’] WILL produce the same output as input.
You may notice that some spammers/spambots intentionally misspell words when creating comments. 
bbboing does not in anyway endorse this.
Please use bbboing for your own amusement.
Note: the bbboing plugin is dependent upon the oik plugin.

bbboing

obfuscate text but leave it readable, apparently

pixeline

This plugin provides an unobtrusive yet efficient protection against email harvesters / spambots. Here is a <a href="https://pixeline.be/blog/email-protector-demo-4258.html" rel="nofollow ugc">demo</a>.
Post/page authors may write email addresses in their article in the usual format (“john@doe.com”) without exposing them to spam email harvesters. The plugin takes care of the obfuscation, implementing a graceful degradation technique focusing on usability so as to protect your email addresses from harvesters while keeping them usable to your human visitors.
The plugin replaces any email address found in posts, pages, comments and excerpts, and replace them by a bit of html markup that should deceive most email harvesters: <code>john(replace the parenthesis by @)doe.com</code>. 
If javascript is available, it will display a clickable link and display the original email to the human user. Maximum usability, maximum protection.
Please <a href="https://wordpress.org/extend/plugins/pixelines-email-protector/" rel="ugc">rate the plugin</a> if you like it.
<h3>Usage</h3>
Write your email addresses inside your posts and pages as usual. When the plugin is activated, it will replace them by a human-readable html string that explains how to deduce the email address, and if javascript is available (99.9% of the time), the original email address will be displayed as a clickable mailto: link. For example: 
 Hello john@doe.com. How are you today? 
will become 
 John( replace these parenthesis by @ )doe.com.
Additionally, you can specify what the mailto: link should look like by sticking a parenthesis inside of which you put the visible link text, like this:
<pre><code>Hello john@doe.com(John Doe). How are you today?
</code></pre>
will become 
 John( replace these parenthesis by @ )doe.com.
<h4>inside a theme</h4>
If you need to protect emails inside your Theme’s files (like the footer.php for example), you can use the function safe_email() like this:
<pre><code> echo safe_email('you@domain.com'); <h3>Contribute</h3>
</code></pre>
Github repo: https://github.com/pixeline/pixeline-email-protector

Pixeline's Email Protector

Write email addresses without worrying about spambots and email harvesters.

bbboing vs Pixeline's Email Protector