Skip to content

NodeBB v4.0.0 — Federate good times, come on!

Uncategorized
116 66 914

Diese Artikel könnten Dich auch interessieren.

  • 0 Stimmen
    18 Beiträge
    30 Aufrufe
    julian@community.nodebb.orgJ
    smallcircles@social.coop if you're not able to consume dev discussions on the fediverse and have to continually rely on people creating content on your platform then you need to raise that as an issue on your platform software.
  • Here's an idea.

    Uncategorized activitypub
    7
    0 Stimmen
    7 Beiträge
    23 Aufrufe
    julian@community.nodebb.orgJ
    benpate@mastodon.social Emissary interested? Har Har Har
  • 0 Stimmen
    2 Beiträge
    14 Aufrufe
    julian@community.nodebb.orgJ
    dfyx@social.helios42.de because followers and outbox collections can be faked.
  • Backfilling Conversations: Two Major Approaches

    ActivityPub activitypub fep 7888 f228 171b
    26
    0 Stimmen
    26 Beiträge
    119 Aufrufe
    julian@community.nodebb.orgJ
    > One weakness I have noticed in NodeBB's current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB. No, Lemmy does not implement either strategy, they rely on 1b12 only. If NodeBB is receiving parts of a topic that don't resolve up to the root-level post that might be something we can fix. I'll try to take a look at it.
  • 0 Stimmen
    9 Beiträge
    78 Aufrufe
    julian@community.nodebb.orgJ
    I suppose you're right in a way. The context owner is not supposed to be set by someone other than the context owner. It's a fallback mechanism intended for better compatibility with Mastodon. When a group is addressed and it is one of the local NodeBB categories, it will assume control If it is another group that it knows about but isn't same origin to the author, then no category is assumed.
  • Pleroma Webfinger compatibility

    ActivityPub activitypub pleroma webfinger
    10
    0 Stimmen
    10 Beiträge
    98 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
    167 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
    195 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