No, this is different. This is new, as it was not doing it yesterday. When it scrolls my view, it jumps ~20 posts in the thread and it is not occurring anywhere else. Not even on sites where it makes fucking sense to utilize infinite scroll Twitter and such. I will not test with FB as I left there 6 months ago.

I just realized that if you click on a thread, click on the title image (to go back to the thread listing page), click on the same thread, etc....and repeat a 100 times, you'll get to the end of the thread. Loading the last-read post in the middle causes posts below it to be marked as read, so, without reading, the forum assumes that you're reading a lot more than you actually are.

Or, the simple act of replying to anything in the thread assumes that you have read the entire thread. This is a feature though. @codinghorror adamantly believes that you should read every single post before replying to anything. That might be a good idea on purely informative threads. On this site though, most replies are sarcastic, pedantic, dickweedery. I want to be a dickweed now. I do not want to read the whole topic before doing so. Also, if there is a fucking bandwagon I want to jump right on it.

This is what's happening when I have 2-3 posts in a row. 10-15....400 posts have happened and I don't want to read them all before replying (I'll forget what I was thinking about) and mobile doesn't let you go back to reading the thread without posting the reply.

So I turn off 'jump to end when posting' and just post in line as i'm responding to people. Hilarity ensues when somebody has already addressed what I'm talking about, but such are the risks of life.

We, the users, did not choose this platform. We, the users, tried to make our complaints known through politeness, bile, hate, vitriol. We tried everything, but Jeff still largely ignored our complaints that are the fundamental issues with Discourse as we perceive them.

He was never going to stay around here long term. 60 days he was here - and that's long enough to let us have at it for battle testing in his mind. That's enough and the rest of our objections don't matter because we're Doing It Wrong.

Could we have been more pleasant to Jeff? Sure. Would it have made any difference whatsoever? Not a hope in hell.

Oh, I know exactly how we arrived at having Discourse foisted on us. I just refuse to accept responsibility on any level for it. We didn't 'make our bed', because that implies at any point we had a choice in the matter. I suppose you can argue that we could choose to leave, but the amusement factor outweighs the WTF here.

We did have a choice - we could have been ignorant, not committed to the community, not contributed to the community, could still leave at any time, could do a massive wide scale xss attack on all discourse forums doing an awesome cross site ddos (i'm actually still not opposed to this one)

We made our beds by being halfway competent, or pretending that we are.

Just found another bug. I was in the likes thread and I quickly scrolled up a few times, faster than the shitty AJAX could load it. When I went to scroll back down, it automatically but very slowly started scrolling for me. The only way to clear it was to leave the thread topic and re-enter.

Just found another bug. I was in the likes thread and I quickly scrolled up a few times, faster than the shitty AJAX could load it. When I went to scroll back down, it automatically but very slowly started scrolling for me. The only way to clear it was to leave the <strike>thread</strike> topic and re-enter.

It's too bad @kodingwhorror and @sam have left these parts. Such bug reports must now be filed at meta.discourse.org