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

BONJOUR LE #fediverse β€οΈπŸ§‘πŸ’›πŸ’šπŸ’™πŸ’œβ€οΈπŸ§‘πŸ’›πŸ’šπŸ’™πŸ’œ

Fediverso
24 9 42

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
    6 Views
    Good morning πŸ˜ƒβ˜€οΈ β˜•οΈβ„οΈ friends and Fediverse. Hope everyone has a great day today ahead.My Thinkpad is being delivered tomorrow afternoon.#Coffee #Thursday #Thinkpad #Fediverse
  • 0 Votes
    5 Posts
    15 Views
    @blu256 @louise πŸ‘†
  • 0 Votes
    2 Posts
    4 Views
    A blog requires a platform designed for blogging. Staying within the realm of federated software, the three natural alternatives are: WordPress, which, thanks to the plugin that makes it compatible with Activitypub, has achieved a level of perfect integration with the Fediverse. Ghost, which, federated a few months ago, is not only a blogging platform but is also specifically designed for creating mailing lists based on the Substack model. Writefreely, which, despite being natively federated, is extremely focused on distraction-free writing and therefore has some seriously limiting features. Friendica As for Friendica, I'm a huge fan of that software and manage the second-most active instance in the entire Fediverse. I can assure you that I know it well and appreciate all its most important features. But don't be fooled by the fact that some call it macro-blogging software. In fact, if you visit a Friendica account's profile, it's not possible to filter the Timeline of their posts from the Timeline of the posts they've reshared. So, you could virtually create a page like this: https://poliverso.org/profile/saio But you could only do that if you don't share too much other content, otherwise the result would be like this: https://poliverso.org/profile/notizie which would be much more confusing πŸ˜… However, Friendica is a very powerful software that allows you to republish your blog feed, as well as automatically reshare your federated blogs. Here I've listed some very interesting Friendica features for blogging: https://poliverso.org/display/0477a01e-1366-ebfd-2002-91a370393480 So, to recap, if you want to use Friendica to create your blog, you can: you can create a new account. Remember to define it as a "page account," if possible, but also remember that when you reshare content you like, it will appear on your profile page. However, if you don't need the full suite of tools that characterize a social media platform, you're better off using WordPress. Sharkey We're talking about software with a very nice interface, but it's still a social networking software. Being essentially a fork of Misskey, it also has a section for creating static pages that can be easily viewed from outside the Fediverse, but these pages can't be federated with Activitypub 😭. Ultimately, it seems even less suitable for creating a blog. If you absolutely must use a Fediverse social media platform, then you'd be better off going with Friendica! Hubzilla PS: There's also a software called Hubzilla, which is compatible with Activitypub, although it has developed its own communication protocol. I'm only mentioning it because it's a feature-rich and well-designed product, but its interface is quite complex and unfriendly, so although I've chosen to mention it, I can't recommend it as an alternative.
  • 0 Votes
    1 Posts
    12 Views
    Experimental support for multiple users landed with Ktistec release v2.4.15. "Experimental" means that it works for me, but hasn't seen enough testing for me to call it "ready for production". With that said, it's unlikely you'll lose your data.There are lots of intentional design decisions that fit my vision for Ktistec but may surprise you. Here they are:Every user is an administrator. That doesn't mean users have access to each other's posts and data, but it does mean all users have access to the shared parts of the siteβ€”they can change the site description, for exampleβ€”and they can add new users. So only add people you trust.If you want to add another user, create an account for them and give them their username and password.Β  There is no self-registration. There are no invitations.Beyond adding a user, there is no support for user management. You can't even boot a user from your site. Users can delete themselves, however.There is no support for content moderation. Only add people you trust.TL;DR Multi-user support in Ktistec is suitable for small teams, families (biological or chosen), and your personal avatars. There are better tools for online communities.Here's the full set of changes:AddedAdd support for multiple user accounts.FixedHide attachments behind the summary. (fixes #125)Mark actors as up after refreshing their profile.#ktistec #fediverse #activitypub #crystallang