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

#ActivityPub 日本語ハッシュタグのデコード問題、早く解決してくれないかな…。解決するまではいしい‘@長文の投稿を控えるつもりだけど、軽く投稿したい長文があるんだよな…。

General Discussion
1 1 10

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    6 Views
    RE: https://climatejustice.social/@stefanmuelller/115673891992319316Kann mir jemand erklären, wieso dieser Blog-Post nicht angezeigt wird? Das ist #Wordpress mit #activitypub aber irgendwie geht das nicht. Beim #OstBlog geht alles. Ich finde aber keine Einstellung, die ich ändern könnte.Es heißt einefach immer "Beitragsveröffentlichung ausstehend".#FollowerPower
  • 0 Votes
    1 Posts
    18 Views
    Emerged from another Yak Shaving exercise to implement Add, Remove and Move activities processing in #GoActivityPub 🧑‍🍳 #ActivityPub
  • 0 Votes
    1 Posts
    17 Views
    Mastodon has a concept called "pinned statuses", which is a special collection attached to a Person actor. https://docs.joinmastodon.org/spec/activitypub/#featured It wasn't readily known how this collection is updated and federated (not without code achaeology), but claire@social.sitedethib.com recently shared some additional info :smiley: The actor itself will issue an Add activity targeting the collection with the status in object. This activity is sent to all followers of the actor. No activity is sent if the actor has no remote followers. A Remove is sent when a pinned post is unpinned. This is what the Add looks like: { "@context": "https://www.w3.org/ns/activitystreams", "type": "Add", "actor": "https://example.org/users/testUser", "target": "https://example.org/users/testUser/collections/featured", "object": "https://example.org/users/testUser/statuses/115266412340579560" } The corresponding Remove is identical except for type, which is of course, Remove.
  • FEP 11dd: Context Ownership and Inheritance

    Moved Fediverso fep activitypub
    10
    0 Votes
    10 Posts
    82 Views
    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.