agnos.is Forums

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

Not specifically that URL, no. Now I just tried it. It resulted in a deadlock in Postgres.

2025-04-08T12:42:10.933614676Z 2025-04-08 12:42:10.933 UTC [32590] DETAIL:  Process 32590 waits for ShareLock on transaction 35424413; blocked by process 32626.
2025-04-08T12:42:10.933621228Z 	Process 32626 waits for ShareLock on transaction 35424434; blocked by process 32590.
2025-04-08T12:42:10.933624695Z 	Process 32590: 
2025-04-08T12:42:10.933626920Z 	INSERT INTO "legacy_object" ("_key", "type")
2025-04-08T12:42:10.933629244Z 	SELECT k, $2::TEXT::LEGACY_OBJECT_TYPE
2025-04-08T12:42:10.933631398Z 	  FROM UNNEST($1::TEXT[]) k
2025-04-08T12:42:10.933633432Z 	    ON CONFLICT
2025-04-08T12:42:10.933635396Z 	    DO NOTHING
2025-04-08T12:42:10.933637329Z 	Process 32626: 
2025-04-08T12:42:10.933639423Z 	INSERT INTO "legacy_object" ("_key", "type")
2025-04-08T12:42:10.933641588Z 	SELECT k, $2::TEXT::LEGACY_OBJECT_TYPE
2025-04-08T12:42:10.933643603Z 	  FROM UNNEST($1::TEXT[]) k
2025-04-08T12:42:10.933645586Z 	    ON CONFLICT
2025-04-08T12:42:10.933647519Z 	    DO NOTHING
2025-04-08T12:42:10.933654783Z 2025-04-08 12:42:10.933 UTC [32590] HINT:  See server log for query details.
2025-04-08T12:42:10.933656978Z 2025-04-08 12:42:10.933 UTC [32590] CONTEXT:  while inserting index tuple (6227,69) in relation "legacy_object"
2025-04-08T12:42:10.933659042Z 2025-04-08 12:42:10.933 UTC [32590] STATEMENT:  
2025-04-08T12:42:10.933660966Z 	INSERT INTO "legacy_object" ("_key", "type")
2025-04-08T12:42:10.933663000Z 	SELECT k, $2::TEXT::LEGACY_OBJECT_TYPE
2025-04-08T12:42:10.933664863Z 	  FROM UNNEST($1::TEXT[]) k
2025-04-08T12:42:10.933666666Z 	    ON CONFLICT
2025-04-08T12:42:10.933668430Z 	    DO NOTHING

I've successfully managed to find and track https://sh.itjust.works/c/localllama from my instance. But when I try, for example, https://lemmy.world/c/technology, I can't find anything. These Lemmy communities DO, however, show up as users on my NodeBB instance. Is there something I'm doing wrong? I tried going directly to /category/@[email protected] too.

Does this refactoring also include changes to the synchronization of local + remote categories? Or is it still trying to follow Group actors as a Group, which Lemmy does not like?

@[email protected] something of an alignment would look nice, yeah.

@[email protected] 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.

@[email protected] yes, that function is there. Then maybe the best compromise would be to essentially add a reverse of that reply spotlight feature, so you can read the original post without the page jumping.

@[email protected] I think it would be a good idea to show posts that are in-reply-to as quotes in the reply. Right now, all you see is a tiny "replied to..." on the top. Since NodeBB can interoperate with Lemmy, it can get kind of confusing to follow some threads, as the forum UX presents the discussion as linear, while Lemmy is multi-threaded. Showing the original post as a quote would help with following the discussion.

@[email protected] said in NodeBB v4.0.0 — Federate good times, come on!:
Do we need need to refollow?

Out of curiosity: what plugin/setting does one need to use in order to get a header like the NodeBB.org forums? With the links up top.

@[email protected] said in NodeBB v4.0.0 - Categories not following group actors:

@[email protected] 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?

They show up as a link to a long uuid, which when clicked, goes to 404.

@[email protected] Is there an open GitHub issue for federated images not showing up? It creates links, but the upload seems to have failed, so it just returns a 404 on my end.

If you have a wireless card (or don't need wireless) capable of working with Linux Libre, then by all means use it. There is no technological advantage to using Linux-Libre. There are principle advantages. I say this as someone who uses Linux-Libre on my Gentoo laptop (and maintains an overlay with an ebuild for Linux-Libre).

@[email protected] Only one way to find out!

@[email protected] said in NodeBB v4.0.0 - Categories not following group actors:

@[email protected] 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 @[email protected]

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.

@[email protected] said in NodeBB v4.0.0 — Federate good times, come on!:

@[email protected] 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.

Was a link posted to it? Also I'm noticing that edits don't seem to fully federate. 🤨

@[email protected] funnily enough, I switched from Linkwarden to Hoarder. I like the smart lists. Just bookmark everything, check it later.

@[email protected] can you share a link to it?