Skip to content

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

Uncategorized
116 66 1.3k

Diese Artikel könnten Dich auch interessieren.

  • 0 Stimmen
    7 Beiträge
    12 Aufrufe
    julian@community.nodebb.orgJ
    thisismissem@hachyderm.io it was a very weird exchange! I don't understand what that was about.
  • hi folks

    Uncategorized activitypub golang
    5
    0 Stimmen
    5 Beiträge
    33 Aufrufe
    julian@community.nodebb.orgJ
    No better place to talk ActivityPub than the fediverse! evan@cosocial.ca radhitya@pl.100indie.org reiver@mastodon.social
  • 0 Stimmen
    1 Beiträge
    12 Aufrufe
    Niemand hat geantwortet
  • What drew you to ActivityPub?

    ActivityPub activitypub dotsocial blogs
    5
    0 Stimmen
    5 Beiträge
    30 Aufrufe
    julian@community.nodebb.orgJ
    > Getting a critical mass of people to create yet another account was always a major obstacle. I see and have experienced this effect time and time again, and we're getting closer and closer to the point where the protocol implementations can abstract away the messy bits. Gaining critical mass among devs is the first step!
  • Backfilling Conversations: Two Major Approaches

    ActivityPub activitypub fep 7888 f228 171b
    26
    0 Stimmen
    26 Beiträge
    162 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
    115 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
    123 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
    193 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