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
    13 Views
    Been a while since I last checked what's going on in here, how's it going #fediverse ?
  • 0 Votes
    1 Posts
    5 Views
    I'm against banning social media for under 16's. Just outright banning doesn't make something unavailable - just unregulated and not monitored. Alcohol and vapes are still common among under 16's - especial those that are vulnerable. I am for under 16's not being allowed on corporate socials though - as they are toxic places which do provably screw with brain development in youth - because of that algorithmic nature. I am considering pitching an idea to a local established non-profit that I sometimes work with, who run a number of local youth clubs across the region. It is an idea of setting up a fediverse instance for 11-15 year olds. An account can only be made in person alongside being a member of a youth club -with parent / guardian consent. It will not be federated to the general social web, and begin as a self-contained bubble - but with the idea of other regions creating the same thing and federating together. It would be moderated by the same volunteers / employees that run the youth clubs and social services - who are fully vetted, and follow the protocols - which already also includes moderating each other. Perhaps even somehow make it so the kids can't post on it during school hours, and after, perhaps, 10pm? There would of course be a set of standards expectations, or community codes of conduct, like here in the Fedi. Perhaps also running regular fun things too, that get kids thinking creatively (like what happens at the clubs anyway). There are of course many many issues with this idea, and I can't see it actually happening just like that. Not only is there unlikely the right fedi project to accommodate needs, but things like the online safety act potentially blocking the ability to create safe community based social networks for youth. And I'm sure there are many other issues as to why this idea might not work either. Like, what happens when someone turns 16? Are they just kicked off? However, I do know that corporate socials are bad - but not providing good safe alternatives when attempting to protect children, actually makes them more vulnerable and unsafe. We need a way to embrace them, not outcast them.#socialban #socialmedia #fediverse #activitypub #youthwork #onlinesafety
  • 0 Votes
    1 Posts
    8 Views
    I've gone live!Fireside Fedi - Episode 55 - Meljoann - #multidisciplinary⁩ ⁨#hyperjack⁩ ⁨#arthole⁩#owncast #streaming #interview #fediverse #fedi #people #show #firesidefedi #FsFhttps://stream.firesidefedi.live
  • 0 Votes
    3 Posts
    20 Views
    @darth As said on the 'Tubes, a nice conversation and great to see you and Stefano emphasizing our need for open source, open minds and open conversations. See you both around, at least over here.Cc @stefano