@Floppy @amcewen

The "which BIT" and the - as I call it - #LinkedData conundrum, I addressed recently in a #SocialHub topic on the #JSONLD vs plain #JSON nature of #ActivityPub. Inspired to write a long and personal #SocialExperience tale on my travels in wild #fedi lands. See..

https://social.coop/@smallcircles/116368803389082089

The #EU @ngi #grant programs and the hard work of @nlnet to distribute @EUCommission Horizon Europe #funding has done wonders to take #fediverse where it stands today. In my article I list all the many #FOSS projects that received stimulus and support during the years.

However something fundamental has been lacking in the mandate on who is eligible. Coding is Social. The support does not cover the rich tapestry of #expertise that end-to-end #solutions need during their lifecycle. Does not include fostering cohesive #technology ecosystems, healthy #OpenStandards evolution.

Effectively this creates a 'handover point' of software code from poor FOSS to others who earn a living with it.

@nicol @nlnet

It is the right ask though. The ask is: What are ALL the moving gears that make sustainable #FOSS (i.e. #SOSS) be produced, and in an entire healthy technology ecosystem at that.

My investigation around commons based social dynamics started when I had basically given up "trying to herd cats" at #SocialHub where it was already clear that most people didn't much beyond the interest for their own #ActivityPub project, to mingle in the discussions. I mentioned at the time in various thread "Do you want 'community-of-action' or just a mere discussion forum. But even for those questions there's hardly anyone interested.

I knew all this already from my time facilitating Humane Tech Community - now dormant, waiting for value at https://community.humanetech.com - but needed to more deeply understand.

The notion of #FSDL in its double meaning of #FreeSoftware development lifecycle, and #Fediverse solution delivery lifecycle rose from there, but also the need for a new adoption model.

As precursor to my blog post announcement later today, here's my #SocialHub response to the topic on how to treat the #LinkedData based #ActivityPub open standard where messages can be expressed both as plain #JSON as well as in #JSONLD, leading to the most costly misconception that has dragged the #fediverse sideways from its original promise and power..

https://socialhub.activitypub.rocks/t/practices-around-json-formatting-of-json-ld-messages/8628/24

@mavnn

> As an aside, I'm quite liking the ActivityPub APIs so far, although ld-json does leave me feeling like there's a fair jump from "script that works" to "actually does everything the spec would theoretically allow".

There's the "linked data conundrum" as I call it, which recently reared its head again, triggered by a #SocialHub post I created the other day:

https://socialhub.activitypub.rocks/t/practices-around-json-formatting-of-json-ld-messages/8628

The #LinkedData conundrum is the eternal friction between the plain #JSON and the #JSONLD view of the #ActivityPub social web. And it has never really be solved. I consider it one of the misconception that led to endless discussion, confusion, and waste of time. For the ActivityPub API which hold the promise to correct course towards a more standards-compliant #fediverse, I created an issue on the subject..

https://github.com/swicg/activitypub-api/issues/63

Followed by another on protocol design..

https://github.com/swicg/activitypub-api/issues/66

@fd93 @rriemann

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.

@reiver @thisismissem @mfru

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.