Conversation

Notices

1. infinite love ⴳ (trwnh@mastodon.social)'s status on Wednesday, 18-Sep-2024 01:13:38 JST infinite love ⴳ

   • silverpill

   @julian @silverpill We could define a dedicated type for Thread or Conversation or whatever you want to call "a Collection that contains only "post" objects", but it would still be a Collection as well. I think this was something I was considering for a FEP that I ended up never really writing because it felt unnecessary and also very premature. The general idea is to define some way to know what a Collection "contains" -- is it a Conversation or a MediaAlbum or whatever. The problem is taxonomy

   • erincandescent (erincandescent@akko.erincandescent.net)'s status on Wednesday, 18-Sep-2024 01:13:36 JST erincandescent

     in reply to

     • silverpill
     • erincandescent

     @trwnh @julian @silverpill (the other option is instead of redirection do <link> tags, and then you can link to both if you wish; imagine including <link rel="as:context" href="...">)

   • erincandescent (erincandescent@akko.erincandescent.net)'s status on Wednesday, 18-Sep-2024 01:13:37 JST erincandescent

     in reply to

     • silverpill
     @trwnh @julian @silverpill I think the question here is "does a thread actually have any distinct properties of its own?"
     
     Maybe a title, but that can also be inherited from either the first or most recent post. Many threaded discussion systems don't have thread objects at all, of course (email is perhaps the canonical example)
     
     So I lean towards the idea that you should just redirect to the first thread in the post, and place the context (which when becomes just a collection of in-thread posts; an implementation detail) at another URL where it mostly becomes invisible to users.
     
     And I think that's better, especially because having significant semantics on collections starts getting confusing when e.g. you have collection pages flying around
     
     Really I think most types which can be represented directly as a collection (e.g. image galleries) are best represented as an object that possess a collection, though not everyone might agree
   • Evan Prodromou (evan@cosocial.ca)'s status on Wednesday, 18-Sep-2024 01:14:06 JST Evan Prodromou

     in reply to

     • silverpill
     • erincandescent

     @erincandescent @julian @trwnh @silverpill a thread is a tree with a root. Every non-root node in the tree has an `inReplyTo` that points to one of the other nodes.

     It's represented by a `Collection` in the `context` property of each object. (I don't like this, but it's common so we should just use it).

     It's in reverse-chronological order.

     If you started at the root node and walked the tree using the `replies` collection, you should visit exactly the same nodes as in the `context` collection.

   • infinite love ⴳ (trwnh@mastodon.social)'s status on Wednesday, 18-Sep-2024 01:14:35 JST infinite love ⴳ

     in reply to

     • silverpill
     • Evan Prodromou
     • erincandescent

     @evan @erincandescent @julian @silverpill I don't think a thread *has* to be a tree -- it's a set. The "reply tree" is a separate structure. Threads can be forked out of other threads.

     (I also dislike "reverse chron" and heavily favor "forward chron", but custom sorting of collections is not well-specced rn so that's a future step.)