Skip to content
0
  • Home
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
  • Home
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Wandering Adventure Party

  1. Home
  2. ActivityPub
  3. Automatic category/community assignment on received object

Automatic category/community assignment on received object

Scheduled Pinned Locked Moved ActivityPub
activitypubthreadiverse
1 Posts 1 Posters 1 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • julianJ This user is from outside of this forum
    julianJ This user is from outside of this forum
    julian
    wrote on last edited by
    #1

    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, silverpill@mitra.social recently authored a post that mentioned [swf@socialwebfoundation.org](https://community.nodebb.org/category/swf@socialwebfoundation.org) 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).

    1 Reply Last reply
    1
    2
    • System shared this topic on
      System shared this topic

    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Login or register to search.
    Powered by NodeBB Contributors
    • First post
      Last post