home.social

#litepub — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #litepub, aggregated by home.social.

  1. CW: litepub

    What is the motivation for encouraging LitePub implementors to "supply a locally hosted version of the LitePub JSON-LD Context"?

    Is it just for people using full-out JSON-LD parsers?

    Won't this create problems for people using parsers that do NOT go download and interpret context-URIs? And instead just hard-code the vocabulary in their code?

    #ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #JSONLD #LitePub

  2. The LitePub website has a lot of broken links (on their own site).

    How I understand LitePub protocol is — it is a protocol that was meant to work with ActivityPub, but is meant to be simple & light-weight.

    #activitypub #activitystreams #fedidevs #fediverse #json #jsonld #litepub

  3. Huh, can any #LitePub folk link me to the emojireact spec? I'm not easily finding it, but there's references in this code to litepub.social/ns#emojireact .

  4. @jared hnnnnng yes. That would be the responsible thing to do. I should learn more about how #mastodon works, or at least about the protocol #LitePub.

    Have you researched #misskey?

  5. @krozruch @fnn
    Isn't #litePub supposed to be a sublanguage of #activitypub, with less features? Adding closed extensions will add so much mess...

  6. Ephemeral Posts are coming to :pixelfed:

    We are working with Pleroma developers to ensure full support between Pixelfed and Pleroma!

    @kaniini has created the LitePub extension, and we look forward to working with them on this new and exciting feature.

    #activityPub #ephemeralPosts #litePub #pleroma

  7. @dirb @jalcine I am not surprised that somebody would go to Mastodon first. But at least they seem to be accepting noncompatibility with other implementations as bugs.

    It will be good when there are narrower test suites available, intended for the Fediverse in practice rather than for ActivityPub. I understand that's what @feneas has or is working on, and that the #LitePub people will also have one.
  8. J'apprends l'existence de #LitePub qui serait comme #ActvityPub mais en plus léger ?

  9. That's addressed early in the thread. Pleroma is an opinionated implementation just like Mastodon is, not a reference implementation. It even has its own specification effort tied to it, #litepub.
  10. I'm trying to punt on looking at adding ActivityPub support into #Koype because of my eagerness to have #LitePub support.

    I could see it having both (or me implementing AP to have better understanding of what LP might need)

  11. @Are0h I'm just trying to figure out how to make this happen in a secure and sustainable manner. all of the tech to begin with is there. I'm still going to toy and wait until #litepub is more stabilized before I begin tinkering

  12. Getting closer to having #Koype more #indieweb compliant. I'm using Indigenous (indigenous.adobe.pub) for Android to handle mobile posting and Quill (quill.p3k.io) to handle desktop posting. So far, it's a little janky.

    Once I get proper JF2 storage, then I can probably have simple MF2 markup (and maybe squeeze in some other markup formats?) in there.

    After that, I can either look into making it simpler to deploy/turn-key host or look into adding #litepub support.