Skip to content
  • 6 Votes
    9 Posts

    Far be it for me to agree with Brazzerstop,
    But sometimes Less is more.
    If people want to view the forum they can come here!

  • 1 Votes
    11 Posts

    @julian said in [RFC] Change to the quick-reply `toPid` value?:

    While it is true that you can know at-a-glance whether a post has replies, I'd want to know what specific value it provides to you as an end user, besides the tautological one (i.e. it provides value when showing a post has replies, because it shows it has replies).

    For me one of the primary values of that information is found in picking up the thread of a conversation between two or more users. Traditionally forums have only had back-links, and the only way to read a conversation was to start at the very end and follow the reply-links through to the beginning, perhaps opening each post in a new tab so they could then be read sequentially once you find the beginning. The replies dropdown allows me to start at the beginning and follow the conversation as it bobs and weaves randomly through the thread.

    The broader point is consistency of expectation. If users aren't reading each post of the thread and they want to do what I just described, they could train themselves to <first check to see if there is a replies dropdown; if not, check to see if the next post is a reply; if both of these conditions fail then I am at the end of the conversation>. But more consistency makes it easier to accomplish this use case, as well as the simpler use case of gaining information about whether a post has received replies.

    (Just my $0.02. I am coming from long-form discussion forums where it can be hard to follow a conversation from post to post, where users generally do not read each post in a thread, and where time zone differences tend to place gaps between responses.)

  • 2 Votes
    10 Posts

    FWIW I think there was a bug in a version of Discourse (or it was intentional I have no idea) but if a post was edited or other non-contributory actions (lie moderation) were done, it would bump the topic, again think it experience of it for too long.

    It caused a lot of confusion and sometimes in strained circumstances, people would interpret it in a negative way and lose the head. Rare, but it did happen once or twice. Obviously this was more random than the proposition above.

    I've never used a bump feature ever, other than old school "bump" which is sometimes a humorous affair and clearly signals the bump.

    I rather create and see created topics that will stand the time and value that need regular updating., constant maintaining because they are hot or timelessly useful. I also would think about more editorial management than allowing social management of information, because the "social" is over done IMHO and now Ai can be just as "social" as the next bot. 😉

  • 0 Votes
    2 Posts

    Went ahead and made the changes already 😆

  • 0 Votes
    1 Posts

    Re: gh#1721, the NodeBB team would appreciate thoughts both there and here 🙂

  • 0 Votes
    1 Posts

    Please see the following GitHub issue. The team would appreciate your thoughts both there and here 🙂

    re: gh#1730