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

Journalismus jenseits von Big Tech: unser Report ist da!

Fediverso
10 6 16

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @jonny@neuromatch.social honestly good for you for investing the time to critique this knowing it's AI (adjacent or wholesale) involvement.

    read more

  • @julian @PortaFed
    giving a further read: I can't really imagine a case where someone would a) regularly be creating signed backups and also b) know in advance where you wanted to migrate to to set the destination_did. Like if this is for the case where the instance has shut down, you might have some signed backup, but you probably haven't planned in advance where you would want to migrate, and if the instance is down you wouldn't be able to create the migration object after the fact.

    the validation strategy for the export is sort of mystifying to me. if the whole object is signed, then why would you need a merkle tree for objects and also an object count? if the contents of the object have changed post signing, then the signature validation will just fail and those are irrelevant.

    true to form for LLM generated documents, several critical things are left undefined, like what last_accepted_sequence is or how that works.

    probably the most important problem is that it's not really clear how all other instances are supposed to handle this, which is the entire hard part of a migration spec. Like, if the purpose here is to preserve identity, then you would need to have all the other instances come to see the new identity as being equivalent to the old identity, and there's no discussion of how that process works for third-party instances at all. like e.g. in FEP-1580 i had to spend a long time gaming out scenarios for how third party instances would handle a move event.

    so without that it's not really an account portabiltiy spec, it's an account export/import spec, which is fine, just not really needed since signing objects and collections (which this spec should use anyway) is already described by other specs.

    read more

  • @silverpillThank you , these are important corrections and I appreciate you taking the time.
    You're right on both points. I'll update the spec to reflect that FEP-ef61 authority is not actor-rooted in the way I described, and that migration is possible via outbox export-import. I was overstating the gap.
    The distinction I was trying to draw is narrower:

    read more

  • @PortaFed

    I have a couple of comments regarding the spec https://codeberg.org/portafed/portafed/src/branch/main/portafed-spec/spec.md

    It contains a comparison with FEP-ef61, but it is not quite correct:

    - FEP-ef61 identity is not actor-rooted. The closest equivalent of FEP-ef61 identity in normal ActivityPub is a server with a domain name. A single FEP-ef61 authority can manage multiple actor documents.
    - FEP-ef61 does not lack a migration flow. Strictly speaking, it doesn't need one, because data is not attached to a server and can be continuously synchronized between multiple servers. But a more familiar migration flow is also possible via outbox export-import.

    @lutindiscret

    read more

  • @benpate That would be great and happy to contribute wherever it fits.
    My guess on the scope decision is the same as yours: hostile-server recovery is genuinely harder, and a cooperative spec is already a lot to get right. Makes sense to tackle it separately.
    Take your time reading. I'll put together a short write-up of how MigrationProof could slot into the existing spec easier to react to something concrete than to an abstract pitch.

    read more

  • @jonny@neuromatch.social tracks doesn't it 😝

    read more

  • @julian
    @evan @benpate @PortaFed
    Can't make heads or tails of this one

    read more

  • Warm up the fire! We're LIVE!

    Summer in Winter: Norcal Gma 2's Journey with her Dog - E79

    #owncast #streaming #interview #fediverse #fedi #people #show #firesidefedi #FsF

    https://stream.firesidefedi.live

    read more
Post suggeriti
  • 0 Votes
    9 Posts
    50 Views
    Hmmmm, I suppose, but Facebook never had a Dislike, they added emoji reactions, technically, no?
  • 0 Votes
    1 Posts
    14 Views
    Bonfire isn’t easy to pin down, and that’s the point! We seek to enable a tapestry of social spaces, all built from shared building blocks but diverging in flavour, practice, and purpose.We gathered a whole collection of answers from across the fediverse:👉 https://bonfirenetworks.org/posts/what-is-bonfire-plural-by-design/Want to help shape what comes next? Support and share the crowdfunding to join install parties, co-design sessions, and more: 👉 https://www.indiegogo.com/projects/bonfire/community?refcode=r7GaxBU-z0yejFPdalMOKQ#Fediverse #Plurality #OpenSocialWeb #Community
  • 0 Votes
    1 Posts
    16 Views
    Summer/Autumn 2025: Little coding, but lots of socializing and planningAt the first October weekend I (@linos) was attending the Berlin FediDay 2025. It was a meetup of the Berlin and German community, developers of Fediverse applications, and representatives of German speaking media institutions. It was great to see old friends again and meet some online contacts for the first time. We were discussing the future and the role of the Fediverse, which was super motivating. #FediDayTwo weeks later, I travelled to Sofia, Bulgaria, to attend this year’s OpenFest, give a talk and lead a workshop on how the Fediverse can help announce and discover events. Unfortunately, the talk didn’t attract much attention, as LLMs are currently drawing more of an audience. But the discussions with those in attendance were very interesting. The workshop was mainly about trying out #Gancio, #WordPress and #Mastodon and learning about the possibilities for local communities by trying out the applications themselves. I simply provided real test instances, created a list of tasks, including minor pitfalls, and, of course, answered all the questions that came up – and there were quite a few! And a big thank you to the crew and the organizing team, who were so friendly and simply wonderful throughout. #OpenFestYesterday, I had an awesome online meeting with the incredibly cool folks behind LAUTI, a free and open-source software for hosting small event calendars. #LAUTI is aimed at small and medium-sized communities and has a big focus on social, cultural and activist stuff. The instance for the Stuttgart area, run by the collective that develops it (@klasse_methode@chaos.social), can be found at https://einftopf.info. The developers are in the process of exploring the potential of #ActivityPub and the #Fediverse. I’m very excited and think this could be really great! In case you’ve been wondering: I see LAUTI kind of in between #Mobilizon and #Gancio. In my opinion, it would not be a competitor to them, but it could be a great addition to the Fediverse by filling this gap.I will be at the #SFSCON in Bolzano, Italy, in two weeks. There will be a whole afternoon focusing on the Fediverse! So in case you’re there you’re invited to join my short talk about Interoperability of Events in the Fediverse: status quo and vision. Or you’re welcome any time to say hello and let’s have a chat.After that, it’s time to sit down and get back to programming. But it’s very important to me to continually evaluate and understand what the priorities are, and to remind myself why it’s so important that we all continue our work in this area.#ActivityPub #FediDay #Fediverse #Gancio #Lauti #Mastodon #Mobilizon #OpenFest #SFSCON #WordPress
  • 0 Votes
    1 Posts
    11 Views
    I think it's time to write an #introduction for this account as well!I'm Stefano Marinelli, Barista of the illumos Cafe and the BSD Cafe. I'm a technology and open source enthusiast, a strong advocate for #OwnYourData, and against computer monoculture, even when it comes to open source solutions. I've been active in the #Fediverse for years and am a firm believer in it. I decided to found this Cafe to bring the positive spirit of the BSD Cafe to curious and passionate users of #illumos based operating systems (#OmniOS, #SmartOS, #Tribblix, #OpenIndiana, etc.).I'll mainly use this account for content related to this instance and illumos-based operating systems, while my account at the BSD Cafe - @stefano@bsd.cafe - remains my primary one.For more information about the illumos Cafe, you can read the introductory post here: https://it-notes.dragas.net/2025/08/18/introducing-the-illumos-cafe/#illumosCafe #BSDCafe