Event JSON
{
"id": "112eda9d859417da25375c3e3097df2ecd26b1ec9690cb99b5e572ed08a9e919",
"pubkey": "a9b788528b0fc4650dab10e486c86c151dde0cdf5fa87ce5be30c6472cc10fc5",
"created_at": 1678556366,
"kind": 1,
"tags": [
[
"p",
"4a412ca2af5a5cef2dec7e03805118e3cdadad83a600125c6b8dd2ab9e789ffb",
"wss://relay.mostr.pub"
],
[
"p",
"73285a69e89eb999c78a7ccf3bd73312529aefa05f0ccca084fa0fbf19862107",
"wss://relay.mostr.pub"
],
[
"p",
"e2bc32de32285830ffa94c3619e8a7c9cd7df0176a306fb59af777b07ca1e6e6",
"wss://relay.mostr.pub"
],
[
"p",
"b64de52edd2b8dd13750503b77b6b56bfb3a68825659988fb3a218640c4c6bec",
"wss://relay.mostr.pub"
],
[
"p",
"ec55841e6b607007a0167bd7e8d844705669336aef56485b48f4d38f51e5f68d",
"wss://relay.mostr.pub"
],
[
"e",
"cadb192c0d84fef843e7133deb9e56c93ffe3e7220f8fb5f30a7b07fd100d038",
"wss://relay.mostr.pub",
"reply"
]
],
"content": "#[0] \n\n#[1] is an especially _weak standard_ where interoperability (the ability to talk back-and-forth with an AP system) is very ad-hoc and tends to be defined very heavily by the behavior of the largest and best-known implementations\n\nSo it is relatively straightforward for a company like Meta to throw resources at it, make changes that are incompatible, and then shift everyone to something custom down the road\n\nSee #[2]'s https://lists.w3.org/Archives/Public/public-swicg/2023Mar/0067.html for how it can break down.",
"sig": "a6a539ef0caabe8dade6745fa0da75d59f0fd6610f1305443c44f4612405e2f81fa99666a8b9d6ce0a68f164d82d42bea9cd1b6eeb9ed14b051cfed1aceff749"
}