Skip to content

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

Uncategorized
116 66 1.3k

Diese Artikel könnten Dich auch interessieren.

  • Bridge as a service...

    Uncategorized bridgyfed fediverse activitypub
    8
    0 Stimmen
    8 Beiträge
    0 Aufrufe
    julian@community.nodebb.orgJ
    snarfed.org@fed.brid.gy I wanted to tag you but I wasn't sure which account to tag
  • Long-form articles

    Uncategorized activitypub
    21
    0 Stimmen
    21 Beiträge
    39 Aufrufe
    julian@community.nodebb.orgJ
    feb@loma.ml well the great thing is the FEP is still a draft and your opinions are welcome cc jupiter_rowland@hub.netzgemeinde.eu silverpill@mitra.social
  • From: blenderdumbass .

    Uncategorized activitypub fediverse mastodon bdserver python
    2
    0 Stimmen
    2 Beiträge
    6 Aufrufe
    julian@community.nodebb.orgJ
    blenderdumbass@mastodon.online why does this article keep showing up with a newer timestamp?
  • 7.2.0 – Follow ups

    Uncategorized activitypub blocks fediverse followers following
    2
    2
    0 Stimmen
    2 Beiträge
    8 Aufrufe
    julian@community.nodebb.orgJ
    pfefferle@mastodon.social oh interesting! > We’ve also made it easier to follow people from other sites. When you click “Follow” on someone else’s blog, you’ll now be taken to your own site to complete it. It keeps things simple and familiar, even when you start following someone from another site. How do you know the user pressing the button has a WordPress site?
  • Idle thought re: account delegation

    ActivityPub activitypub c2s
    6
    0 Stimmen
    6 Beiträge
    21 Aufrufe
    julian@community.nodebb.orgJ
    evan@cosocial.ca that's cool, so hopefully I'll have something to test against besides another NodeBB server
  • Fun with Federation: Lemmy edition

    ActivityPub nodebb lemmy activitypub
    5
    0 Stimmen
    5 Beiträge
    54 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
    9 Beiträge
    116 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.
  • 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