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

Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.

Fediverso
51 21 266

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
    1 Posts
    14 Views
    Es wäre etwas anderes, wenn ich keine Beweise hätte. Wenn ich nur eine zufällige Person wäre, die wilde Behauptungen ohne jegliche Dokumentation aufstellt, wäre das natürlich Unsinn.Aber ich habe Beweise. Ich habe das aus erster Hand gesehen und sogar das Risiko auf mich genommen, Dinge von der Arbeit zu teilen, um es zu untermauern.Dieser Ort soll doch besser sein als Blue Sky, Twitter, Facebook und Reddit – richtig?Wenn dem so ist, warum werden dann Betrüger geschützt und behandelt, als gehörten sie zu einer besonders geschützten Personengruppe?#Betrug #Täuschung #Fediverse #ActivityPub #Twitter #Reddit #Facebook #BlueSky
  • 0 Votes
    6 Posts
    40 Views
    @liaizon @Mastodon @altstore@fosstodon.org @altstore@alt.store Super cool!
  • 0 Votes
    1 Posts
    15 Views
    Since the influx of Blue Sky and Twitter users, Mastodon Dot Social had unfortunately — but temporarily — experienced a few Nazi accounts, all of which have since been removed. However, a few individuals are now wrongfully claiming that the Fediverse is no different, simply because a few bad individuals managed to make it here. What they’re choosing to ignore is the key difference: those accounts were dealt with and rightfully removed. The fact that they weren’t caught immediately does not support the implications being made. 🙄Haters are going to hate. 🤷#Fediverse #ActivityPub #Mastodon #BlueSky #Twitter #Nazis
  • 0 Votes
    1 Posts
    18 Views
    Mastodon has a concept called "pinned statuses", which is a special collection attached to a Person actor. https://docs.joinmastodon.org/spec/activitypub/#featured It wasn't readily known how this collection is updated and federated (not without code achaeology), but claire@social.sitedethib.com recently shared some additional info :smiley: The actor itself will issue an Add activity targeting the collection with the status in object. This activity is sent to all followers of the actor. No activity is sent if the actor has no remote followers. A Remove is sent when a pinned post is unpinned. This is what the Add looks like: { "@context": "https://www.w3.org/ns/activitystreams", "type": "Add", "actor": "https://example.org/users/testUser", "target": "https://example.org/users/testUser/collections/featured", "object": "https://example.org/users/testUser/statuses/115266412340579560" } The corresponding Remove is identical except for type, which is of course, Remove.