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
    3 Posts
    23 Views
    @activitypub.blog Nice! Very cool outlook!I would love to see some action not just on the technical side of ActivityPub in WordPress but also on the promotion side. It woud be great to convince some of the more interesting blog from wordpress.com to activate ActivityPub.
  • 0 Votes
    1 Posts
    5 Views
    Release v3.2.3 of Ktistec includes two big features:FEP-1b12 Group federationImproved federation with Lemmy and other forum-type servers. Ktistec supports community and thread follow/unfollow, as well as up-vote/like (down-vote/dislike is supported but there is no visual affordance for that yet).FEP-9098 Custom emojisSupport for viewing custom emoji in posts and on actor profiles. Ktistec does not yet support custom emoji creation and management.The full changelog:AddedSupport for viewing custom emoji in posts and on actor profiles.Actor type (Person, Group, etc.) overlay badges on actor panels.Colored fallback avatars for actors without icons.Support for robots.txt.FixedFederation with Lemmy and other servers that support FEP-1b12.Shared inbox support for local actors.Serialization of Undo includes the undone activity.Serialization of Like and Dislike does not.Notify only once for an object's first received activity.ChangedAccumulate metrics by hour for finer granularity.Clean up presentation of public followers/following pages.The next release will include support for Mastodon polls (FEP-9967).#ktistec #crystallang #activitypub #fediverse
  • PieFed 1.3 is released

    PieFed Meta fediverse piefed
    1
    0 Votes
    1 Posts
    9 Views
    What's new Media library that lets you upload images to comments/post body and paste from the clipboard Animated gif support for user profile pictures Specify alt-text for link posts that link to an image Emoji picker and spoiler button added to markdown toolbar More links to the modlog (footer, community sidebar, user profile) and improved searching/filtering Leave a conversation to remove it from the list of their direct message conversations Post urls are now "friendly" since they include the community name and a snippet of the title instead of just a number Add link to show parent comment when directly viewing a comment reply Image markdown style formatting to allow more advanced control of how images are rendered. e.g. ![image alt text :: width=300px](https://url to image) Code syntax highlighting in code blocks and allow for style selection in user settings Tag cloud added to sidebar for feeds and topics Better searching and filtering of the Instances list Add a block (of a user, community, instance or domain) from the blocks and filters management area, without doing it via a post Popup suggestions when mentioning a community or user as you type Onboarding plugin which auto-subscribes, auto-blocks and sends a welcome message for new accounts Improved federation efficiency Old posts can be automatically archived (saved to S3) to free up database space Old posts by bots with no comments are automatically deleted LLDAP support, which does LDAP a bit differently To upgrade To upgrade from 1.2.x: git pull git checkout v1.3.x ./deploy.sh or ./deploy-docker.sh In the past we had a separate project for realtime notifications, which is now unsupported as it's code has been merged with the main PieFed project. To set it up, refer to the Push Notifications section of install.md. As well as enhancing the user experience doing this will decrease load on your server if it hosts local communities with many subscribers as some of the federation work has been offloaded to the push notifications service. 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
    2 Posts
    9 Views
    @AnneTheWriter1 Don't support the pumpkin spice poachers!!!