Does nodebb support following/joining federated communities?
-
@julian Personally, I find the reply list -- and especially the new auto-quote back-references a more than sufficient solution, but then I don't think threaded discussions are a value-add to the bulletin board experience.
It's just not part of the expected UX, and kind of breaks the BB UX, which has always been built on the expectation of reverse-chronological posting. Not that I don't understand the utility, or someone having the preference. Threading is now ubiquitous on other social modals. It's become part of the design language of Web 2.0.
Some platforms that use threading now only load the first couple of levels of replies. I wonder if that's something that's currently possible via theme work, or if a plugin would be required, or even if work on core would be necessary. Or if some sort of popup modal that loads threads might be viable? Solutions that wouldn't require the threads to be pre-loaded.
-
@Kichae the workaround that @baris and I played around with (very) briefly involved the "x replies" expando button.
I think there were some rather simple adjustments made to load only one level at a time, and that was essentially the "threaded" view.
I don't remember the details any more, perhaps he does.
-
Does nodebb support following/joining federated communities? And does it support switching to a threaded view?
Yeah there is a config property
config.showNestedReplieshttps://github.com/NodeBB/NodeBB/blob/master/public/src/client/topic/replies.js#L40, it is not exposed anywhere but a plugin can set this totrueinfilter:config.getand that would cause more than one level of replies to show up. However the posts all show up at the top level in chronological order, since core adds everything at the top level(tid:posts) and then adds it topid::repliesif it is a reply to a specific post. -
@baris could we theoretically load only top-level replies by:
- filtering
tid::posts(expensive), or - maintaining a separate zset (lighter)?
- filtering
-
Does nodebb support following/joining federated communities? And does it support switching to a threaded view?
Filtering goes
when you have a topic with 50k posts, and adding a new zset means adding 2 actually because there is sort by timestamp and sort by votes for topics. -
Does nodebb support following/joining federated communities? And does it support switching to a threaded view?
I made a post about this a couple of days ago with an example, where I tried to post into a Lemmy community and it didn't arrive
-
Does nodebb support following/joining federated communities? And does it support switching to a threaded view?
@julian did you have a chance to look at this issue of not being able to post into lemmy community?
-
@eeeee If you mean 'post' in the sense that Lemmy means 'post' (i.e. something distinct from a comment), then Lemmy doesn't process User Mentions in those. In a comment, you can Mention your NodeBB user and Lemmy will send it to the relevant instance, but nothing will happen if you Mention your NodeBB user in a post.
-
-
Does nodebb support following/joining federated communities? And does it support switching to a threaded view?
@freamon
Are you saying that Lemmy is different in that regard?
Example. Im logged into Lemmy and see and interesting post that a friend might be interested in.
I post as a reply
Hey @friend@nodebbinstace look at thisThen it wont notify? How am I supposed to include a friend in a thread?
-
@eeeee Your reply (what Lemmy would term a comment) would go out to friend@nodebbinstance but it would be up to nodebbinstance to resolve what post the comment was a reply to.
To illustrate what I mean about Lemmy and User Mentions in posts, see this post as an example. In the body of that post, the user Mentions 2 people -
[email protected]and[email protected]but neither of those people would have been notified of that post. You can see for yourself by looking at the activitypub representation of that post (by runningcurl --header 'accept: application/activity+json' --location https://lemmy.dbzer0.com/post/39126561 | jq .) and noting that there are no Mentions in the 'tag' section. By contrast, another user Mentions[email protected]in this comment, and she would have been notified of that (you can see that this time there is a Mention in activitypub representation of that coment).@julian For the other direction - as you've found out, Lemmy will first look at 'audience' for a root post and try to resolve it and bail if that doesn't work. If there's no 'audience', it will look in 'cc' to try to find a community and stops when it finds one. It won't look further, so you can't post in more than one community at a time, and you can't use a root post to post in Lemmy community and also notify a Lemmy user of it. It distinguishes between root posts and other posts because the root post is a Note will 'null' for 'inReplyTo'.
