From 77446e77ed360417cb71d3f3105da6a47946b245 Mon Sep 17 00:00:00 2001 From: a Date: Mon, 8 May 2023 12:31:37 -0400 Subject: [PATCH] ordered attachments and tags --- .../spec/activitypub/ideas/do-not-inline.md | 4 +--- .../activitypub/ideas/orderedAttachment.md | 20 +++++++++++++++++++ 2 files changed, 21 insertions(+), 3 deletions(-) create mode 100644 content/tech/spec/activitypub/ideas/orderedAttachment.md diff --git a/content/tech/spec/activitypub/ideas/do-not-inline.md b/content/tech/spec/activitypub/ideas/do-not-inline.md index caa64bf..67a5c1c 100644 --- a/content/tech/spec/activitypub/ideas/do-not-inline.md +++ b/content/tech/spec/activitypub/ideas/do-not-inline.md @@ -1,6 +1,4 @@ -### maybe objects shouldn't be inlined tho - -spritely magenc golem ocappub etc etc etc +maybe objects shouldn't be inlined tho? spritely magenc golem ocappub etc etc etc ```yaml id: alice.example/54078934249073290847321094/activity/1 diff --git a/content/tech/spec/activitypub/ideas/orderedAttachment.md b/content/tech/spec/activitypub/ideas/orderedAttachment.md new file mode 100644 index 0000000..8056f8a --- /dev/null +++ b/content/tech/spec/activitypub/ideas/orderedAttachment.md @@ -0,0 +1,20 @@ +problem: sometimes you want to have attachments in a certain order, but `attachment` is an unordered set by default + +solution: define `orderedAttachment` similar to `orderedItems` + +```json +{ + "@context": [ + { + "orderedAttachment": { + "@id": "https://...", + "@type": "@id", + "@container": "@list" + } + }, + "https://www.w3.org/ns/activitystreams" + ] +} +``` + +you could maybe do the same for `orderedTag` but idk if that makes full sense bc `tag` is not really used for categorization so much... but if tumblr or a tumblr-like implementation wanted to order their tags then they have no way of doing so \ No newline at end of file