@scott
-
> the top level post stays the top level post. It's the post that started the conversation.
so the "top-level post" is the topic of the discussion? what if the topic of discussion is something outside the thread, or something more general, like a concept?
basically, "the post that started the conversation" isn't special. it's just "the post that started the conversation".
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
> comments inherit the permissions (access list) of the top-level-post.
inheriting permissions is orthogonal; you can inherit them from the thread itself instead of from the "top-level post".
> the whole thing can be sorted any way you want, it does not matter
threads can also be sorted any way you want.
> f you took a blog post and its comments, and then reverse sorted the posts. The most recent comment would become the article
no? just pluck the first item out before resorting?
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
@scott i don't think we should let implementation-specific UI decisions define the semantic relationships here.
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
@scott anyway, what i'm getting out of this conversation is that i should probably devote a section of some writeup to how you can take generic data and give it specific presentation. a sort of "UI/UX considerations" section, showing how a conversation can be rendered in multiple different ways.
-
scott@authorship.studioreplied to trwnh@mastodon.social last edited by@infinite love ⴳ That is like saying the blog post that started the conversation is not special and it is okay to sort the posts so that the article appears as a comment and someone's comment appears as the article.
I think we are talking about two different things. You are talking about how the data is stored and I am talking about what information I need to render it properly.
As I said, you can call it whatever you want on the backend. You can call a thread a "collection" in ActivityPub. I don't care.
Here is the information I would like to have:
Is this a threaded conversation (conversation container)?
If so, what is the top level post?
Does this post belong to other collections or contexts?
Can this object be replied to by the current user?
You can call it a collection in ActivityPub. That is fine. A thread is a type of collection.
You can assume that the oldest post on the list is the first post. That is probably a good fallback.
But it would be better if the top level post is explicitly defined if there is one.
Because, as I said before, lists with a top level post are NOT displayed the same as a list without a top level post on most platforms that support threaded conversations and collections. -
trwnh@mastodon.socialreplied to scott@authorship.studio last edited by
> it is okay to sort the posts so that the article appears as a comment and someone's comment appears as the article.
no, this is not "okay". but this is the result of semantic confusion. it stems from assuming that the order of posts in a conversation's *presentation* decides the topic of the conversation, instead of the conversation having its own explicitly declared topic.
multiple presentations are possible, so clear semantics are needed to describe what you want.
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
@scott by which i mean, classes (types) and properties in order to be able to know that you are looking at "something you can participate in by sending your object to the owner, who may Add it". if those types and/or properties are present, that should be a clear enough signal for you to render it with a comment compose box for example.
i still need to think about the taxonomy that makes the most sense here, but i hope to have more to share soon regarding the "information i would like to have".