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

apparently someone is hostign a activitypub instance on a ps4...https://fedilist.com/instance/fedi.on-a-ps4.lol#activitypub #ps4

Uncategorized
3 3 26

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    8 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
  • 1 Votes
    3 Posts
    16 Views
    Yep, that's basically it. It's not really a concept in threadiverse implementations since group actors do the Announcing for synchronization.
  • 0 Votes
    15 Posts
    50 Views
    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.
  • 0 Votes
    3 Posts
    21 Views
    @Gargron interesting!