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

Is it correct to say the #Fediverse and #BlueSky are "federated" by protocol bridges?

General Discussion
3 2 9

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    6 Views
    Week in Fediverse 2026-01-30Servers- Betula v1.6.0- stegodon v1.6.2- flohmarkt v0.14.3- Friendica v2026.01- PeerTube v8.0.2- Manyfold v0.132.0- Hubzilla v11.0- Ktistec v3.2.8- Castopod v1.14.0- NodeBB v4.8.1- shops v0.2.1- PieFed v1.5.4- Loops v1.0.0-beta.9Clients- Pachli v3.3.1- tooi v0.20.0- PeerTube-GTK: Native desktop PeerTube clientTools and Plugins- Poduptime v6.2.0- FediBoost: Automatically boost WordPress posts on connected Mastodon accountsFor developers- APx v0.21.0Articles- A Crowdsourced Photo Gallery from the Fediverse – the Open Social Web in action- Community, Fedi-style-----#WeekInFediverse #Fediverse #ActivityPubPrevious edition: https://mitra.social/objects/019bebbb-adee-b1ae-ab85-c1825103684b
  • 0 Votes
    6 Posts
    21 Views
    @eyeinthesky @evan @trwnh the charter has the correct scope. I believe Evan was responding to discussion about the Fediverse and trying to point out the venn diagram overlap of Fediverse and WG charter. As such, indieweb stuff didn't factor in to that conversation. Or at least that was my read -- I raised an eyebrow when I read the email too!
  • 0 Votes
    8 Posts
    18 Views
    @krafting you can explore without an account, we just simply limit it. Mastodon does this too.
  • FEP 11dd: Context Ownership and Inheritance

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