-
A miniscule numbers of users, who by their own action create a slightly different pagination for them. Yet navigation wise this doesn't even break things... all links to comments will calculate which page to send you to and get you to the right place.
I'm obviously not understanding this right, I sent people to
https://www.lfgss.com/conversations/133015/?offset=105750#comment12718409
but anybody who doesn't bother to ignore the two or three most egregious trolls actually needs to be sent to
https://www.lfgss.com/conversations/133015/?offset=105800#12718409
so to link to a specific comment in context, I have to first check what page it's on for people who are viewing a complete comment stream, and then create a link which will be wrong for anybody who has a non-zero ignore list?
-
Your links are over-complicated. All you need is:
https://www.lfgss.com/comments/12718409/
No need for the offset bit. (If people want to read that bit of accompanying thread, they can.)
That does include Googlebot... which would suddenly start seeing the same content on different pages as people would be replying to the end of the conversation and earlier comments may not appear on different pages.
Google treat duplicate as a spam technique deserving de-listing.
I mean... you seem to imagine that the current system lacks thought. It doesn't.
The only people affected by this non-issue are those who ignore others. A miniscule numbers of users, who by their own action create a slightly different pagination for them. Yet navigation wise this doesn't even break things... all links to comments will calculate which page to send you to and get you to the right place.
And @mdcc_tester infinite scroll is possible. Always has been. But if we did it, then on image heavy threads the amount of RAM that browsers would take up would be huge.