Welcome to sparql-12 Discussions!

[JervenBolleman]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[TallTed]

Another introduction of myself? I'll let the comment linked below, and my github profile, speak for me for now...

#136 (comment)

[VladimirAlexiev]

Another introduction of myself? I'll let the comment linked below, and my github profile, speak for me for now...

I'm responding ot Ted here

[VladimirAlexiev]

@TallTed can you quote-reply to #137 ("continuing this thought") and let's see where it goes.
Hmmm, nope, this more specific link https://github.com/w3c/sparql-12/discussions/137?sort=new#discussioncomment-338643 is rendered as a global link to #137 so you have to search by the text in quotes.

[TallTed]

quote-reply to #137 ("continuing this thought")

One whole level of depth to the conversation... This is not a very well implemented threaded discussion space!

[VladimirAlexiev]

But here's a new train of thought, so a new subthread

[VladimirAlexiev]

continuing this thought, here's a subcomment

[VladimirAlexiev]

And further sub-sub-comment. You go ... > Quote reply then delete what you don't want to quote

[VladimirAlexiev]

I want a new OUTDENTED thread!!

[TallTed]

I am unimpressed. To put it mildly.

(ETA: This should have been a top-level reply, not a reply to a lower level of the discussion.)

[gkellogg]

I think if GH had implemented something more like review comments on lines of a commit the "threaded" concept could have been more useful. The important thing is to keep things that are closely relevant together, and I really don't see how this accomplishes that.

[TallTed]

It's too bad there weren't decades-worth of other attempts at building threaded discussions for them to learn from before building their own wheel from a raw boulder...

Oh, wait.

[ericprud]

In case GH is still accepting input on this. Can someone propose a publicly-viewable link to a node model for them to follow, maybe a nice viewer for mailing list archives (like W3C mailing list archive interface, but reflective of the aesthetics of this millennium)?

[TallTed]

I care less about the aesthetics of this millennium (how much value do avatars alongside user handles really add? OK, take a ahem page from LiveJournal/DreamWidth code...), than I do about simple discussion tree/thread displays (again, see LiveJournal/DreamWidth).

Almost any reasonably recent NNTP reader would do better than this. I seem to recall some attempts to reinvent NNTP with RSS feeds/readers, too. But those are generally client-side readers, so I guess they're out of vogue again.

[ericprud]

Sure, I don't care about the aesthetics either, but feedback to github is going to go a lot further if they have a model they're motivated to copy.