Skip to content

Bug: unable to follow some friendica accounts

ActivityPub
7 3 28
  • 0 Stimmen
    3 Beiträge
    0 Aufrufe
    julian@community.nodebb.orgJ
    Jon-Pincus hey check out that topic loading from within this NodeBB cc admin@discussions.thenexus.today
  • How much can I extend an OrderedCollection?

    ActivityPub activitypub
    1
    0 Stimmen
    1 Beiträge
    6 Aufrufe
    Niemand hat geantwortet
  • Final thoughts re: FediCon 2025

    ActivityPub fedicon fedicon2025 activitypub
    17
    0 Stimmen
    17 Beiträge
    39 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!
  • Fedicon Livestream

    ActivityPub fedicon fedicon2025
    64
    0 Stimmen
    64 Beiträge
    233 Aufrufe
    chigaze@mstdn.caC
    @julian I have that mug!@chad @evan
  • Idle thought re: account delegation

    ActivityPub activitypub c2s
    6
    0 Stimmen
    6 Beiträge
    88 Aufrufe
    julian@community.nodebb.orgJ
    evan@cosocial.ca that's cool, so hopefully I'll have something to test against besides another NodeBB server
  • What drew you to ActivityPub?

    ActivityPub activitypub dotsocial blogs
    5
    0 Stimmen
    5 Beiträge
    85 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
    742 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
    294 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.