@smallcircles "Even more remarkable is the near complete absence of the #ActivityPub developer community in mingling in the social side of the discussion."
Once you've been here for a little longer you'll realise this statement isn't the case.
Créer un système de partage de contenus sur #BitTorrent fédéré avec #ActivityPub.
#fenêtreDOvertonDuPiratage #fediverse
There are people I follow who I never see on my home feed, but when I go to their profile I see they post frequently.
Makes me suspect they blocked me or something, but then I wouldn't be able to see their profile. Also, when I reply to them they see it.
Maybe I'm accidentally muting?
More likely explanation: #ActivityPub just be like that sometimes.
Moim.live Release note (v0.2.0)
https://hackers.pub/@kodingwarrior/2026/moim-live-release-note-v020
Dé-GAFAMiser #1
> Mes solutions alternatives ¶
C'est suite au message d'@loevenbruck, l'auteur, qui annonçait son indépendance des GAFAM que je me suis lancé.
Aujourd'hui la quasi totalité des applications que j'utilise en remplacement sont installées sur un serveur d'application auto-hébergé, sauf Signal.
> Un serveur d'application #Yunohost ¶
J'ai choisi d'installer l'ensemble des applications sur Yunohost, le serveur d'application simplifié, dédié à l'auto-hébergement. Cette distribution basée sur Debian dispose d'un catalogue étoffé d'applications prêtes à l'installation.
J'ai commencé il y a 2 ans sur un micro-PC d'architecture AMD64, sur un microprocesseur N3000, puis j'ai basculé sur un micro-PC toujours en AMD64, sur un microprocesseur Intel de 11ème génération, i5-11320H, histoire d'être tranquille pour quelques années.
> Le nom de domaine ¶
J'utilise les services d'#OVH depuis de nombreuses années pour gérer les domaines et l'hébergement de sites personnels ou professionnels.
Quelle chance, la gestion de l'API de gestion de domaines d'OVH est disponible sur Yunohost. Elle permet de créer, éditer, supprimer les domaines et sous-domaines de presque tous les besoins des applications.
Nous reverrons le sujet avec Cryptpad.
> La stratégie d'utilisation des sous-domaines ¶
Après quelques essais, j'ai installé le catalogue d'applications sur apps.newan.net pour laisser le domaine principal disponible. Le serveur de messagerie électronique fournit donc des adresses en "@newan.net".
Puisque les applications #Prosody, qui gère le serveur de messagerie #XMPP, et #Mastodon, qui fournit le serveur #ActivityPub, ne sont pas mutuellement exclusives, elles sont toutes les deux installées sur le domaine principal.
En revanche le serveur de messagerie instantanée (mais pas seulement) #Matrix ne supporte pas la concurrence. Il est donc installé sur le sous-domaine matrix.newan.net, ce qui surcharge les adresses Matrix de ce sous-domaine.
Cette installation est le résultat d'échecs et de réussites sucessifs. Le serveur ActivityPub sur le premier micro-serveur tournait sur le logiciel #Pleroma, puisque je n'avais pas réussi à installer Mastodon. C'est au passage vers le serveur sur i5 série 11, que j'ai réussi à installer Mastodon.
De même, j'utilisais initialement le serveur XMPP #Métronome fourni par défaut avec Yunohost. Ce n'est que lorsque j'ai eu besoin d'installer le serveur de visio-conférence #Jitsi, que j'ai désintallé Métronome pour le remplacer par Prosody.
La suite sur https://eikan.newan.net/Libre.
Besides falling in the thread by context collapse with an unsubstantive remark (which I don't blame you for, as such is the nature of this communication medium), I've been posting extensively on some of the wicked challenges we must overcome, and which determine the future(s) of the fediverse(s) we have today. There is a lot to ponder about. It is not all technical in nature, and I'd argue our problems are more on the social side of things even.
An open standard is a technical artifact. The reason why someone creates the next standard, is a social one. Coding is social.
What is very remarkable is that on a poll asking fedizens about their social experience, and discussing deeper issues in the various subthreads, not any of the #ActivityPub developers are mingling in.
This shows more than anything to me the app-centric nature of the fediverse, and how it evolves in a pure technosphere where app devs are in charge, the rest are users.
@fox @raphael @julian @mariusor
@csarven @strypey @FinchHaven @naturzukunft2026
My arguments of the last two weeks that are spread about the timeline, boils down that Coding is Social, and code alone and passion for tech isn't always enough. Esp. if one depends on an entire technology ecosystem in a pioneering stage of its technology adoption lifecycle, that should evolve along with them. And which evolves on the basis of chaotic grassroots social dynamics that no one is able to steer onto a healthy adoption path. There are wicked problems to overcome, and they are mostly social in nature. I took notes on this for the fediverse years ago, and these challenges are still the same to this day, haven't been tackled.
https://discuss.coding.social/t/major-challenges-for-the-fediverse/67
We have a successful fediverse now, but also one who has limited its application area, hemmed themselves in wrt the original 'promise' of AP. With the #ActivityPub API there's opportunity to make step in place, and get some of that back. And go LD route too.
https://social.coop/@smallcircles/116109447243110037
Read the blog post, and these are astute observation and valuable way of thinking about the networking environment, both offline as well as online, and how they interact together, how they intertwine. #SX envisions a peopleverse (which is a concept, not a name), a hypothetical space where the interaction is seamless and technology unobtrusively serves our day to day needs.
#PersonalSocialNetworking is a powerful instrument to design better social experiences.
Often the talk of the town in the #ActivityPub dev circles is about some feature or other, an app functionality and the extent to which it can be made interoperable. Technical implementation details dominate the discussion. And drama ensues on the broader #fediverse if social impact and other externalities are overlooked in an app design.
When comparing #microblogging we have today, it really is like sticky notes on the fridge, which fall off or are removed by people. And we project all communication modes onto them.
Oww, that is interesting. See here what brought me to the #ActivityPub fediverse ages ago on IT timescales..
https://social.coop/@smallcircles/116109998586728783
@smallcircles @strypey @FinchHaven @naturzukunft2026
Hi, author of some things here. I can assure you that that is more of that big bad "semantic web" stuff baked into #ActivityPub than there is to #SolidProject but people spin things as they want to for a narrative. That said, totally agree with you that do x and y will come is not enough. Folks conflate various variables or attempt to boil things down to a single perspective. The reality is far more strange and unpredictable.
@strypey @FinchHaven @naturzukunft2026
For the sake of further clarity I should point to your starting post and this text:
> we need domain-specific applications that leverage ActivityPub’s full semantic potential
And remark that in my opinion and by observation, tapping the sign "Reminder: #ActivityPub is #JSONLD, folks!" isn't enough. Much more is needed than pointing to the #OpenStandards to win back developers minds to adopt #LinkedData. There is a high reluctance and resistance to adoption that must be overcome.
Referring again to that adoption chart I drafted the other day - which is about #SolidProject, but this is where LD is strong(est?) today - "build open standards, and they will come" isn't going so well. I hope that changes, as I have always been a fan of the *notion* of the semantic web. Yet in role of a technology decision maker, not ready to bet on it for a social networking environment.