Event JSON
{
"id": "bd23734078651302979e19ed691445da2699f734b4be287c4ee5382aef157453",
"pubkey": "d9944edbb9d6da3a1a485cd89464e1f99be5e26eeac07cb011f3aa4fe3ab3770",
"created_at": 1745875414,
"kind": 1,
"tags": [
[
"emoji",
"boost_ok",
"https://files.ausglam.space/custom_emojis/images/000/033/226/original/4d9d453a6a4a237e.png"
],
[
"proxy",
"https://ausglam.space/@hugh/114417691179911082",
"web"
],
[
"t",
"activitypub"
],
[
"proxy",
"https://ausglam.space/users/hugh/statuses/114417691179911082",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://ausglam.space/users/hugh/statuses/114417691179911082",
"pink.momostr"
],
[
"-"
]
],
"content": "As far as I understand, most (all?) fediverse #ActivityPub software does not use the Client-to-server protocol from the specs (https://www.w3.org/TR/activitypub/#client-to-server-interactions) but rather use custom APIs instead.\n\nAny fediverse devs able to explain why? Is there a technical reason/limitation, or is it more about other considerations? \n\nI'm looking for information here rather than speculation, thanks.\n\n:boost_ok:",
"sig": "07ef6ed919e2156435fd5056e586cad95db643586044fdc86a12d0db84c78348ffa4c54237c5b3d1a032627989128dc09cd82eb78c9aa741d671c2306102e886"
}