@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

> if the challenge of knowing what Fediverse Apps implement which bit of the spec is a blocker, is there a standard way to declare which bits of the spec an app is conformant in?

The #ActivityPub #FEP process keeps a list of implementations, in each of its documents. The FEDERATION.md was once introduced as "something to start with before going more complex wrt introspection", a temporary bandaid to bring improvement. Its adoption and use, and later its description as a recommended practice are going very slow though. Still, a very useful practice, compared to lacking such doc and perusing foreign codebases for the info.

> does the Fediverse need a democratic membership org that funds core maintenance of FEP and pays for some of the core community maintainers to keep looking after the ecosystem.

That might be a good solution. For part of a much bigger problem. No #funding bakes bread yet.

I addressed this with @nlnet in the past, and intend to bring it up again next week.

#TokensOfGratitude 🌻

My personal thanks goes out to the many people that helped me stick around in this great #ActivityPub space full of fedizens.

Especially grateful I am, for their consistent support during many yeas, towards the @EUCommission who with @ngi and @nlnet made a BIG difference to where the fediverse stands today.

It goes to show that only with a little "breadcrumb funding" - as I call it in my #SocialExperience piece on my years of navigating chaotic #commons, doing #CommonsJanitoring and #CommonsCustodian duties - can already achieve so so much 🪙🪙

I hope for further improvement to the #funding facilities that are available to #FOSS and #SocialWeb cocreators, and look expectedly to upcoming changes in the #HorizonEU grant programs and their alignment to our fediverse developer ecosystem.

PS. You can find my definition of #BreadcrumbFunding in the "Challenges of standardization" section of my blog post, right before the call to ideation.

https://coding.social/blog/grassroots-evolution/#challenges-of-standardization

#SX

#TokensOfGratitude 🌻

My personal thanks goes out to the many people that helped me stick around in this great #ActivityPub space full of fedizens.

Especially grateful I am, for their consistent support during many yeas, towards the @EUCommission who with @ngi and @nlnet made a BIG difference to where the fediverse stands today.

It goes to show that only with a little "breadcrumb funding" - as I call it in my #SocialExperience piece on my years of navigating chaotic #commons, doing #CommonsJanitoring and #CommonsCustodian duties - can already achieve so so much 🪙🪙

I hope for further improvement to the #funding facilities that are available to #FOSS and #SocialWeb cocreators, and look expectedly to upcoming changes in the #HorizonEU grant programs and their alignment to our fediverse developer ecosystem.

PS. You can find my definition of #BreadcrumbFunding in the "Challenges of standardization" section of my blog post, right before the call to ideation.

https://coding.social/blog/grassroots-evolution/#challenges-of-standardization

#SX