= 27d567bc2d48d9f40e9ccc20ea370b15)
see comments on [META] Alternatives to rot13 and karma sinks - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (31)
I'm still in the, "It ain't easy until I have a bookmarklet that will encode/decode for me" camp.
This LW comment in the "Reforming rot13" discussion has a very good one for rot13.
I'm perfectly willing to deal with something else — if you make it just as easy for me to encode/decode. No external websites, no vastly overengineered plug-in; just highlight the text and press the bookmarklet's icon.
This is a great solution! And it could be made even easier by readers not having to install the bookmarklet, but to include the "Rot 13" button directly in the LW pages. With "position:fixed" it would be always on screen.
Like this:
<script type="text/javascript">
function rot13() {
// rot13 code here
}
</script>
<style type="text/css">
#tools { position: fixed; }
</style>
<div id="tools">
<p><a href="javascript:rot13();">Rot 13</a>
</div>
I've made a ro13 function here. It returns a RO13'd version of it's arguments.