Skip to content

Backfilling Conversations: Two Major Approaches

ActivityPub
26 8 649
  • Bridge as a service...

    ActivityPub Test Kategorie bridgyfed fediverse activitypub
    8
    0 Stimmen
    8 Beiträge
    2 Aufrufe
    julian@community.nodebb.orgJ
    snarfed.org@fed.brid.gy I wanted to tag you but I wasn't sure which account to tag
  • Final thoughts re: FediCon 2025

    ActivityPub fedicon fedicon2025 activitypub
    17
    0 Stimmen
    17 Beiträge
    18 Aufrufe
    jdp23@neuromatch.socialJ
    @julian Also, speaking of fixable deficiencies, my edits here don't seem to propagate to SocialHub . Without knowing the code I'm confident it's fixable because my edits did propagate to the NodeBB thread at https://community.nodebb.org/topic/18932/final-thoughts-re-fedicon-2025/14 , great to see!
  • 7.2.0 – Follow ups

    ActivityPub Test Kategorie activitypub blocks fediverse followers following
    2
    2
    0 Stimmen
    2 Beiträge
    26 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?
  • 0 Stimmen
    5 Beiträge
    68 Aufrufe
    julian@community.nodebb.orgJ
    deadsuperhero@social.wedistribute.org I'm of the opinion that a solid collection of links is the easiest way to get there. FediDevs set out to do that but I think the best approach would be to update ActivityPub.rocks with the links and docs instead. Join the WG for it!! Led by evan@cosocial.ca and j12t@j12t.social
  • 0 Stimmen
    1 Beiträge
    22 Aufrufe
    Niemand hat geantwortet
  • Fun with Federation: Lemmy edition

    ActivityPub nodebb lemmy activitypub
    5
    0 Stimmen
    5 Beiträge
    113 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
    17 Beiträge
    603 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
  • Live testing of remote categories

    ActivityPub Test Kategorie activitypub nodebbactivityp
    63
    2
    0 Stimmen
    63 Beiträge
    2k Aufrufe
    julian@community.nodebb.orgJ
    @pfefferle@mastodon.social just wanted to poke you about this issue again. The latest updates to NodeBB now do a webfinger backcheck to ensure that the actor has a valid webfinger entry for their purported handle. If it does not, then the user is not properly created. Mastodon also does this. This check is probably for security as well as for preventing handle collisions. The multilingual plugin in conjunction with the ActivityPub plugin creates users that share the same handle, and that causes issues with federated content. For example, this article by @jonvt@vivaldi.com will load up just fine in Mastodon, but this japanese article by @akira@vivaldi.com will not, because that second article's attributedTo is https://vivaldi.com/ja/?author=176, which fails that check (the author's ID is actually https://vivaldi.com?author=176 as per the handle backcheck) cc @AltCode