= 27d567bc2d48d9f40e9ccc20ea370b15)
potato 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)
I've upgraded the LW anti-kibitzer so that it hides the taglines in the recent comments sidebar as well. (Which is imperfect, because it also hides which post the comment was about, but better will have to wait until the server starts enclosing all the kibitzing pieces of information in nice tags.) No such hack was possible for the recent posts sidebar.
Well, to kibitz the anti-kibitzing, it looks to me like:
would match pretty easily against something that looked for
and deleted it, similarly on the Recent Posts but without the <strong>, checking for the identity of the two matched strings is optional (I forget how to do this offhand with REs).
That particular hack looks like a bad idea. What if somebody actually put a bold-face link into a post or comment? However, your original suggestion wan't as bad. All non-relative links to user pages get blocked by the anti-kibitzer. (Links in "Top contributors" and stuff in comments seem to be turned into relative links if they point inside LW.) It's gross, but it works.
Version 0.2 is now up. It hides everything except the point-counts on the recent posts (there was no tag around those.) (Incidentally, I don't have regular expressions because by the time my script gets its hands on the data, it's not a string at all, but a DOM-tree. So, you'd have to specify it in XPath.)
I think trying to do any more at this point would be pointless. Most of the effort involved in getting something like this to be perfect would be gruesome reverse engineering, which would all break the minute the site maintainers change something. The right thing to do(TM) would be to get the people at Tricycle to implement the feature (I hereby put the code I wrote into the public domain, yada yada.) Then we don't have to worry about having to detect which part of the page something belongs to because the server actually knows.
A great way to put your code into the public domain would be to put it up somewhere like (ideally exactly like, because they're very awesome) http://github.com/.
If anyone else wants to modify your code the git (and GitHub) workflow is very good - anyone can fork your repository, and if you want to accept their changes that's easy for you to do.
See the GitHub Guides if you're interested.
by <a href="<http://lesswrong.com/user/([^>"]+)"><strong>([^<]+)</strong></a>would be better (you could also make your.+non-greedy with.+?), but us (Trike) providing moreclasses andids is better still. We're looking into it.