Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
  1. Home
  2. Categories
  3. General Discussion
  4. finally 🥳'n#loops #activityPub

finally 🥳'n#loops #activityPub

General Discussion
1 1 15
Log in to reply

Feed RSS
finally 🥳'n#loops #activityPub

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • django@social.coopundefined

    ActivityPub client development is coming along!

    General Discussion activitypub c2s
    20
    1 Votes
    20 Posts
    23 Views
    silverpill@mitra.socialundefined
    @phnt C2S API has always been a solution looking for a problem, but it is similar enough to FEP-ae97 API, so I have no issue with people devoting their time to fixing C2S.However, almost nobody actually works on it. There is a lot of cheap talk, but anyone who actually tries to implement C2S quickly realizes how broken it is and gives up. Most progress so far has been made by a single developer (btw: I began to document some aspects of his implementation in FEP-9f9f: Collections).>fixing the complete mess of a specification and making a v2 spec that isn't ambiguous and open-ended as a typical corporate privacy policyThe working group is too busy renaming https://www.w3.org/ns/activitystreams#Public to as:Public@julian @django
  • toddsundsted@epiktistes.comundefined

    Experimenting with x-ray mode for ktistec.

    General Discussion ktistec activitypub
    1
    0 Votes
    1 Posts
    5 Views
    toddsundsted@epiktistes.comundefined
    Experimenting with x-ray mode for ktistec.#ktistec #activitypub
  • julian@activitypub.spaceundefined

    Minutes from 6 November 2025 WG Meeting

    Uncategorized forumwg swicg activitypub socialcg
    15
    0 Votes
    15 Posts
    50 Views
    julian@activitypub.spaceundefined
    trwnh@mastodon.social Yes, you're right. There are nuances and situations where you would explicitly not want to inherit the root object's context. I am dealing with the typical day-to-day use case of replying to an object with the expectation that is be part of the same existing context. However I am more than happy to make this clear in the FEP and spell out alternative situations where context inheritance would not apply. The situation I found myself in was one where anybody can (and does) include whatever context they want. In that case, it's difficult to determine whether disparate contexts are actually referring to a common set of the same objects, or whether they were disparate on purpose (i.e. a fork.) To that end, it meant that as a receiver there was no guarantee that any contexts I'd be sent would map to any contexts I know. Strict root-level inheritance for the common use-case would at least disambiguate a lot of this.
  • stevenixon@mastodon.socialundefined

    If #Funkwhale is #federated and uses #ActivityPub then why do I need an account?

    Uncategorized funkwhale federated activitypub
    2
    0 Votes
    2 Posts
    21 Views
    julian@activitypub.spaceundefined
    stevenixon@mastodon.social you're not wrong about that! Some people are working on getting there, but right now you'll have to create a new account.