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
    4 Beiträge
    7 Aufrufe
    julian@community.nodebb.orgJ
    silverpill@mitra.social there was! I am very bad with putting together minutes but I will put some together tomorrow (hopefully) For cross posting essentially I outlined how Piefed does it, and how NodeBB hopes to do it differently, but there are some moderation concerns. Will elaborate more in the 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?
  • 0 Stimmen
    2 Beiträge
    16 Aufrufe
    julian@community.nodebb.orgJ
    tom@tomkahe.com That's a fun idea... I'm doing it (using FetchRSS, though) in NodeBB. community.openbeta.io pulls in a bunch of climbing news websites via their RSS feeds and re-publishes it onto fedi
  • 0 Stimmen
    1 Beiträge
    12 Aufrufe
    Niemand hat geantwortet
  • What drew you to ActivityPub?

    ActivityPub activitypub dotsocial blogs
    5
    0 Stimmen
    5 Beiträge
    30 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!
  • 0 Stimmen
    9 Beiträge
    116 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.
  • 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
  • Blogtastisch: 2. Blogs und das Fediverse

    notizBlog activitypub blogs fediblog fediverse weblogs
    17
    1
    0 Stimmen
    17 Beiträge
    231 Aufrufe
    caromite@troet.cafeC
    @pfefferle Wow, danke für das super Video! Für mich ist das Fediverse noch ganz neu, hab jetzt mein Blog föderiert und mir einen Account bei Mastodon erstellt. Fühle mich noch etwas verloren, aber bin überzeugt auf dem richtigen Weg zu sein