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
    3 Beiträge
    0 Aufrufe
    julian@community.nodebb.orgJ
    abraham@indieweb.social and they say ActivityPub is too technical ...
  • 0 Stimmen
    1 Beiträge
    4 Aufrufe
    Niemand hat geantwortet
  • 0 Stimmen
    2 Beiträge
    7 Aufrufe
    julian@community.nodebb.orgJ
    A reminder that the ForumWG meeting will begin in 15 minutes.
  • 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
  • Backfilling Conversations: Two Major Approaches

    ActivityPub activitypub fep 7888 f228 171b
    26
    0 Stimmen
    26 Beiträge
    163 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.
  • Unicode in handles

    ActivityPub unicode activitypub
    15
    0 Stimmen
    15 Beiträge
    158 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
  • 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