Skip to content

Blogtastisch: 2. Blogs und das Fediverse

notizBlog
17 8 182

Diese Artikel könnten Dich auch interessieren.

  • Backfilling Conversations: Two Major Approaches

    ActivityPub activitypub fep 7888 f228 171b
    26
    0 Stimmen
    26 Beiträge
    97 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
    13 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
    19 Beiträge
    77 Aufrufe
    julian@community.nodebb.orgJ
    PewDiePie built his fame and fortune on a centralized platform. I am not certain whether he will see the benefit of a decentralized future beyond dollar signs. Happy to be proven wrong.
  • Pixelfed Uptick in Monthly Active Users

    Uncategorized fediverse
    20
    1
    0 Stimmen
    20 Beiträge
    83 Aufrufe
    julian@community.nodebb.orgJ
    I would say that Pixelfed is closer to the microblog space than it is the threaded discussion space. It's essentially microblogging except with an image media focus (or video, in the case of Loops.) To each their own, some people communicate better using pictures, some better over short text, some better over long-form text. There's a space for them all
  • 0 Stimmen
    9 Beiträge
    64 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.
  • Pleroma Webfinger compatibility

    ActivityPub activitypub pleroma webfinger
    10
    0 Stimmen
    10 Beiträge
    87 Aufrufe
    julian@community.nodebb.orgJ
    trwnh@mastodon.social before, I was not sending Accept at all, now I am sending application/jrd+json.
  • 0 Stimmen
    17 Beiträge
    149 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
  • Post flair in PieFed

    Fediverse fediverse
    4
    0 Stimmen
    4 Beiträge
    41 Aufrufe
    julian@community.nodebb.orgJ
    I think the FEP process is overly complicated for what it is, but it's definitely helpful if you have multiple implementors on board. The easiest (but least accessible) solution is to document something on your own site, but that lacks the social proof that a finalized FEP has. Just some food for thought I'm looking to create an FEP for cross posting and would love to get the entire threadiverse dev community involved.