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
    12 Posts
    19 Views
    @budududuroiu @andymouse it was ironic.
  • I just love TUIs!

    General Discussion tui fediverse activitypub
    1
    0 Votes
    1 Posts
    12 Views
    I just love TUIs! #tui #fediverse #activitypub
  • 0 Votes
    4 Posts
    22 Views
    @julian @box464 There's actually already an Android app that allows all this: Raccoon for Friendica (which actually also works for Mastodon).Raccoon for Friendica is a rather unique app, one I'm very fond of, because it perfectly illustrates how the best ideas come from the "contamination" of different environments. Here's an article about Raccoon that should be updated, which I wrote a few weeks after the app's beta release (launched in late August 2024)Raccoon for Friendica was developed by @akesiseli after he had already developed an Android client for Lemmy (Raccoon for Lemmy).When he focused on Friendica, he faced the problem of how to translate Friendica's ability to display group conversations into an app (they're quite visible on Friendica's web interface, though they don't have the clearest interface possible like Lemmy's or forum platforms like NodeBB and Discourse). He ported the "topic view" feature already present in Lemmy's apps to Friendica!Since Raccoon is an app that also works with Mastodon, @akesiseli attempted to "force" Mastodon to have the same interface, and after a few attempts, he succeeded perfectly.Raccoon for Friendica still has a few imperfections (search isn't 100% functional, it still doesn't handle resharing with quoting, and other minor glitches, and feed capture is still a bit slow compared to Tusky and Fedilab), but despite being just over a year old, it's a decidedly mature app. Most importantly, it offers group viewing features that no other app offers. And—trust me!—group viewing isn't the only new feature Raccoon has brought to a social media client!I hope the app's development continues well, although I'm a little concerned: the developer is a bit disappointed that almost no one uses his app... But this is mostly due to the fact that the app has a name that appeals to Friendica users (who are very few) and that even the most established apps for Mastodon suffer from competition from an "official" app!
  • 0 Votes
    3 Posts
    19 Views
    @wendythedruid I really like the PDS part of the protocol and the way identity is handled. The fact that you decide where your data is regardless of the app you choose to use is neat