🫧 socialcoding..Apparently a mention does not arrive at #SocialHub, perhaps a new top-level post does. I cannot check how the AP plugin is configured. Perhaps I'm holding it wrong, or these are the rough edges that exist.
Discourse has an official ActivityPub plugin, though it is fairly rudimentary at this point, and needs more love I'd say.
The #SocialHub community forum is federated, for instance. https://socialhub.activitypub.rocks and is also used by the AP plugin maintainers for testing the functionality.
@silverpill @raphael @julian @mariusor
Btw, damn we should've caused this entire discussion thread to somehow flow to #SocialHub to have it in the archives. Instead of on "now you see me, now you don't" channel. Peekaboo. 🫣
https://social.coop/@smallcircles/116141469199837056
Here today, gone tomorrow, who made notes? The post-facto interoperability leaders did. Those who happened to be around at the right time to hear things being said on the grapevine.
We need a proper Grassroots standardization process, and a Grassroots open standard that is able to healthily evolve. The good organization of this is just as important as the technical robustness of the protocol, which is the solution artifact at the end of the open standards cocreation pipeline.
I made a diagram yesterday that contrasts #ActivityPub and #SolidProject that is I think interesting to consider.
In the past I've been very active on the Solid forum, and tried to get a collab going with #SocialHub community. A number of points that existed then, are still issues today I think.
Like, though anyone could participate in the standards process via chat, the Solid team and Inrupt were not really interested in their community, hardly giving attention while people were building interesting stuff there.
Also at the time basically all available code was Javascript, making Solid uninteresting or hard to access for other language devs.
But I think biggest issue was that Solid didn't know what it was. It was positioned as 'personal data vault' on the landing page then (but not using this term), but was 'secretly' TBL's desire to reboot the #SemanticWeb. The new web would be all 'Solid apps'. But the adoption strategy for that didn't exist.
I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the #AltText
See also and for discussion: https://discuss.coding.social/t/diagram-interoperability-in-practice/828
Or join the Social experience design chatroom at: https://matrix.to/#/#socialcoding-foundations:matrix.org
Also posted to #SocialHub at: https://socialhub.activitypub.rocks/t/activitypub-versus-fediverse-interoperability-in-practice/8498
#SX #SocialCoding #SocialWeb #ActivityPub #SolidProject #fediverse
To chain things together a bit on this fleety medium of ours, create a hyperweb 😜 I'll quote this toot to follow-up to
https://social.coop/@smallcircles/116110545919004233
I remember about 2018 or so, when I joined my first #SocialCG meetup. It was when the CG was still strongly tied to #SocialHub community.
There were mundane items on the agenda, interesting to any #ActivityPub dev, and also the call to action was "whether you are technical or not at all, join the meetup, we are open and inclusive to all fedizens". Very friendly, good vibes.
However during the session the talk was not only CS expert level, but dealing with subject matter nowhere near the spec. It was 'wire reality' slang, and to learn it the guidance was either nowhere, or everywhere, dispersed. And this is still as it is today. To expertised AP developers their domain language sounds all natural, but it likely seems Martian to a dev newcomer.
Stark contrast to the W3C specs that leave folks with refreshing "Let's implement this" vibe.
Thank you, that is nice to hear. I am however not an expert, am but a humble generalist and a person who'd love to be in that Solution developer stakeholder role. Who however does not see the fediverse trend in a direction where I'd adopt the technology for what I have in mind. Drifting away from "the promise" that I read in the #ActivityPub specs in 2017, and which at the time made me decide to lend a helping hand here and there as #SocialHub facilitator and tech advocate.
#OMN (Open Media Network)Europe, the Fediverse, and the story we failed to tell
A bunch of native #openweb people spent real time, energy, and focus pushing the #EU toward the #Fediverse. This wasn’t theoretical, it wasn’t speculative, it wasn’t a #NGO whitepaper or a #VC funding pitch. It was practical outreach, grounded in working technology and lived experience, aimed at reducing Europe’s dependency on centralized corporate platforms. One concrete moment of this work was the webinar organised between the European Commission and the ActivityPub community: […]https://hamishcampbell.com/europe-the-fediverse-and-the-story-we-failed-to-tell/
@hrast I've seen this passing by in #fediverse discussions many times, but always in fleety timelines.. aka lost-in-time no further #ideation lines :)
This is a good #idea to describe in more detail in the ideas inbox. Staging ground for the #FEP process and #SocialHub #ActivityPub developer community, if there are people willing to pick them up. And then in turn perhaps staging ground for further standardization by #W3C #SocialCG.
#SocialHub community forum has the #ActivityPub plugin enabled yet 1st with full open, untweaked federation settings. Accessiblity for any #fedizen got a real boost. Yet with big negative impact on 'sense of community'. It's up for debate whether adding #fediverse support in early stages of dev was a wise move. And whether the result is net negative or positive (I think the former).
Any fedi dev: Think hard what it means to be federated. It's more than just 'plugging in'. Consider the #SX side.