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.

@ben

@evan

> it's ok if you haven't heard of a REST API.

Well, you be you. I consider this a 'typical Evan remark' by now, dripping with sarcasm. It is a weird fit for someone who want to lead the #SocialCG efforts, I'd say.

Ah well. What I am talking about is architecture and design, and all the things that allow people to easily form a clear mental picture on how things fit together, wrap their head around the fediverse.

A HTTP interface is a very low-level thing, and clearly but one of the many moving parts that play a role in #ActivityPub based solution development.

Never defining this well, and having the documentation be scattered all across the fediverse in 1,001 random locations doesn't help. Meanwhile the dev talk that is going on for years remains very inefficient due to endless Babylonian speech confusion.

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

@cwebber @steve

#ActivityPub, a *great start* providing the key ingredients.

#Fediverse, where things are cooked into a mush, by pragmatic though unsustainable fast-food preparation.

Recipe:

- Mash everything into #ActivityStreams
- Overload the semantic frying pan
- Sprinkle in combinatorial complexities
- Cook until too hot

Then simply keep stirring with increasing whack-a-mole maintenance burdens until project phased out.

Or become the post-facto #interoperability leader and dominate the restaurant chain.

Recipe improvement tips:

- Add #FEP spice to the mix where you can!
- Participate in #SocialCG collective cooking.

@steve @jerger

Yes, I would highly discourage the use of "app". It is why I scare quoted it, but "app" is common language when people talk about the fediverse. "App" is a neat container concept that fits the full scope of ones own FOSS project, but on the fediverse - a growing heterogeneous and interoperable social network - one becomes highly dependent on the foundational network communication layer based on #ActivityPub, and any fedi FOSS developer should be concerned beyond direct project scope, and pay attention that this foundation evolves healthily. This unfortunately happens unsufficiently, and only a very small number of people try to get the ecosystem as a whole to higher levels, volunteering time where it does not directly benefit their own projects. Think @silverpill for the #FEP and @evan for #SocialCG.

Cool find yesterday was that @HolosSocial rather than C2S has a "full AP server" client-side, that communicates with a Websockets tunnel to a dedicated relay server.