• GNU/Linux Admin

    @a_5mith @Kamal-Patel Mention notification pings do not show up when you edit a post, only when you create a new post. This is because I don't store "who pinged whom" in the plugin, so it would be trivial to just continually edit a post in order to ping lots of people over and over again, sort of like a post bump, but worse, since it's a notification.

  • @julian Your mention shows up in my notifications, but no counter appeared to tell me I had an unread notification. If that makes sense. 🙂

  • @julian Same here (no red thingy, but unread notifications listed). But damn, now I can't "edit notification bump" my way to infamy 😞

  • There are a few great thread examples on this forum where comments would be a nice feature...

    ...Like here, where the topic of poutine is interspersed within the normal conversation, and it could instead be a couple comments within the original poutine post.

    ...Or [here](link url, the "introduce yourself", thread where it might seem out of place for the user to read through and see a reply to an introduction from several posts above. Some of the intro posts are beefy enough to deserve a bunch of comments underneath them.

    I know comments can be made as a plugin, so I'll try to learn javascript a bit better and some node.js and help out in a few weeks/months!

  • Here's someone talking about how expandable comments reduce usability compared to smaller always-listed comments:

    "When the big site redesign happened the useability of the site went into the crapper. I don't waste my time expanding comments under answers. Many good things are lost when embedded under answers and not seen. Who wants to click to expand comments? Not me. I think the problem is directly linked to this clunky comments and answers system. It non-standard and I don't like it."

  • I too think a comment (reply under reply) feature would be extremely beneficial. It doesn't have to be fully threaded, just 1 level under a top level reply is enough.

    This would make NodeBB even more perfect as a blog commenting system too as blog commenting systems such as DISQUS have this.

  • If you start threading one level, then it needs to go another level when that quote or reply receives another reply or a quote. The one thing I despise about reddit is the layout of the comments and how they just get levelled down, until eventually it stops giving you the replies and tells you to open another page to view them.

    List view, all the same. Nice and simple. Winner.

  • @a_5mith To be fair, reddit has infinite layers whereas all StackExchange/Askbot/Q2A/etc sites have one layer.

    From my (admittedly narrow) experience, the comments rarely number more than five or so.

  • GNU/Linux Admin

    @Kamal-Patel They sure do here 😆

  • @julian I didn't know those still existed in 2014 😛

  • If not threaded comments, maybe a control next to the @name_of_person_replied_to that will zoom you up to the post that was being replied to.

    Another idea is to have an alternate view. A control that when you click on it, rearranges everything as nested comments.

  • Actually discourse has a very good implementation of threaded comments. Best of both worlds approach that satisfies everybody.

  • @zenkamal this is true!

  • GNU/Linux

    This thread is applicable to this discussion I believe. Perhaps NodeBB can leapfrog what's currently out there by a happy medium between nested comments and forked conversations. I dunno... it seems like we could allow 1 level of comments on a post, but not 2 (so no comment on a comment, only comment on a post). But --- we could build up forking functionality to allow forking of posts.

    So if someone really did want to comment on a comment, they could fork that and keep going. After all, confusion and lack of context is the complaint against reddit-like discussion isn't it? If we allowed one level of comments only, and then required forking after that, it might be the happy medium. Context would theoretically always be there.

Suggested Topics

  • 4
  • 10
  • 5
  • 2
  • 8
| |