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

[julian@community.nodebb.org]

@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.

[projectmoon@forum.agnos.is]

@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?

[raul@mastodon.in4matics.cat]

@julian great job!

[dani@mastodon.dtalens.com]

@julian

[germ@deletethis.lol]

@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!

[julian@community.nodebb.org]

@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.

[projectmoon@forum.agnos.is]

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

[julian@community.nodebb.org]

@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

[dandandin@mastodon.uno]

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

[projectmoon@forum.agnos.is]

@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.