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. I've been working on #ActivityPub support in the Agora, looking forward to testing!

I've been working on #ActivityPub support in the Agora, looking forward to testing!

General Discussion
10 3 21
Log in to reply

Feed RSS
I've been working on #ActivityPub support in the Agora, looking forward to testing!

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • lqdev@lqdev.meundefined

    Test sig verification after hotfixes

    Moved Uncategorized fediverse activitypub mastodon
    1
    0 Votes
    1 Posts
    9 Views
    lqdev@lqdev.meundefined
    Post 500 error fixes
  • contrapunctus@fe.disroot.orgundefined

    Does choice of server affect the reach of your posts?

    General Discussion activitypub fedihelp
    6
    0 Votes
    6 Posts
    15 Views
    rimu@piefed.socialundefined
    Yes. If no one on, say, mastodon.social is following you then none of your posts will show up in the global timeline there or in searches or in hashtags. Also if you have few followers your posts will receive few boosts so hardly anyone will follow you. So we end up with a handful of wildly popular accounts dominating the conversations which mostly happen on the big instances. Centralised power. Bad. The threadiverse solves this. People don't follow other people, they join communities and it's their membership that determines where the federation traffic goes. So nearly every instance has all the conversation and everyone is on an equal footing.
  • 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.
  • wjmaggos@liberal.cityundefined

    Thanks for speaking up Rudy (even though he did throw a dig at #ActivityPub in the thread).

    General Discussion activitypub xitter atproto bluesky
    5
    0 Votes
    5 Posts
    23 Views
    mastodonmigration@mastodon.onlineundefined
    @wjmaggos Yeah, but feel bad for the guy. What's happening is that there is an adversarial relationship developing and Bluesky holds all the cards. This is not going to end well for Blacksky.This has always been the problem with corporate sponsored standards. If the technology host company is not fully and completely committed to open competition with their standard clients it can never work.