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

Good morning from DUMBO in Bologna 👋 🇮🇹

Fediverso
13 7 23

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
  • #fediverso

    Fediverso fediverso
    4
    0 Votes
    4 Posts
    22 Views
    @luca un social europeo su server aws.
  • Voci di donne su Mastodon

    Fediverso mastodonuno fediverso mastodon
    36
    0 Votes
    36 Posts
    105 Views
    Benvenute! Non vediamo l'ora di leggervi con piacere!@filippodb @emama @lauramassera @fediverso
  • 0 Votes
    2 Posts
    21 Views
    Sono proprio felice di iniziare a vedere altri #admin del #Fediverso riuniti nello stesso angolino.È normale che siamo tutti un po’ sulla difensiva (me compreso), la stanza è nata da un solo giorno… ma siamo già in 20!La verità è che stare ognuno nel proprio fortino e non collaborare è controproducente; se non troviamo un vero punto d’incontro, rischiamo solo di farci schiacciare dai soliti social commerciali che già bussano alla porta con il loro “ciao, vi inglobiamo tutti?”.Chissà, magari tra un po’ ci rilassiamo, abbassiamo gli scudi e iniziamo davvero a fare squadra, aiutarci e costruire qualcosa di bello insieme… senza campanilismi e senza “il mio server è più bello del tuo”.🙏
  • 0 Votes
    1 Posts
    13 Views
    ⚔️ Cronache del Fediverso – “Il Ban Facile” ⚔️Ogni tanto i cavalieri del keyboard-valor bussano alle porte dei miei piccoli server,convinti di trovarci il buffet aperto. 🤺🍽️Peccato per loro che qui ha vinto la noia: c’è uno che ha tempo libero, ci smanetta, conosce i trucchi e ha il ban facile.Risultato? Invece del trofeo del giorno, ricevono il premio più temuto: una settimana di esilio digitale. 🧨🔎 Per i curiosi (e i distratti)Ecco perché questi attaccanti sembrano più ridicoli che pericolosi:🏷 Si fingono americani (IP sembra registrato in Kentucky)…ma la traccia reale spesso punta a Hong Kong (geolocazioni contrastanti).🆕 IP appena creati — subnet assegnate la scorsa settimana: perfetti per affittare VPS “usa e getta”.🔍 Nessun PTR / reverse DNS configurato: server appena messo online o volutamente “anonimo”.🧭 ASN sospetti (Optibounce / Silverstream / reti “bulletproof”): provider che riciclano blocchi e li spostano in giro per il mondo.✉️ Comportamento tipico: tentativi SMTP/relay e scansioni veloci — presi al volo da fail2ban.⛔ Risultato: ban immediato (7 giorni), recidive trattate con mano ferma (periodi molto più lunghi).💬 Morale della storiaSe volete davvero fare gli “eroi” del net:fatevi un tè, leggete un po’ e lasciate perdere i miei server. Qui non si trovano porticine aperte a caso — si trova solo ordine, logs e un amministratore con tempo libero e riflessi pronti. 😎Alla prossima puntata di🎬 “Phisher & Furious – Truffatori all’ultima mail”.#Fediverso #Fail2ban #SnowfanDefense #CyberChronicles