Thread:User talk:Qgil/Enabling LQT

Hey, could you please in the future refrain from enabling LQT on pages with existing discussions? Even in general the net benefits of LQT are questionable, but when a page is converted that makes the content a lot harder to follow and adds needless confusion.

I do bring this up in part precisely because the net benefits are so questionable, however, as I would argue that this initial confusion is not a necessary cost for something overally useful in the long run because LQT is if anything damaging in the long run. Instead of removing barriers for new users, it presents new barriers for those coming from other projects, as they are not used to it, it is massively unintuitive, and the differences cross-project are staggering enough as it is. It is hard enough for many users to step out of the comfort zones of their home projects without strange technical issues such as LQT presents.

And they are technical issues - having a reply button is nice, but the complete lack of integrated notifications when someone uses that reply button makes it a lot harder to follow updates to discussions, especially if they are happening at the same time as and relevant to stuff happening on one's watchlist. None of it shows up on the watchlist at all, as LQT does not have a meaningful history, and as a result apparently the only way to go back and find a discussion later (after already having marked it as read) is to go to the page and find it on the page.

So yeah, please don't do that.