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

Due miliardi di indirizzi email sono stati esposti!

Uncategorized
2 2 0

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • Massacro nelle favelas.

    Uncategorized
    1
    0 Votes
    1 Posts
    0 Views
    Massacro nelle favelas. Rio de Janeiro@anarchia Non ci sono parole sufficienti per descrivere l’orrore che proviamo per il massacro di oltre 130 giovani afrodiscendenti poveri uccisi dalla polizia di Rio de Janeiro, con la scusa di combattere il narcotraffico. Si è trattato di un’operazione di guerra...Vedi https://www.rivoluzioneanarchica.it/massacro-nelle-favelas-rio-de-janeiro/
  • 0 Votes
    1 Posts
    0 Views
    My toot machine :I first type with a typewriter, then scan and OCR it to post.
  • 0 Votes
    3 Posts
    0 Views
    @_elena @jaz … which is a change from 🐈
  • 0 Votes
    15 Posts
    3 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.