I often read LW on my phone and for that use case rot13 is the best spoiler method by far. It prevents immediately seeing words that would give away spoilers, but I can generally decode a given phrase in my head given the word lengths, punctuation, topic of conversation, and position of common words like 'gur', 'na', 'bs', 'vf', or 'gb'.
Using reddit-style CSS spoiler tags means that I can't access the spoilered content at all AFAICT, and linking me to a decoder, while nice in theory, isn't very helpful because if I click it I will lose the nice highlighting of new posts. This is a Big Deal on long-running threads like the HPMoR discussions.
linking me to a decoder, while nice in theory, isn't very helpful because if I click it I will lose the nice highlighting of new posts
Does your phone browser allow you to open links in new tabs? (If you're not sure, try doing a long press on a link.) If not, you should switch browsers. I use Dolphin on Android. Opera Mini also has this feature and is available for virtually all phones, I think.
Now if someone could tell me how to avoid accidentally voting someone up or down on my phone (or worse, accidentally banning a comment) when I'm trying to scroll...
rot13 is... (Results)



A quaint internet tradition that I quite enjoy
So annoying
Easy to use because I have Leet Key
Vapbzcerurafvoyr
In November, DanielVarga complained about rot13.com as a way of hiding spoilers, and suggested some specifications for an alternative web service, with an algorithm that can operate on any character. I whipped up two, one using a bitwise not and the other using a password. These have a usability advantage over rot13.com: they automatically generate a decode link, so that people who don't have an add-on such as Leet Key (get Leet Key! or d3coder if you're on Chrome!) on whatever device they're on can still use them. The advantage over using a site like pastebin is that all of the text is encoded in the url, so if makefoil.com is down or you're offline you can still extract it with a bit of work. Both algorithms are in unobfuscated javascript; feel free to host your own version.
Recently, I had the thought of doing a similar thing with polls. This site doesn't have built-in polling functionality, and the project to create it seems to have stalled. People generally solve this by creating a comment for each option, asking people to upvote the comment of their choice, and asking people to downvote another comment to balance the karma. It's elegant as these kludges go, but it's still visually confusing in a comment thread, clogs the "Top Comments" lists, and somehow rarely ends up balancing correctly.
Here's the site I used to create the above poll. Those vote buttons will turn into vote counts once you vote (you may need to refresh). The site outputs poll syntax in two formats: html, which you can use by creating an article and clicking the html button on the top tool bar, or markdown, which is for comments. The markdown display is a little different because the Less Wrong functionality for having an image be a link seems to be broken; the image gets double-encoded or something.
I hope you'll consider using markdownSpoiler or passwordXor when sharing secret info on the next Harry Potter and the Methods of Rationality chapter, and getting input with a makefoil poll.
Notes: