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
    9 Views
    This is our biggest release yet, including more finished tasks than any of our previous ones. Below is a summary of the highlights: What's new Posts & communities can be labelled as AI-generated and people can choose to hide all posts tagged that way. Very similar to how NSFW works. Comments can be marked as an Answer, like on StackOverflow. React to posts and comments with an emoji. Hide an individual post from yourself, without blocking the author. PieFed is now in the Yunohost app store, making initial setup easier. When banned from a remote instance you cannot make local-only posts in their communities. Honeypot to automatically IP ban badly-behaved crawlers. https://lemmy-federate.com integration, making PieFed communities get more exposure. "Share on Mastodon" menu item on posts. Vastly improve docs for new developers, see https://codeberg.org/rimu/pyfedi/src/branch/main/docs/developer_docs. Language selection is more visible during post creation. Tag clouds can also be viewed as a list of tags. View post/comment markdown. Bot accounts are not included in community statistics. Footnote support in markdown. Polish translation. Better HTTP caching, which reduces dependence on Cloudflare. Bugs Passkey fixes. Polls can now have up to 15 options. User profile performance improved. Don't allow bypassing minimum username length and post title with whitespace. Polls and Events can no longer be posted into Lemmy communities. API Additional user settings can be set through the api, including Extra Fields. Fetch url metadata. Sort comments by controversial. Comment search now works. Hashtags. Events. Polls. Emoji reactions on posts and comments. See https://piefed.social/c/piefed_api for more details. To upgrade To upgrade from 1.3.x: git pull git checkout v1.4.x ./deploy.sh or ./deploy-docker.sh There is a big database migration that will take a few minutes to run. How long will vary depending on how old your instance is - older instances will have more content to process. It took ~25 minutes on piefed.social so expect it to be less than that. Donations PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features. Donations can be made via Patreon, Liberapay or Ko-fi.
  • 0 Votes
    1 Posts
    5 Views
    Selbst mein kleines, privates @blog hat inzwischen 400 Follower: https://kaffeeringe.de/ Da soll noch jemand sagen, hier sei nix los!#ActivityPub #WordPress #Fediverse#Mastodon
  • 0 Votes
    7 Posts
    25 Views
    @luca @beach I'm afraid I'm not aware of any client that does it presently, sorry.
  • 0 Votes
    2 Posts
    22 Views
    @michaelrowe01 there’s more where that came from