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

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

General Discussion
2 2 0

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
    1 Posts
    8 Views
    Well, let's see what direction we go in this time.Mastodon's founder is no longer its CEO https://www.engadget.com/social-media/mastodons-founder-is-no-longer-its-ceo-143011438.html?src=rss#Mastodon #Founder #CEO #ActivityPub #SocialMedia #Tech
  • 0 Votes
    1 Posts
    7 Views
    There are two big features in release v3.1.3 of Ktistec: auto-approve followers and a new image viewer.Auto-approve followers is conceptually simple ("the server automatically sends an Accept activity when it receives a Follow activity") but it required extensive changes to some of the oldest code in the codebase: the inboxes and outboxes controllers. I refactored inbox and outbox side-effect processing into independent services, which made it possible to support side-effects like auto-approve follow (and also auto-follow back), without having to go through the controllers.A more significant change for me personally was replacing the lightGallery image gallery (an external dependency) with my own implementation. It's not as slick, and not as full of features—I wrote it in two days—but it is fully free software, and that's important to me.AddedAdd admin page for managing OAuth access tokens.Add support for auto-approve followers. (fixes #26)Add support for auto-follow back.FixedPrevent triggering actor refresh when user is anonymous.ChangedReplace "lightgallery" dependency with custom image viewer.Set OAuth access token expiry to 30 days (previously expired after 24 hours).Refactor inbox and outbox processing into dedicated processor services.The OAuth changes set the groundwork for better support of the Mastodon API and the Fediverse clients that depend on it. Stay tuned!#ktistec #fediverse #activitypub #crystallang
  • 0 Votes
    1 Posts
    8 Views
    @cwicseolfor @juergen_hubert@sunkencastles.com It's the standard output that the #ActivityPub plugin for #WordPress generated - you can see the original article here:https://sunkencastles.com/2025/10/27/a-long-history-of-ableism-the-changeling-narrative/
  • 0 Votes
    11 Posts
    63 Views
    @evan @phi > We have some ad hoc ways to move from one to the other, but they aren't built into the SMTP or IMAP specsyes they are, though? in IMAP, you can just copy your messages and folders from one inbox to another. in SMTP, we have email forwarding.using your own DNS name can make things easier, but the main challenge in fedi is that we don't have a common storage/access abstraction (equivalent to IMAP folders), and we don't recognize HTTP redirects (equivalent to SMTP forwarding).