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

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

General Discussion
22 5 38

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    10 Views
    Week in Fediverse 2025-11-28Servers- tootik v0.20.0- Ktistec v3.2.1- NodeBB v4.7.0- Wafrn v2025.11.01- Loops v1.0.0-beta.5- Mitra v4.14.0- Misskey v2025.11.1- Omnom v0.8.0- PieFed v1.3.5- stegodon: An SSH-first federated blogging platform- linkblocks: A federated network to bookmark, share and discuss good web pages with your friendsClients- Chihu v1.14.0- Phanpy changelogTools and Plugins- feed2fedi v3.4.0- FIRES Server v0.7.0- OwncastLive Panel: A GNOME Shell extension that monitors your favorite Owncast instances and notifies you when they go liveArticles- Git as Federation Transport — Rethinking How Small Social Networks Talk to Each Other- Now witness the power of this fully operational Fediverse!- Fediverse onboarding resources- Owncast Newsletter November 2025- Fediverse Report – #144-----#WeekInFediverse #Fediverse #ActivityPubPrevious edition: https://mitra.social/objects/019aa829-83b6-d369-eedb-8725125ced7b
  • 0 Votes
    1 Posts
    13 Views
    This year, at the famous FOSDEM gathering in Brussels (Belgium), we were invited by the SocialWeb devroom to give a presentation on ActivityPods. It was an opportunity to highlight the “universal social network” that would be possible with ActivityPods, and how it differs from the Bluesky project. For more informations: https://activitypods.org/activitypods-at-fosdem-2025
  • 0 Votes
    7 Posts
    52 Views
    silverpill@mitra.social oh don't tell me we're going to have competing E2EE implementations too!
  • FEP 11dd: Context Ownership and Inheritance

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