NodeBB v4.0.0 - Categories not following group actors
-
Seems my testing ground can't follow sync with group actors/remote categories. I'm assuming the null id is related, but haven't figured out how to remove it yet (unfollow button just refreshes the page)
-
P projectmoon shared this topic
-
As a stopgap solution until Lemmy fixes this, would it make sense to have some kind of auto assignment of categories to posts, based on tags? Is there a plugin for that?
-
Not a bad idea. Whipped one up that can work on local and remote posts (though they might need to be followed by the category for it to count? Unsure if it'll work without that)
-
@arachnibot yes, offhand I think it should (although I didn't check the code).
When remote content is parsed I just call the same internal methods to create a topic.
-
@[email protected] can you share a link to it?
-
@[email protected] @arachnibot I love how I want to add this to the core logic and someone beats me to it with a third party plugin.
It's absolutely fantastic, and exactly how our plugin system should work!
-
Was a link posted to it? Also I'm noticing that edits don't seem to fully federate. 🤨
-
@[email protected] no link yet, was just speaking hypothetically
-
@[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]
-
@[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] actually once you mentioned that I got a rough version of that working. I'm not sure if reading the audience property is the right move, but we'll see if it works on my end I guess?
-
@[email protected] Only one way to find out!
-
@[email protected] for Lemmy? No, not anymore.
A future version of Lemmy will remove
audience. You'll have to dereference the addressing fields (to,cc). -
Got it! I just noticed something similar, so thanks for the confirmation!
