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

End-to-end Encryption (E2EE) over ActivityPub


Gli ultimi otto messaggi ricevuti dalla Federazione
  • @box464 👀

    read more

  • #? @rf
    Поднял минималистичный инстенс mitra - а mastodon с ним не хочет педерироваться, говорит 503, а курл нормально всё достаёт:
    curl http://mitra.root.sx/users/l29ah --header 'Accept: application/activity+json'

    ЧЯДНТ?

    read more

  • I am waiting for ActivityPub and the Fediverse to make an appearance. I would suspect that the "expensive and annoying game of whack-a-mole" will start to get very hard to manage.

    https://www.abc.net.au/news/2025-12-04/when-is-the-teen-social-media-ban-what-apps-are-banned/106086152

    read more

  • @almino SIM

    read more

  • O @evan acabou de dizer que a W3C tá trabalhando em geo localização pro .

    Vamos ter vários "Foursquare" no Fediverso?

    read more

  • read more

  • Perfect! Let’s make something awesome :)

    @juergen_hubert @andypiper @alisynthesis @WeirdWriter

    read more

  • My approach to these issues is probably unfiltered, and I'm sorry if this makes my statements seem too categorical.

    I should also point out that when I talk about Bluesky being tied to huge funding (and therefore adequate returns), I'm not expressing a moral judgment. I want to be completely non-partisan on the matter.

    I simply wanted to provide my best explanation for the disruptions we're witnessing as a result of attempts at cross-pollination between the Blueskysphere and the Fedisphere.

    Let me try to explain myself better:

    considering the vertical nature of Bluesky PBC considering the horizontal nature of the Fediverse
    I don't rule out the possibility of cross-pollination, but I do rule out the possibility of it being guided by the same principles.

    The development of the Fediverse is, in fact, driven by the community of developers who work only on the application layer and know that (almost) none of them has the power to decide on the "protocol." And it isn't based on a single business model. On the other hand, those who have decision-making power over the protocol know that any change would have a huge impact on an extremely diverse ecosystem. It's not easy to decide what to change because it's not easy to understand what impact such a change could have.
    Bluesky's development, on the other hand, revolves around a single entity that holds decision-making power over the protocol, running the server and developing the app and APIs that dominate that ecosystem. And it's based on a business model that was already defined well before the protocol was created, with a protocol that was also developed with a business model in mind!

    The developers of the Fediverse were therefore Darwinianly selected by circumstances and today appear to be a bit more hacker-like, a bit more experimental, more adept at circumventing limitations, and (this isn't always a good thing...) more oriented toward community-driven financial support (and self-driven, because luckily for them, they all have IT jobs in a company). Moreover, not everyone is highly knowledgeable about the Activitypub protocol. And some of them are real "gourmets" of controversy...
    Bluesky developers, on the other hand, seem decidedly more "secular" to me; they also have to deal with a more rigid protocol (definitely more protocol-based than the Activitypub protocol), strong centralized decision-making power, and objectively have more limited room for manoeuvre. Furthermore, these developers' livelihood model isn't clear to me (I mean, beyond their IT jobs at some company: do they all work for Bluesky PBC?).
    I don't know... they seem like two worlds that aren't easily compatible, even from a social perspective...

    If this is true, then it shouldn't be surprising if the attitude of Bluesky stakeholders (the real ones, those sitting at the top) is positive only when a change could benefit their business model.
    Conversely, the responses from Fediverse stakeholders (i.e., those dozen or so de facto influencers who, with a nod, can determine the public's favor or hostility toward an initiative) might seem more disappointing.

    I reiterate that even if I were right, this attitude wouldn't stop the new ideas germinating between the Fediverse and Bluesky developers.
    It must be said, however, that since Bluesky was launched, I haven't seen any particular innovations. Recently, however, I've seen several new ideas emerge in the Fediverse, and these ideas, despite the rapidly declining user base, have led to very promising developments in the federated ecosystem over the past two years.

    All of this, however, would explain the communication difficulties between the two worlds, linked to the fact that the Bluesky leadership is too high-flying and the Fediverse stakeholders are too free-wheeling.

    I hope I've explained myself better, despite the language barrier.

    julian said in I also want to see #activitypub get some of the primitives that #atproto has such as decentralized identifiers (except for real), personal data stores, content addresses, etc.:
    > This is an important observation we should take into consideration.

    My theory, however, would explain this reaction... :grin:

    See you soon and have a good evening.

    read more
Post suggeriti
  • 0 Votes
    6 Posts
    16 Views
    Yeah, it's frustrating -- people have been asking for this since forever (well 2018 but close enough .There are some interesting perspectives from Claire on the challenges of adding this to Mastodon in a Github discussion in https://github.com/mastodon/mastodon/issues/7135#issuecomment-636767048@julian @miriamrobern
  • 0 Votes
    1 Posts
    11 Views
    so #bluesky is struggling with spam? we could've told you that dealing with that junk at scale won't work. that we have a much higher proportion of admins per user for a reason. but you chose to build your own. you're still not decentralized. but you obviously always cared more about making it profitable than sustainable.we are not the same. #ATproto #ActivityPub
  • 0 Votes
    1 Posts
    16 Views
    I submitted a Pull Request to update MacPorts' OpenSSH to 10.1p1 here:https://github.com/macports/macports-ports/pull/28592GitHub Continuous Integration checks passed OK!Alas, the agent.patch that iamGavinJ had created, doesn't apply cleanly, in large part because ssh-agent.c has been reworked significantly with this release.Subsequently, I closed this previous Pull Request: https://github.com/macports/macports-ports/pull/28592 not because I didn't want to restore that functionality to launchd, but because it will require more effort than I can give such things at this time.But, check out these improvements to ssh-agent from the OpenSSH 10.1 release notes:"ssh-agent(1)](https://man.openbsd.org/ssh-agent.1), sshd(8): move agent listener sockets from /tmp tounder ~/.ssh/agent for both ssh-agent(1) and forwarded socketsin sshd(8).This ensures processes that have restricted filesystem accessthat includes /tmp do not ambiently have the ability to use keysin an agent.Moving the default directory has the consequence that the OS willno longer clean up stale agent sockets, so ssh-agent now gainsthis ability.To support $HOME on NFS, the socket path includes a truncatedhash of the hostname. ssh-agent will, by default, only clean upsockets from the same hostname.ssh-agent(1) gains some new flags: -U suppresses the automaticcleanup of stale sockets when it starts. -u forces a cleanupwithout keeping a running agent, -uu forces a cleanup that ignoresthe hostname. -T makes ssh-agent put the socket back in /tmp."Anyway, I updated this as well:https://trac.macports.org/ticket/72482I should probably actually close this ticket now that I think of it (fingers crossed that adding that to the PR is sufficient, since I forgot to add that note to the commit message as is typically preferred: https://trac.macports.org/ticket/73084).#OpenSSH #MacPorts #SecureShell #macOS #encryption #security #infosec
  • 0 Votes
    2 Posts
    14 Views
    jeffries@ieji.de yes, it is beautifully presented and hits on some good points. I believe the author was a Bluesky employee, hence the lack of ActivityPub mention.