Proof that LQT truly sucks

Plus I can't manually patrol these...unless you tell me how? 03:36, 13 May 2011 (UTC)

Oh, and it fux up RCs

User:Blue/scripts/markpatrolled.js

Oh okay...so I just add 2k of code to the wiki do be able to do something I didn't need the code for in the first place? I see. Won

der

ful

03:43, 13 May 2011 (UTC)

I know, it's annoying.

There was a bit of a flap over this earlier. I have said this before, but I think that Liquid Threads violate a number of good design principles, such as the KISS principle, REST, and preference for human-readable storage formats.

Some people (who shall remain nameless) should love this cause they're also a bitch to external link to.

I think that's done on purpose. Why would you want to patrol talk page comments?

Perhaps because they leave annoying red marks all over Recent Changes?

Really?

No, they don't. That's the point. It removes another annoyance. Patroling was designed for articles, as was pretty much everything else in MediaWiki, and makes using MediaWiki as a forum annoying. LQT fixes that.

I find these little boxes more annoying. I also prefer getting edit-conflicts, since that way I do not shoot off a post without knowing about other posts that have been made in the meantime.

Like this?

There are saner and more user-friendly ways to do that, e.g. some forums force a "show preview" in case other posts have been made while replying, I'm sure it could be implemented in LQT as well. Besides, LQT already warns you if there are new posts to a thread you're reading, it's at the top of the thread.

I think LQT is going to happen the same way voting reform happened in the UK. Let's just give it up.

It's going to happen at WP sooner or later

Somehow I don't see that going down well as a reason.