i will not rest until fedi devs start using as:context properly. this is my single-issue. /hj
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social on last edited by
@silverpill cc @mikedev for posterity. also the swicg threaded discussions task force (hi @julian and @angus) is looking at this from a forum perspective and not just a social media perspective. it is quite likely they will arrive at a similar finding in their report
-
julian@community.nodebb.orgreplied to trwnh@mastodon.social on last edited by
@trwnh@mastodon.social something @angus@socialhub.activitypub.rocks and I were discussing was that some implementations include OP in the Page/context (iirc Lemmy does this @nutomic@lemmy.ml), and subsequent replies are Notes, whereas NodeBB, Discourse, and later Flarum, treat the context as merely a container.
It seems the latter fits better with the vision of 7888 but I'm not sure whether concessions need to be made for those other types.
-
trwnh@mastodon.socialreplied to julian@community.nodebb.org on last edited by
@julian @angus @nutomic i'm not sure what exactly you mean, but the exact types don't really matter (and shouldn't matter). for `context` you would just match against the id. after grouping by context, you are free to present in whichever way you want -- you can present in a flat chronological list, or in a nested reply tree sorted by some algorithmic scoring, it's all the same.
-
evan@cosocial.careplied to trwnh@mastodon.social on last edited by
-
trwnh@mastodon.socialreplied to evan@cosocial.ca on last edited by
@evan @julian @angus @nutomic yeah, i'm just saying that crawling the tree is optional if you already have context. pleroma for example presents things in a flat chronological list, like an imageboard.
example: post 3 is a reply to post 1, it has replies in posts 4 5 and 87. post 6 is in reply to post 2. there's an option to show the tree as indentation. if that option is disabled, you see posts in order 1 2 3 4 5 ... 87. if that option is enabled you see posts in order 1 2 6 3 4 5 87 and so on
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social on last edited by
@evan @julian @angus @nutomic similarly, a chat app might not have `inReplyTo` on every single message. in fact, the vast majority of chat messages probably won't have `inReplyTo`. in this case, building a tree would fail spectacularly. all the chat messages are grouped together by the context of being in the same room, not by being in a reply tree. the reply is just metadata, like in discord or indieweb reply-contexts or the old youtube "video replies" feature.
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social on last edited by
-
evan@cosocial.careplied to trwnh@mastodon.social on last edited by
-
trwnh@mastodon.socialreplied to evan@cosocial.ca on last edited by
-
evan@cosocial.careplied to trwnh@mastodon.social on last edited by