NodeBB v4.0.0 — Federate good times, come on!

@freamon
Thank you!

That link with my reply redirects me here. Is there a way to read it somewhere else?
Maybe I need to connect with another activitypub account to read it there?

@julian
It could make sense to change a little bit the design of the remote users vs the local users, so it is easier to identify. Now that I know that I need to look for the @ and is easier but most people won´t know that.

I really love this new functionality. Thanks again!

@darkpollo Oh, sorry. It turns out that that link worked because I’m logged in to defcon.social.

I’ve crowbarred your comment into my dev instance for PieFed instead: https://pythag.net/post/4695#comment_27962

@phenomlab @cagatay long story short, it works, but this community is running NodeBB v4.1, which is slightly different. Should all work fine once v4.1 is released and everybody updates.

@julian This is really awesome! Forum software federated with Fedi-Power! Cool stuff. I love it

@julian@community.nodebb.org great. Thanks

@freamon Thank you for the additional proof.

This is great!

Trying to mentally organise how to use it and sync with a mastodon account so everything is “connected and synced”.

another thing: that image doesn’t federate properly (seems like it’s because it’s a relative link)

I’ve just installed a new instance of NodeBB and it works beautifully. Some questions:

1. Is it possible for categories to follow Lemmy communities in their sync settings? I seem to be able to follow Lemmy communities, but the categories are stuck on pending.
2. Same for NodeBB categories. Can I sync my own category with remote NodeBB categories?

Edit: the URLs stuck on pending are giving “invalid-id” errors in the log. As in invalid activitypub ids. I pasted the URLs of some Lemmy communities and NodeBB categories.

Edit 2: Found the topic about this. https://community.nodebb.org/post/102818

@projectmoon@forum.agnos.is

1. Is currently outstanding: https://github.com/LemmyNet/lemmy/issues/5354

2. You should be able to do this, although I may have to double check the logic. There have been reports that it is not working as expected.

@julian@community.nodebb.org said in NodeBB v4.0.0 — Federate good times, come on!:

I’m wondering, as a stopgap solution, would it make sense to have some kind of rules engine that allows topics coming in from the fediverse to automatically be moved to NodeBB categories? Kind of like a somewhat less elegant sync.

Edit: like automatically assigning incoming topics based on tags seems like a particularly easy solution?

@julian great job!

@julian

@julian I read this whole thing wondering how NodeBB posts would look from my instance and then clicked your link at the end and realized I'd been reading one the whole time lol. Super cool, hope this takes off!

@projectmoon@forum.agnos.is thanks for the suggestion, that’s definitely something I’d want to consider.

Sort of a post queue for federated content that needs automatic or manual review before it is automatically slotted in a category.

@julian@community.nodebb.org Thanks. Even something as simple as mappin topic tags to categories automatically would work I think.

@projectmoon@forum.agnos.is careful with that though, not all tags are the same, some have a higher signal-to-noise ratio, but others would just be filled with garbage

@julian so cool, can't wait to upgrade my nodebb forum to V4 (I'm exclusively on mobile for a few days)

@julian@community.nodebb.org said in NodeBB v4.0.0 — Federate good times, come on!:

@projectmoon@forum.agnos.is careful with that though, not all tags are the same, some have a higher signal-to-noise ratio, but others would just be filled with garbage

I think the best way, then, would be to have rules that map various group actor URLs to categories, and possibly also tags. Nothing automatic. Only configured. Of course, once Lemmy fixes the ability of Group actors to follow other Group actors, this will be a non-issue.

One other possible solution, which is employed by Misskey et al., is a proxy actor. It’s a special user that follows other users, and relays info within its own instance. It’s used for doing things like adding a remote user to a list without directly following them. The proxy account follows the user, and then your local instance adds the remote user to your list. But all ActivityPub interactions go through the proxy user.

If you have deployed NodeBB v4, and you updated to v4.0.1, please update now to v4.0.2 which fixes a regression that silently broke outgoing user follows.

@julian@community.nodebb.org said in NodeBB v4.0.0 — Federate good times, come on!:
Do we need need to refollow?