Skip to content

Blogtastisch: 2. Blogs und das Fediverse

notizBlog
17 8 194

Diese Artikel könnten Dich auch interessieren.

  • 0 Stimmen
    5 Beiträge
    15 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
    18 Beiträge
    28 Aufrufe
    julian@community.nodebb.orgJ
    smallcircles@social.coop if you're not able to consume dev discussions on the fediverse and have to continually rely on people creating content on your platform then you need to raise that as an issue on your platform software.
  • FEP-9098: Custom emojis has been published.

    Uncategorized activitypub fep
    2
    0 Stimmen
    2 Beiträge
    12 Aufrufe
    julian@community.nodebb.orgJ
    silverpill@mitra.social I thought the plural of Emoji was Emoji
  • What drew you to ActivityPub?

    ActivityPub activitypub dotsocial blogs
    5
    0 Stimmen
    5 Beiträge
    16 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
    2 Beiträge
    11 Aufrufe
    julian@community.nodebb.orgJ
    jsit@social.coop Ghost? NodeBB? Just to name a couple
  • Backfilling Conversations: Two Major Approaches

    ActivityPub activitypub fep 7888 f228 171b
    26
    0 Stimmen
    26 Beiträge
    114 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
    17 Beiträge
    162 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
    47 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.