B
@taylorlorenz@mastodon.social fancy meeting you here! big fan, read the book and everything.
this isn't at all what you asked for, but i wrote an essay once that might be useful in more of a bigpicture/media-industry context.
you might also find to check out (or interview) elena, who is kind of our resident fedifluencer <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f49e.png?v=0b03a81bb1f" title="
" />
@rimu@piefed.social we if it's a trap we're all in it because ActivityPub is a JSON-LD serialization fullstop, if the collective action problem results in a majority of projects wanting to abandon that and hardcode to a closed-world JSON model just fork the protocol and call it something else.
> @hongminhee@hollo.social said in I have deeply mixed feelings about #ActivityPub's adoption of JSON-LD, as someone who's spent way too long dealing with it while building #Fedify.:
>
> Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.
This asymmetry of blame and credit is a real problem in distributed systems generally, as much economically as emotionally. The system doesn't actually scale to multiple disjoint platforms and orthogonal ecosystems without someone doing the hard work of open-world translation... if everyone hardcodes their preferred JSON shape it quickly becomes a zero-sum game and small players have to do much more work than big players. This has consistently been a challenge for public-benefit funders, who try funding load-bearing infrastructure like fedify to avoid those dynamics, but that often demands funding bigger teams on longer horizons than they are set up to fund by their structure.
