agree. This is also the gist of my post in the other branch.
Must. address. misconceptions. first.
agree. This is also the gist of my post in the other branch.
Must. address. misconceptions. first.
I'd say both of you are right, and neither are. The decision "Should it be JSON or JSON-LD?" is only part of the story. Both are but low-level data formats.
What needs more rigour is "How do I develop interoperable apps and services?", or even better "How do WE develop interoperable apps and services?" since interoperability means relying on others.
Fediverse currently evolves as a Big Ball of Mud anti-pattern due to the fact that post-facto interoperability - meaning "if you are first you can invent it on-the-fly" - is the dominant work method, and there is too little reconciliation of the tech debt and protocol decay that causes.
When misconceptions in ActivityPub aren't addressed, things will not improve.
JSON: Figure out in my app's codebase and perhaps docs what it means.
JSON-LD: You have ultra open standard flexibility, here see N specs on the magic of "linked data".
Both can't be just handwaved to as AS/AP extensibility mechanism.
Blog post is done already
and you and @silverpill the first ones I made reference to 
Here's the announcement, and be sure to fill in the #poll if you want.. https://social.coop/@smallcircles/116379158584600016
P.P.S. My latest blog post about #ActivityPub fediverse contains a "Back to (potentially radical) simplicity" call-to-reflection (among other subject matters) .. https://social.coop/@smallcircles/116368803389082089
Solution is.. difficult, but simple, yet not easy. 
Hey, thank you! Delighted you found my article even before I announced it on fedi 
https://social.coop/@smallcircles/116379158584600016
Thus far my poll on readership found 4 Meh skips. AI vs. long handcrafted thinkpieces: 1 - 0?
We'll see. Finding that out is also SX, after all. 
@bechele I made option 4 a combo mashup, that includes "Other", so you may still add your vote. 
#fediverse is at an inflection point.
Either revival and course correction to the original #ActivityPub protocol power and promise. With the potential to #ReimagineSocial.
Or keep current track with fedi-we-have. Be content with a few great and reasonably popular app platforms. Surely some more to come. But with a messy wire protocol that stifles #innovation and isn't future-proof.
#AskFedi do you dare to dream?
This special thought provoker is based on personal reflection and 8 years of #commoning. Deliberately exposed to the inherent unsustainability of the #FOSS movement. Burning privilege by spending my savings.
Goal: 1st-hand experience to learn the #social dynamics that make a #commons tick.
I invite you to a #brainstorm & #ideation ride. To ponder how #fedi can organically evolve. Become unbeatable by #hypercapitalism.
https://coding.social/blog/grassroots-evolution
But in an age of #AI who still reads long handcrafted #blogs? Fill in the #poll.
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
Flipboard looks like a very well organized company with good values and great work culture. Where their website leaves us completely in the dark however, is what its business model is, and where the revenue for all the salaries and investors is coming from. Should put more mouth to where the money is, to revert the saying 
Off-topic reformulation of the procedure in general terms.. In areas where PeerTube isn't post-facto interop leader itself, it should hope a reasonably broadly adopted #FEP consensus exists, or follow the post-facto leader in that particular application area and accept the upstream dependency to that part of the #ActivityPub specs the leader owns (and hopefully cares for, beyond their own needs, with good design and documentation).
@hongminhee that is really cool, thank you for explaining. Marvellous Unicode and browser capabilities.
At the start of my career I developed translation software for Philips for the creation of their product manuals in N different languages, Korean among them of course. And it was before Unicode existed, so I had to manually create character mapping tables for each language's codepage and input method editor combinations. It was absolute hell doing that, ha ha. That was why this particularly caught my eye and curiosity.
Interesting. I have never seen this text formatting before. I don't know any Korean
so can't tell if this is intentional or not. Is this a means to write both in Hangugeo and in ChosΕnΕ in a compact manner?
As for compatibility layer, bridging these worlds, the idea is that services encapsulate their design, which can be introspected and validated against.
For Protosocial AP extension I intend to conceptually divide the protocol layer into 2 API's. The Protosocial API provides a closed-world view of the social network as a JSON-LD-formatted but plain JSON distributed actor-based messaging architecture. While the Knowledge API exposes read-only open world information supporting full linked data.
I don't think 'suppressed' is the right word, but rather think you are feeling the *inertia* of the installed base. A reluctance to spend time on enabling technologies, by the majority of fedi app developers who already figured out how AS/AP works for them. Who are thus enabled to code, focused on their own project and less interested to mingle in time-consuming discussion. On what they consider out of scope, less relevant than adding features.
It would be very cool to have something like that. Thus far the list of games on the fediverse is saddeningly short:
https://delightful.coding.social/delightful-fediverse-experience/#fediverse-games
@applepine yes. I held this poll a couple days ago, with delightful results on the social experience of the current #fediverse: Dispersed cozy villages with here and there a bustling city..
https://social.coop/@smallcircles/116154415408228188
That is a great outcome, and something to cherish and protect.
Currently I feel the slow growth of the #ActivityPub fediverse is healthy and natural growth we can cope with. And #Bluesky being the lightning rod for corporate attention, borrows more time to mature and evolve.
The #SocialWeb dynamics will totally change if the technology adoption lifecycle gets beyond early adopter phase, and 1,000's of commercial vendors start to launch products in this new market space that we, pioneers, made available to them.
The question is whether we can handle that. I think currently we cannot and we have to hand over fedi's fate to the market and hope for the best.
I see the #fedi announcement by a commercial marketing agency of a venture capital based app store joining the fediverse.
Is the #fediverse we have capable of avoiding #enshittification as it grows and attracts an increasing number of corporations, who make it their market?
Is our #ActivityPub landscape resistant to corporate capture and eventual takeover and domination? Just like the Corporate Web, also decentralized.
There are nice niches on the web, like a bloggosphere, bulletin boards, and news readers, that all still exist. But web as a whole is predominantly corporate, arguably not commons based, for the people by the people.
Social experience design defines "commons based" as "where people are in control of their future on a path of healthy evolution and natural growth". A core principle is being sustainable at all times, and timely acknowledge and mitigate risks.
Is fediverse commons based? Did we cocreate the Future of Social networking?