I'm wondering how content on threadiverse is automatically assigned its community when received by the software (e.g. PieFed, Lemmy, Mbin).
The answer I am expecting is "if the community is addressed (to, cc, audience), then it is slotted into that community".
However that causes issues for compatibility with microblogs... for example, [email protected] recently authored a post that mentioned [[email protected]](https://community.nodebb.org/category/[email protected]) and it got slotted into that community on NodeBB, which isn't correct since that group is private.
Better practice would be to only trust the addressed community if it is Announce'd by the community directly, but would fall short if my instance does not receive the Announce (say, if nobody follows the community), in which case we'd fall back to "uncategorized", which is where all microblog posts currently go. Then it's neither correct nor incorrect, I suppose.
I think this might be an issue where NodeBB tries to be too many things at once (microblog and threadiverse compatible).
I still think it would be good to update the synchronization function in admin settings to automatically slot any synced community/category into the local category, even if the sync only goes one way (e.g. with Lemmy not being able to remote follow category actors).
[email protected] it'll work better once cross-posting is built into NodeBB I think :smile: