The biggest problem with developing for #ActivityPub is answering the question "so WHICH BIT didn't work?".
-
The biggest problem with developing for #ActivityPub is answering the question "so WHICH BIT didn't work?".
The second biggest problem with #ActivityPub dev is that when debugging, you have to look at your Mastodon* feed, and it's *impossible* not to get distracted.
*other softwares are available
-
The second biggest problem with #ActivityPub dev is that when debugging, you have to look at your Mastodon* feed, and it's *impossible* not to get distracted.
*other softwares are available
go ahead, ask me where my day went.
-
@amcewen yeah, it's not too hard once you work out what `@context` is doing. That said, that's probably where my current bug lies.
-
-
@amcewen yeah, it's not too hard once you work out what `@context` is doing. That said, that's probably where my current bug lies.
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.
-
It DOES create problems though, just not on the level of an individual project that is part of the AP ecosystems. Though it likely does, and I've seen this mentioned recently, give problems to the JSON-LD folks out there.
And if they stick to Linked Data approach, they are right and the ones doing Linked Data wrong or half-baked thought theoretically fall in line, given that W3C ActivityPub is a linked data based standard first of all, that permits JSON interpretation unless in compliant ways.
I just mentioned on a fork in this thread some of the issue at larger ecosystem scale, which started with discussion on - to use the general term Rich Hickey named it in his "Hammock driven development" talk - the Misconception around LD from the early start, that was never addressed.
Cardinal mistake if you ask me. But here's the thing: No one can be blamed in a chaordic commons. It can't organize for strategic direction very well.
-
It DOES create problems though, just not on the level of an individual project that is part of the AP ecosystems. Though it likely does, and I've seen this mentioned recently, give problems to the JSON-LD folks out there.
And if they stick to Linked Data approach, they are right and the ones doing Linked Data wrong or half-baked thought theoretically fall in line, given that W3C ActivityPub is a linked data based standard first of all, that permits JSON interpretation unless in compliant ways.
I just mentioned on a fork in this thread some of the issue at larger ecosystem scale, which started with discussion on - to use the general term Rich Hickey named it in his "Hammock driven development" talk - the Misconception around LD from the early start, that was never addressed.
Cardinal mistake if you ask me. But here's the thing: No one can be blamed in a chaordic commons. It can't organize for strategic direction very well.
@smallcircles @Floppy @amcewen I don’t think it’s the problem you make it out to be … we create a “Living standard” similar to how whatwg did for the web two decades ago … we drop json+ld from it and use a more frictionless approach to interop that is based on FEPs defining new attributes, and FEPs look at the fediverse as-is to find how to do that in a frictionless way, no complicated namespacing needed
-
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.
@Floppy @amcewen @ngi @nlnet @EUCommission
Btw, I just used the phrasing "ActivityPub ecosystems", plural, in a fork of this discussion (see quote of this post).
And I think that against the holistic breadth and scope that I am exploring our fediverse #technology landscape, that is a fair assessment.
In this wild garden of our #fediverse commons, there exist different islands of green moss, sometimes barely touching, or with infurtile patches between them to be bridged, or actively repelling each other, lacking synergetic relationships that make furtile tendrils intertwine.
That is for another exploration in a future blog post I may write, come my self #sustainability again. #SX et all is all just Hobby social activity track (SAT) right now..
https://coding.social/blog/reimagine-social/#social-activity-tracks
-
@smallcircles @Floppy @amcewen I don’t think it’s the problem you make it out to be … we create a “Living standard” similar to how whatwg did for the web two decades ago … we drop json+ld from it and use a more frictionless approach to interop that is based on FEPs defining new attributes, and FEPs look at the fediverse as-is to find how to do that in a frictionless way, no complicated namespacing needed
Yes, that is the good approach. And is what is happening also, in a good way. Question is if it is happening in the best way. In the SocialHub discussion around my blog post, my (quite holistic) considerations around the overall Grassroots standardization process in our chaotic commons, was misunderstood.
The question is, is there a vision, an ideal, towards which the standards should evolve, to be able to support the Future of Social Networking. If yes, what is it? What do we rally together for? Is it decentralization, and is that enough? Answering that would mean (re)imaging what that future might hold. There's too little of that today, and if it happens, it happens on fleety ephemeral microblog or chat spaces. Long gone musings in timeline history now.
On SocialHub I gave the example of @cwebber @spritely Fantasary as capturing a vision, that may be lost today.
-
Yes, that is the good approach. And is what is happening also, in a good way. Question is if it is happening in the best way. In the SocialHub discussion around my blog post, my (quite holistic) considerations around the overall Grassroots standardization process in our chaotic commons, was misunderstood.
The question is, is there a vision, an ideal, towards which the standards should evolve, to be able to support the Future of Social Networking. If yes, what is it? What do we rally together for? Is it decentralization, and is that enough? Answering that would mean (re)imaging what that future might hold. There's too little of that today, and if it happens, it happens on fleety ephemeral microblog or chat spaces. Long gone musings in timeline history now.
On SocialHub I gave the example of @cwebber @spritely Fantasary as capturing a vision, that may be lost today.
@smallcircles @Floppy @amcewen @cwebber @spritely yeah, I agree that we’d need a proper vision as well
