Bleh

I'm just wondering if I'm the only person who assessed the functionality of this before passing comment... yes, it's fugly, I'll agree every day of the week. But when I first started reading Wiki talk pages after years of using bulletin boards I had no clue as to what was happening. You had to invent an entire new piece of etiquette about indents and replying just to make it work. This automates and controls that with specific replies and notifications. The internet spent the best part of a decade working out how best to set up a forum system and it came up with something exactly like this - it's only on Media Wiki talk pages that you get anything different. So if people complain about this I don't see why they don't head over to every other forum on the internet and complain there too.

It seems to be crashing Opera 10.63 half the time after saving, however. That is a major problem above any visual fuglyness.

Opera crashes from a lot of things (from my experience, it's an unstable pile of crap, at least the linux version), it's not necessarily lqt's fault. Then again, sometimes you can't see your newly posted comment, maybe that's related. Oh btw, https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions and select LiquidThreads from the list

Opera isn't that unstable, it just doesn't like things that are a little experimental. Often websites prefer to ban that browser than, you know, check their site actually works... but anyway.

I can't seem to consistently find what is the problem. It might be if it's trying to automatically update and reload the thread. If I can figure out the exact issue, I'll report it properly. As you can probably tell, I'm not the sort of person to just say "it don't work gud" and assume tech support can fix it like magic. I've been on the receiving end of generic complaints enough to find that isn't going to help at all.

Well yeah, but a decent browser shouldn't be crashing because some website has broken javascript.

Yeah, but sites shouldn't have piece-of-shit javascript.

Anyway, it's stopped it now so it might have been a background window being a dick.

Postel's Law: be conservative in what you produce, and liberal in what you accept from others. Opera isn't exempt.

I'd just rather use IE 5 than start worshiping at the Church of Firefox.

Who's making irrational, kneejerk opinions of something based on no evidence or reason now?

Yay, a browser flamewar. Because there wasn't enough DRAMA already

I believe you started it when you said Opera was a pile of crap. You have insulted my honour, sir, and I challenge you to a duel.

Yes, the battleship grey is ugly. I'll do something about it. But I have a million more important things to do right now. So if you want to do something about it rather than just complain (this isn't directed at you, Armondikov), right-click, inspect element, and play with it.

Could do. I can definitely spot some places where it could be streamlined a little, but I'm not sure how much of that would be in the CSS and how much would be in the software itself.

But when I first started reading Wiki talk pages after years of using bulletin boards I had no clue as to what was happening.

That is why liquid threads was developed, because people new to MediaWiki were unfamiliar with the system and prefered the blog/facebook/BB style thread.

I figured that much.

Now if ONLY the Facebook system was this useful...

I have just found that the new message thing Human was complaining about on my talkpage is a much better way of finding replies to your post.

I don't use facebook so I couldn't comment.

I'm finding it better than scanning recent changes and hoping I've caught the right one. And the fact it highlights new posts is useful if someone is sending threads off in different directions.

I'm in agreement that this thing is far from finished, but the potential is there and I think the benefits for running better discussions could be had now. It might not be best for the extremely short casual chit-chat of the saloon bar, but for where replies tend to be longer on average (with an increased risk of edit conflicts) and where threads go off on tangents this is a far superior way of doing it.

That said, it'd be nice if it could collapse the posts above the highlighted replies, rather than nesting everything and you having to scroll down to find them. But again, this is no different to scrolling down a tl;dr discussion in the normal talk page manner so it's more a problem that it doesn't solve than a problem it creates.

Isn't that what the arrow does? (Which should be a lot smaller and maybe down the bottom of the comment)

No, it just seems that clicking the arrow above a nest of comments collapses the whole thing into an outline of peoples sigs.

It's also messed up for me doing that, showing just a repeat of the same sigs over and over again. Unless you and I have had a conversation in this thread with 100 posts apiece without me noticing.

The repetition is obviously a bug. It is suppose to fold so you can see the next reply to the comment.