Skip to content

Automatic category/community assignment on received object

ActivityPub
3 2 26
  • 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).

  • I think it's important to get an Announce, because the actor who addressed the community might be blocked by that community, or might not be a member of it (if the community is private).
    You can try to retrieve the outbox of the addressed community to verify that a post was actually Announce'd

    @activitypub

  • I think it's important to get an Announce, because the actor who addressed the community might be blocked by that community, or might not be a member of it (if the community is private).
    You can try to retrieve the outbox of the addressed community to verify that a post was actually Announce'd

    @activitypub

    silverpill@mitra.social I thought about checking against the outbox, but there's a potential race condition that could occur if I receive the Create(Note) at roughly the same time as the community, but the community hasn't processed the activity yet. In that scenario, the activity would not be in the outbox for checking.

    The same thing would happen if there was some out-of-band check for object membership in a collection (not that there is one right now).

Diese Artikel könnten Dich auch interessieren.

  • 0 Stimmen
    1 Beiträge
    2 Aufrufe
    Niemand hat geantwortet
  • Fun with Federation: Lemmy edition

    ActivityPub nodebb lemmy activitypub
    5
    0 Stimmen
    5 Beiträge
    8 Aufrufe
    julian@community.nodebb.orgJ
    nutomic@lemmy.ml let me know if I got any of the details wrong. Much thanks to your team for the assist in debugging!
  • 0 Stimmen
    2 Beiträge
    19 Aufrufe
    julian@community.nodebb.orgJ
    rood@aus.social that... is actually not a bad idea If every account exposed their time zone, then your client or server could simply delay the post the appropriate amount until it's your time zone... 10pm their time, shows up 10pm your time. oooooh.
  • Unicode in handles

    ActivityPub unicode activitypub
    15
    0 Stimmen
    15 Beiträge
    88 Aufrufe
    julian@community.nodebb.orgJ
    לאצי the usernames work fine locally (that is, on the site itself). It's when interoperating with other sites not running NodeBB where there are issues, it seems
  • I wrote a #FEP about actor statuses.

    Uncategorized fep activitypub
    2
    1
    0 Stimmen
    2 Beiträge
    30 Aufrufe
    julian@community.nodebb.orgJ
    Man!!! That screenshot takes me back..
  • Pleroma Webfinger compatibility

    ActivityPub activitypub pleroma webfinger
    10
    0 Stimmen
    10 Beiträge
    66 Aufrufe
    julian@community.nodebb.orgJ
    trwnh@mastodon.social before, I was not sending Accept at all, now I am sending application/jrd+json.
  • 0 Stimmen
    17 Beiträge
    115 Aufrufe
    julian@community.nodebb.orgJ
    Hey rimu@piefed.social thanks for responding (and sorry for the late reply!) I am not married to the Announce([Article|Note|Page]) approach, so I am definitely open to Create([Article|Note|Page]) with a back-reference. I think I went the former direction because there is a known fallback mechanism — the Announce is treated as a share/boost/repost as normal. However, sending the Create also is fine I think. However, do we need a backreference? In my limited research, it seems that Piefed, et al. picks the first Group actor and associates the post with that community. If I sent over a Create(Article) with two Group actors addressed, could Piefed associate the post with the first, and initiate a cross-post with the remaining Group actors? Secondly, is how to handle sync. 1b12 relies on communities having reciprocal followers in order for two-way synchronization to be established. On my end since I know it is cross-posted I will now send 1b12 activities to cross-posted communities, but can Piefed, et al. send 1b12 activities back as well, in the absence of followers? cc andrew_s@piefed.social nutomic@lemmy.ml melroy@kbin.melroy.org bentigorlich@gehirneimer.de
  • Blogtastisch: 2. Blogs und das Fediverse

    notizBlog activitypub blogs fediblog fediverse weblogs
    17
    1
    0 Stimmen
    17 Beiträge
    146 Aufrufe
    caromite@troet.cafeC
    @pfefferle Wow, danke für das super Video! Für mich ist das Fediverse noch ganz neu, hab jetzt mein Blog föderiert und mir einen Account bei Mastodon erstellt. Fühle mich noch etwas verloren, aber bin überzeugt auf dem richtigen Weg zu sein