Another nail in the coffin for #JsonLD:
That's a post that I edited shortly after I first made it. The corresponding conversation container contains both the original Create, and an Update with the changes. This means that the embedded Note object appears twice, with different contents, but with the same ID.
JSON-LD processing will kind of squish them together into the same object that contains both the original and the new
#ActivityPubDev
{
"id": "https://zotum.net/conversation/235e8736-1b3e-4d7f-ab9e-3d49f04ecda7",
"orderedItems": [
{
"type": "Add",
"object": {
"type": "Create",
"object": {
"type": "Note",
"id": "https://zotum.net/item/235e8736-1b3e-4d7f-ab9e-3d49f04ecda7",
"published": "2025-02-25T20:28:33Z",
[... original version of post ... ]
},
},
},
{
"type": "Add",
"object": {
"type": "Update",
"object": {
"type": "Note",
"id": "https://zotum.net/item/235e8736-1b3e-4d7f-ab9e-3d49f04ecda7",
"published": "2025-02-25T20:28:33Z",
"updated": "2025-02-25T20:29:03Z",
[... edited version of post ...]
},That's a post that I edited shortly after I first made it. The corresponding conversation container contains both the original Create, and an Update with the changes. This means that the embedded Note object appears twice, with different contents, but with the same ID.
JSON-LD processing will kind of squish them together into the same object that contains both the original and the new
content etc. Handling this as JSON-LD will mean recognising the high level structure of it first, and then iterating over the orderedItems and processing them individually, rather than trying to treat the whole thing as a single JSON-LD message.#ActivityPubDev