Reading threads in separate tabs?



  • Opening a thread in a new tab from e.g. /recent lands you at the top of the thread, rather than wherever you left off.

    Now, there's briefly the toaster (which, btw, is not really readable with the darkly theme), but that disappears fairly quickly, making it useless when opening stuff in new (background) tabs.

    Any fixes to that? Some setting that I've missed?


  • Winner of the 2016 Presidential Election

    @cvi
    If you don't want to go to the top of the topic, you need to click the link on the right side of the recent-table. (the one that says "X minutes ago".) I am not sure if that brings you to the end of the topic or the last read post, though... It seems to change every once in a while.

    Making the toaster more visible is solved via a Stylish I posted in the topic for the NodeBB stylishs.

    Filed Under: I can probably look for that topic if you want

    Addendum: https://what.thedailywtf.com/topic/19207/can-we-have-an-official-nodebb-stylish-topic-now



  • @Kuro The "X minutes ago" takes me to the last post (using a convenience sample of four topics).

    Not sure what you mean by changing once a while -- you mean between updates?


  • Winner of the 2016 Presidential Election

    @cvi No, I mean that - probably by virtue of jelly-potatos - I ended up at my last read post when clicking on that link. So I was never entirely sure.

    I am pretty sure we mentioned that during Discourse times already and the NodeBB-Devs are aware that a 1-click solution to go the last read post is the preferred method of navigating.

    Filed Under: Give it time!



  • @Kuro

    Give it time

    This is mainly me checking if it's me doing it wrong(tm), or not. ;-)


  • Winner of the 2016 Presidential Election

    @cvi Well, you are obviously :doing_it_wrong:

    But NodeBB is also :doing_it_wrong: So I guess it's fair game.

    Filed Under: Why would you want to read anything on the forum anyway? Thats a :barrier: to spammingposting well researched posts



  • @Kuro said:

    If you don't want to go to the top of the topic, you need to click the link on the right side of the recent-table. (the one that says "X minutes ago".) I am not sure if that brings you to the end of the topic or the last read post, though... It seems to change every once in a while.

    I'm pretty sure that sends you to the last post at the time the topic list was reloaded.


  • area_deu

    @PleegWat said:

    @Kuro said:

    If you don't want to go to the top of the topic, you need to click the link on the right side of the recent-table. (the one that says "X minutes ago".) I am not sure if that brings you to the end of the topic or the last read post, though... It seems to change every once in a while.

    I'm pretty sure that sends you to the last post at the time the topic list was reloaded.

    That makes sense-ish



  • @aliceif Yeah, but what @cvi/I/we are looking for is something we can click in the topic list that immediately opens the first unread post. Currently that's two clicks away, via a toaster when opening the topic from the top that is only visible for a very short time.



  • There's an issue pin GitHub or a topic over on nodebb's forum about this. They're more or less open to improving this, but not sure what to do.

    I think they're used to having generally small topics, so it's not been very important to them our their users.


  • Discourse touched me in a no-no place

    @boomzilla said:

    They're more or less open to improving this, but not sure what to do.
    I think they're used to having generally small topics, so it's not been very important to them our their users.

    Well, I made a suggestion in the other thread mentioned above: all you need is an xref table, with userid, topicid, and "last read post #", one row per person per topic. You don't need to fuck around with :disco::carousel_horse:'s keeping track of whether or not each individual post was read, just keep track of where the user left off.

    Well, that was how you could do it in Web 1.0 forums. I don't know if NodeBB uses a Complicator's schema or not.



  • @FrostCat They're using MongoDB, it's so webscale, things like that doesn't matter.



  • @FrostCat NodeBB already knows the last read post, and presumably without Discourse's "log the read time for each post for each user" shit. NodeBB just isn't very good at using it.



  • @FrostCat said:

    Well, I made a suggestion in the other thread mentioned above: all you need is an xref table, with userid, topicid, and "last read post #", one row per person per topic. You don't need to fuck around with 's keeping track of whether or not each individual post was read, just keep track of where the user left off.

    Tracking individual posts is not a bad feature. Tracking only last read post is simpler to implement (you probably really want to partition the dataset on user ID otherwise), but it means you can't ever enter the thread by any other means than 'take me to my latest read post' or it might override the remembered position in a wrong way.



  • @CatPlusPlus said:

    @FrostCat said:

    Well, I made a suggestion in the other thread mentioned above: all you need is an xref table, with userid, topicid, and "last read post #", one row per person per topic. You don't need to fuck around with 's keeping track of whether or not each individual post was read, just keep track of where the user left off.

    Tracking individual posts is not a bad feature. Tracking only last read post is simpler to implement (you probably really want to partition the dataset on user ID otherwise), but it means you can't ever enter the thread by any other means than 'take me to my latest read post' or it might override the remembered position in a wrong way.

    Unless you actually do it, and end up with a 3 GB table (like we did).
    In theory i like it, allowing alternate reading modes is cool. Discourse didn't do that, it only collected the data.


  • Discourse touched me in a no-no place

    @swayde tracking individual posts like Discurse did is essentially useless, because even it only took you to the last read post when you entered a topic the normal way.



  • @CatPlusPlus said:

    @FrostCat said:

    Well, I made a suggestion in the other thread mentioned above: all you need is an xref table, with userid, topicid, and "last read post #", one row per person per topic. You don't need to fuck around with 's keeping track of whether or not each individual post was read, just keep track of where the user left off.

    Tracking individual posts is not a bad feature. Tracking only last read post is simpler to implement (you probably really want to partition the dataset on user ID otherwise), but it means you can't ever enter the thread by any other means than 'take me to my latest read post' or it might override the remembered position in a wrong way.

    You mean, like Discourse did? That's nothing new, and it's a penalty only if I decide to go somewhere else. My choice.


  • Impossible Mission Players - A

    @CatPlusPlus said:

    but it means you can't ever enter the thread by any other means than 'take me to my latest read post' or it might override the remembered position in a wrong way.

    Well, not as much. You could make the marker only sensitive to push-forwards (or increasing), so if you happen to accidentally enter at a later time the marker won't get updated until scrolling down again, and if you enter at the top the unread marker doesn't update until you reach it.



  • @FrostCat said:

    all you need is an xref table, with userid, topicid, and "last read post #"

    like this?


  • Discourse touched me in a no-no place

    @ben_lubar Beats me, Captain Cryptic.

    I hope you're not suggesting I bookmark the last post in every topic every time I finish reading it, though. Because I've been to Milwaukee and I'm willing to drive up there and slap you.



  • @swayde Eh, 3GB is nothing. With proper partitioning it should be even less of an issue.

    @FrostCat said:

    tracking individual posts like Discurse did is essentially useless

    Discourse doing something wrong doesn't mean that the idea is bad. :p



  • @FrostCat no, bookmarks are last read posts and favourites are bookmarks.


  • Discourse touched me in a no-no place

    There's a SpongeBob macro that contains an adequate response to what you wrote, but I CBA to look it up. It's from the end of their Moon trip, though, if you want to. You can probably figure out the right bit.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.