agnos.is Forums

After restarting NodeBB, I can load the category, though. Maybe some deadlock on initial import of the community.

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

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

@arachnibot@nodebb.arachnibot.com said in NodeBB v4.0.0 - Categories not following group actors:

@projectmoon@forum.agnos.is Adding UI for settings today. Will put on github once that's done (though I can share the core snippet in a bit). It can also work for auto-moving local tagged posts as well.

Should also mention that not every post from remote actors is tagged, so it might not catch everything. Could possibly have it just read any uncategorized posts and move based on users instead? Might be a better workaround for core, but if you have any thoughts let me know @julian@community.nodebb.org

Sounds good. Looking forward to trying it out. If there's a way to tie the post back to a Group Actor "user" (which are the local NodeBB users that share/boost the content within NodeBB), then you could probably make the algorithm more reliable. I don't know anything about the internals of NodeBB, though. Just spitballing ideas.

@arachnibot@nodebb.arachnibot.com said in NodeBB v4.0.0 - Categories not following group actors:

@julian@community.nodebb.org sounds good! I'm actually re-assigning the category before creation, rather than using the helpers in TopicTools, but I'll make the issue in case that should result in the same behavior

I'm very eager to try this plugin lol. Have you put it up on GitHub somewhere yet?

@baris@community.nodebb.org it looks pretty nice! Suggestions would be to have the ability to jump to the post via a button (if not already present). And maybe a user setting to expand or collapse these by default.