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. Technical Discussion
  4. RE: https://colours.bots.edent.tel/posts/68d87379-8e35-18be-b901-2730376a090d.jsonOk, I need some #ActivityPub help, please

RE: https://colours.bots.edent.tel/posts/68d87379-8e35-18be-b901-2730376a090d.jsonOk, I need some #ActivityPub help, please

Technical Discussion
6 3 35
Log in to reply

Feed RSS
RE: https://colours.bots.edent.tel/posts/68d87379-8e35-18be-b901-2730376a090d.jsonOk, I need some #ActivityPub help, please

Gli ultimi otto messaggi ricevuti dalla Federazione
  • julian@activitypub.spaceundefined
    julian@activitypub.space

    @sk@utsukta.org mentioned in another thread that the way Hubzilla and threadiverse software handle group discussions is incompatible.

    It got me thinking about whether that is true. At its core both FEPs (171b and 1b12, respectively) rely on a central "distributor" node to send activities to recipients.

    @silverpill@mitra.social did further comparisons in thr text of 171b itself:

    > Announce activity is used instead of Add. Conversation and related activities are synchronized between participants, but conversation backfilling mechanism is not specified.

    The questions here are:

    If threadiverse software federated out an Add in addition to Announce, would that satisfy basic synchronization (not backfill) requirements laid out by 171b? Is there any reason why Announce could not be used to facilitate private federated group discussions as well? Assuming visibility maintains scoped to addresses, I don't see any immediate reason why not...
    read more
  • box464@mastodon.socialundefined
    box464@mastodon.social

    I'm playing around with Offer activities in Fedify. The AP Vocab provides this, easy peasy.

    ✅ Alice OFFERS Book to Bob
    ✅ Bob ACCEPTS Alice's OFFER

    Or:

    ✅ Bob OFFERS Rotten Tomato to Alice
    ❌ Alice REJECTS Bob's OFFER

    ----------------

    But I'm not clear if this is right:

    ❓Alice ANNOUNCES OFFER of Labubu to Followers?

    ❓Bob OFFERS $10 for Labubu to Alice?

    ❓ Alice ACCEPTS Bob's OFFER of $10 for Labubu?

    ✅ Alice OFFERS Labubu to Bob

    ✅ Bob ACCEPTS Labubu

    read more
  • reiver@mastodon.socialundefined
    reiver@mastodon.social

    Your Home Feed is the inbox of an ActivityPub actor — in particular YOUR ActivityPub actor.

    There could be an actor for each hash-tag, too.

    You could even do Del.icio.us like things — and have actors for intersections of hash-tags, too.

    These hash-tag actors' inboxes would need to be readable by anyone.

    ...

    This could be a more ActivityPub like API alternative to Mastodon's "GET /API/v1/tags/{name}" API.

    read more
  • mcc@mastodon.socialundefined
    mcc@mastodon.social

    @hongminhee How hard would it be for a future version of ActivityPub to simply back out JSON-LD support? Would there be a downside to this?

    read more
  • silverpill@mitra.socialundefined
    silverpill@mitra.social

    @julian Yes, POST to personal inbox sends a 404, POST to group inbox sends a 202 (I guess group inbox is how we communicate now).

    read more
  • julian@activitypub.spaceundefined
    julian@activitypub.space

    @silverpill@mitra.social POSTing that inbox sends a 404?

    read more
  • silverpill@mitra.socialundefined
    silverpill@mitra.social

    @julian @liaizon https://activitypub.space/uid/1/inbox still returns 404. Perhaps group's inbox is working?

    UPD: yes https://activitypub.space/category/5/inbox returns 202

    read more
  • stefan@stefanbohacek.onlineundefined
    stefan@stefanbohacek.online

    @nicholas Agreed with all of this!

    @evan @travisfw

    read more
@pierobosio@soc.bosio.info
Post suggeriti
  • dansup@mastodon.socialundefined

    Loops also uses snowflake ids for ActivityPub actor identifiers!

    General Discussion loops activitypub loopsdev
    1
    0 Votes
    1 Posts
    10 Views
    dansup@mastodon.socialundefined
    Loops also uses snowflake ids for ActivityPub actor identifiers!I noticed that Mastodon has adopted this too, great to see. I will be bringing this to Pixelfed later this year as well 😁https://browser.pub/https://loops.video/ap/users/1#Loops #ActivityPub #LoopsDev
  • informapirata@www.informapirata.itundefined

    Post di prova da Raccoon

    Uncategorized activitypub raccoon wordpress
    6
    1
    0 Votes
    6 Posts
    12 Views
    lgsp@social.tchncs.deundefined
    @informapirata sembra funzionare bene, tutti i tag e le formattazioni si vedono a posto, da qui
  • box464@mastodon.socialundefined

    Bonfire pushed a big release last week, and I'm excited to try out all the new shiny things on my test instance.'nPost migration and Quote Posts among them.'n#Bonfire #ActivityPub

    General Discussion bonfire activitypub
    7
    0 Votes
    7 Posts
    29 Views
    cheeaun@mastodon.socialundefined
    @box464 if approved on Bonfire's side, Mastodon should recognize it… probably takes time? 🙈There's no approve/deny UI/flow/API on Mastodon's side. I've asked & got this response "we included support for it in case someday another software wants it" and "(but we think it's not a good idea, as it means your quote can be displayed as pending for a long time, which is not ideal in a timeline-based network)" — which I think make sense. By the time it's approved, it's probably too old to be read
  • julian@community.nodebb.orgundefined

    Minutes from 4 September 2025 WG Meeting

    Forums and Threaded Discussions Task Force forumwg swicg activitypub
    1
    0 Votes
    1 Posts
    15 Views
    julian@community.nodebb.orgundefined
    Apologies in advance if I misrepresented anybody or missed any crucial bits of information. Jesse Karmani (jesseplusplus@mastodon.social), Ted Thibodeau Jr. (tallted@mastodon.social, and Julian Lam (julian@activitypub.space) in attendance Julian provided an update on adoption of FEP 7888 Both Piefed and Lemmy have adopted 7888, and will begin publishing resolvable context collections in their next release Jesse opened a PR to Mastodon, which received preliminary approval from Gargron@mastodon.social (ed. it was later merged, rolled back, updated, a new PR opened, which was then merged) This PR is the first of two planned pull requests. The first generates the outgoing context (the same as what Lemmy/Piefed have done recently) The seconds handles incoming contexts and backfills Jesse was asked whether it would conflict with existing reply-tree crawling methods, but the two are complementary. She expects additional discussion before the PR is opened. Julian noted that it would be helpful if statistics/analytics were gathered by the Mastodon team to see how conversation contexts and backfill works at scale; admits that existing implementations and testing has been small scale and may not reflect real-world usage. Julian noted that Lemmy's implementation (nutomic@lemmy.ml) does not paginate their resolvable context implementation. All objects are listed in one OrderedCollection Jesse noted that she followed Mastodon's pagination convention for collections. Context inheritance Julian asked for opinions on whether contexts were inherited in existing implementations. Notes that NodeBB inherits parent context, but checks further up the known parent chain for further contexts Julian admits that not everybody can and should do this, is also not sure anymore whether NodeBB actually does this. Julian notes the ideal implementation would be every object referencing their immediate parent, which would lead to the entire collection referring to the same context collection. Jesse: Decodon inherits immediate parent context only Ted: notes that this is a reinvention of inReplyTo Julian and Jesse note that there are marked differences between crawling the reply chain. A short discussion about how netnews and usenet handled reply chains was had. Julian notes that Lemmy will not inherit context. Every object will point back to its own server's context collection. This was a conscious decision by Nutomic as each instance is meant to consider its own representation of remote content as the canonical representation ActivityPub.Space Julian made a short shout-out to a new site called ActivityPub.Space, meant to be a hub for AP development discussions ("A federated space for ActivityPub discussions so that they don’t just get lost in ephemeral replies") A short double-back to NNTP and how they approach "eventual consistency" Ted: “Cloud of NNTP servers are all hosts of articles and replies.” Strictly speaking it’s not a reply tree as replies can be inReplyTo multiple parents