@informapirata
Molto interessante! Appena avrò un po' di tempo cercherò di provarlo.
@fabio @fediverso

Madblog è entrato ufficialmente a far parte della famiglia del #Fediverso!

#Madblog è una piattaforma di blogging semplice da gestire tramite file Markdown.
Nessuna interfaccia complessa. Nessun JavaScript. Nessun dB o script di migrazione. Nessun plugin non sicuro. Solo una cartella git, un vault Obsidian o una directory SyncThing sincronizzata, e la possibilità di creare e modificare contenuti semplicemente scrivendo file di testo!

Il post di @fabio

https://manganiello.eu/notice/B47BLSKrlsdeXrPGWO

@fediverso

Sto provando #fedistar per il desktop. Qualcuno conosce questo client per Mastodon? Avete esperienze da condividere?

#fediverso

@PortaFed
@julian
Why wouldnt the whole export object be signed? If an object is missing, the merkle root wouldnt match and you wouldnt be able to do partial validation anyway. I could have missed something on the strategy there

@jonny @julian You're right on all three points. Updated the spec: destination_did is now optional the backup-before-shutdown case is the primary use case and requiring a destination in advance was a mistake.
Added Section 5.1 explaining why the Merkle tree exists alongside per-object signatures: the signatures prove per-object authenticity but not completeness. A Merkle root over the full set detects silently dropped objects.
Added Section 8 explicitly scoping this as an export/import substrate

@jonny@neuromatch.social honestly good for you for investing the time to critique this knowing it's AI (adjacent or wholesale) involvement.

@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.

@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: