Skip to content

As someone who has developed several #ActivityPub software implementations ([Fedify], [Hollo], [BotKit], and [Hackers' Pub]), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

Uncategorized
43 9 0

Diese Artikel könnten Dich auch interessieren.

  • 0 Stimmen
    2 Beiträge
    6 Aufrufe
    julian@community.nodebb.orgJ
    dfyx@social.helios42.de because followers and outbox collections can be faked.
  • Communities not existing on all instances is a big problem.

    Fediverse fediverse
    23
    0 Stimmen
    23 Beiträge
    19 Aufrufe
    julian@community.nodebb.orgJ
    Yes. When the reply is posted to C, it is sent to A. A then sends as:Announce to C, as well as any other communities that follow it. B seems to be irrelevant here.
  • 0 Stimmen
    5 Beiträge
    11 Aufrufe
    julian@community.nodebb.orgJ
    silverpill@mitra.social I wasn't aware that there were sections pertaining to context. I'll have to review more closely.
  • OF alternative fediverse?

    Uncategorized fediverse
    12
    0 Stimmen
    12 Beiträge
    24 Aufrufe
    julian@community.nodebb.orgJ
    Tell me about it! There are some very cool people (i.e. thisismissem@hachyderm.io) working on content classification and tagging so that the burden of filtering out this kind of content isn't borne by server admins directly.
  • 0 Stimmen
    5 Beiträge
    52 Aufrufe
    julian@community.nodebb.orgJ
    melroy@kbin.melroy.org oh sorry to hear that hopefully Dan hasn't moved on from FediDB already.
  • 0 Stimmen
    17 Beiträge
    153 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.
  • Blogtastisch: 2. Blogs und das Fediverse

    notizBlog activitypub blogs fediblog fediverse weblogs
    17
    1
    0 Stimmen
    17 Beiträge
    184 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