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
  • 0 Votes
    1 Posts
    3 Views
    The oldest backrooms level is a very long house. The longhouse was the first very large building designed by humans. Some of them were massive. So I propose a backrooms level that's just a long house that extends into infinity, maybe with partition doors at intervals. Dead fire-pits, dry sleeping spots. Discarded carvings and broken cooking pots. And always light flickering through the walls, the sound of running animals and chaos. #backrooms

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • #Bonfire Social 1.0 sta arrivando.

    Fediverso bonfire fediverso
    10
    0 Votes
    10 Posts
    11 Views
    @informapirata @bonfire @fediverso è quello il guaio: oggi se non hai una comunicazione efficace, puoi avere l'idea di inventare il mondo, ma non ne sei in grado. Io voglio capirlo perché casomai accenno a bonfire nel talk al #WCPISA
  • 0 Votes
    4 Posts
    2 Views
    @elettrona @nationsblind @BPI @mastoblind I guess a mirror cube (it's how it is called, usually it came with gold or silver sticker) can be a cheap substitute.Sighted people buy it because unscrambled, on a table, it looks great
  • 0 Votes
    4 Posts
    10 Views
    Hey @kyva I have issues debugging why it is not possible to follow some WordPress blogs. Can you maybe have a look at the logs what might went wrong when trying to follow @activitypub.blog on firefish?thanks for connecting @DavidMarzalC 🫶
  • FEP 11dd: Context Ownership and Inheritance

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