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. Big news!

Big news!

General Discussion
4 4 19
Log in to reply

Feed RSS
Big news!

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • jdt@enigmatick.socialundefined

    `keyId` is a problem.

    General Discussion activitypub
    8
    0 Votes
    8 Posts
    1 Views
    jdt@enigmatick.socialundefined
    @eyeinthesky@mastodon.social Thanks. In your description, does "primary resource" refer to https://enigmatick.social/user/jdt#main-key or https://enigmatick.social/user/jdt? That matters since the latter is not known as accurate until the resolution is complete. Practically speaking, it's clear that I can retrieve the Actor resource using the fragment ID (https://enigmatick.social/user/jdt#main-key) and then retrieve the owner field from the publicKey field of that object to arrive at the Actor ID. Although since the leap to look in the publicKey field doesn't seem like it's specified by LD-JSON, I suppose just pulling the id from the returned Actor object directly might be as valid.
  • pfefferle@mastodon.socialundefined

    if you have issues with the #ActivityPub plugin for #WordPress or curious about how it works.

    General Discussion activitypub wordpress supportrotation
    22
    0 Votes
    22 Posts
    37 Views
    pfefferle@mastodon.socialundefined
    @AdamStuartSmith yes! But it will only show up if the post you added it to has likes or shares. That said, it will not work on the frontage, only on singular posts.
  • flipboard@flipboard.socialundefined

    Missed @ben's keynote at this year's @fediforum?

    Fediverso opensocial opensocialweb community commmunitybuilding fediforum fediverse media activitypub
    1
    0 Votes
    1 Posts
    15 Views
    flipboard@flipboard.socialundefined
    Missed @ben's keynote at this year's @fediforum? Here's the full transcript. "The opportunity right now isn't to build a better Twitter or to provide a nice place for people who care about Linux to chat: it's to build infrastructure that vulnerable people can actually use to organize, to communicate safely, and to build community. But we can only do that if we're building with those communities from day one, not building for them based on our assumptions about what they need." https://flip.it/Xs9Lur#OpenSocial #OpenSocialWeb #Community #CommmunityBuilding #FediForum #Fediverse #Media #ActivityPub #ATProto #Protocols #Technology #Tech
  • julian@activitypub.spaceundefined

    FEP 11dd: Context Ownership and Inheritance

    Moved Fediverso fep activitypub
    10
    0 Votes
    10 Posts
    83 Views
    julian@activitypub.spaceundefined
    I have amended the text of the FEP to clarify a couple of things, but also changed the inheritance logic following this month's WG meeting and subsequent discussion on ActivityPub.space. Instead of recommending that replies inherit context from the object it is in reply to, implementors must find the root node (how, is out of scope; tree traversal or context resolution are two ways that come to mind) and inherit its context. This will simplify context resolution and pave the way for other actions like moving, crossposting, forking, locking, etc. I also added in a blurb about situations in which a context would explicitly not be inherited.