= 27d567bc2d48d9f40e9ccc20ea370b15)
Morendil comments on LessWrong anti-kibitzer (hides comment authors and vote counts) - 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 (52)
Anyone else using Anti-Kibitzer, the new version that's activated from Preferences?
The AK script is currently broken on article pages, due to some funky interaction between its CSS and the AddThis bookmark at the bottom of the page. (Since this is outside the LW codebase I have no reliable way to check if this is a recent change or if it has been broken for a while and I only just noticed. I'm pretty sure it's a recent change.)
I'll push a fix in the next few days.
Is anyone still using the old (Greasemonkey powered) version?
Fix committed and pushed. Though I'm getting the impression this is mostly for my own benefit?
I may take another look. I used it for a while... must be a year ago now. I hacked it around a little too, to add a couple of features I desired.
What were those?
Turning off the 'new messages' notification and blocking comments based on user. I also had it so it would selectively block comments by a user only when they were replying to me.
I had been using the anti-kibitzer, but since yesterday if I pushed the button to turn it off I would get:
http://i157.photobucket.com/albums/t43/Macbi/lesswrongscreenshot.png
And if I pushed it again the page would be pure white (not even an anti-kibitz button). (Latest version of Firefox being used on Windows 7)
Yep, I've been seeing just the same thing. It's the defect I've corrected, and it will go away as soon as Tricycle push it to production. That sometimes takes a few day or more.
The specific defect in the code might make an interesting anecdote in that "programming as a rationalist skill" post I've been planning for ages. My thesis is that every single "bug" in software is the result of a map-territory mismatch.
In this particular case, I'd been assuming that once a Web page was loaded, its CSS stylesheets could be accessed by a Javascript program through an array whose ordering wouldn't change. This assumption turned out to be wrong: the "AddThis" widget at the bottom of a post inserts a stylesheet right at the top of the array, shifting the main stylesheet one place forward, so that it is on that stylesheet that the AK script stomps.