Skip to content

Blogtastisch: 2. Blogs und das Fediverse

notizBlog
17 8 212

Diese Artikel könnten Dich auch interessieren.

  • I uploaded the fourth FediCon 2025 video:

    Uncategorized fedicon fedicon2025 fediverse
    2
    0 Stimmen
    2 Beiträge
    2 Aufrufe
    julian@community.nodebb.orgJ
    reiver@mastodon.social woo! Keep it up!
  • Final thoughts re: FediCon 2025

    ActivityPub fedicon fedicon2025 activitypub
    17
    0 Stimmen
    17 Beiträge
    13 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

    Uncategorized activitypub blocks fediverse followers following
    2
    2
    0 Stimmen
    2 Beiträge
    4 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
    1 Beiträge
    5 Aufrufe
    Niemand hat geantwortet
  • Come see @atomicpoet host his panel at FediCon

    Uncategorized fedicon fedicon2025 fediverse
    2
    0 Stimmen
    2 Beiträge
    10 Aufrufe
    julian@community.nodebb.orgJ
    fedicon@techhub.social reiver@mastodon.social what does the AYBABTU reference mean in relation to AP? I suppose I will have to wait for atomicpoet@atomicpoet.org to explain...
  • Backfilling Conversations: Two Major Approaches

    ActivityPub activitypub fep 7888 f228 171b
    26
    0 Stimmen
    26 Beiträge
    141 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.
  • Bounce Helps You Switch Networks

    Fediverse fediverse
    2
    1
    0 Stimmen
    2 Beiträge
    27 Aufrufe
    julian@community.nodebb.orgJ
    Hey deadsuperhero@lemmy.world have you tried updating to the latest NodeBB? You can post to Lemmy communities from there too!
  • 0 Stimmen
    17 Beiträge
    189 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