Assigning a thread to a remote category
-
Hello everyone,
I'm the administrator of a NodeBB instance (4.9.1) and I also display other remote categories within that instance (the communities of a Lemmy instance I manage).I would like to point out that I have not opened an issue on Github because I am not sure whether the problem in question is a bug or just the consequence of a deliberate choice by the developers.
I've noticed that sometimes, when a Fediverse user posts a mention of a Lemmy community, while the Lemmy server correctly categorizes that conversation, the NodeBB server displaying the remote category may not "understand" that the post belongs to the community in question.
In the past, when I noticed these anomalies, I could resolve the issue by "moving the thread" using my administrator privileges. When I moved the thread, I was only shown the local category tree, but I could search for remote categories using the search function.
Not anymore.
Has something changed, or am I misremembering?
I hope I explained myself correctly, but since I use an automatic translator, I may have explained the problem incorrectly.
-
Hello everyone,
I'm the administrator of a NodeBB instance (4.9.1) and I also display other remote categories within that instance (the communities of a Lemmy instance I manage).I would like to point out that I have not opened an issue on Github because I am not sure whether the problem in question is a bug or just the consequence of a deliberate choice by the developers.
I've noticed that sometimes, when a Fediverse user posts a mention of a Lemmy community, while the Lemmy server correctly categorizes that conversation, the NodeBB server displaying the remote category may not "understand" that the post belongs to the community in question.
In the past, when I noticed these anomalies, I could resolve the issue by "moving the thread" using my administrator privileges. When I moved the thread, I was only shown the local category tree, but I could search for remote categories using the search function.
Not anymore.
Has something changed, or am I misremembering?
I hope I explained myself correctly, but since I use an automatic translator, I may have explained the problem incorrectly.
Can you check if the category you are searching is in the
categories:namesorted set? In mongodb it would be.db.objects.find({_key: "categories:name"}); -
Hello everyone,
I'm the administrator of a NodeBB instance (4.9.1) and I also display other remote categories within that instance (the communities of a Lemmy instance I manage).I would like to point out that I have not opened an issue on Github because I am not sure whether the problem in question is a bug or just the consequence of a deliberate choice by the developers.
I've noticed that sometimes, when a Fediverse user posts a mention of a Lemmy community, while the Lemmy server correctly categorizes that conversation, the NodeBB server displaying the remote category may not "understand" that the post belongs to the community in question.
In the past, when I noticed these anomalies, I could resolve the issue by "moving the thread" using my administrator privileges. When I moved the thread, I was only shown the local category tree, but I could search for remote categories using the search function.
Not anymore.
Has something changed, or am I misremembering?
I hope I explained myself correctly, but since I use an automatic translator, I may have explained the problem incorrectly.
> @informapirata said:
>
> I've noticed that sometimes, when a Fediverse user posts a mention of a Lemmy community, while the Lemmy server correctly categorizes that conversation, the NodeBB server displaying the remote category may not "understand" that the post belongs to the community in question.This is a bit of an edge case, worth opening an issue for.
On the wider fediverse it is possible to create topics by mentioning the category. Depending on software, that published activity doesn't actually contain the community, and if your NodeBB sees that post first, then it won't have a category assigned to it.
I can try patching around that behaviour.
-
Thanks for the reply @julian !
I've created an issue on Github: https://github.com/NodeBB/NodeBB/issues/14040I hope my English translathane allowed me to be understandable
-
Good evening, @julian !
Were you finally able to come up with a solution for this issue? Or do you think the possible solutions would have a negative impact on the system? -
Good evening, @julian !
Were you finally able to come up with a solution for this issue? Or do you think the possible solutions would have a negative impact on the system?@informapirata sorry, I have not taken a look at this issue yet.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login