From a304590ba8222df55cd05783af1c96cc2e3d8abf Mon Sep 17 00:00:00 2001 From: a Date: Fri, 5 May 2023 08:30:12 -0500 Subject: [PATCH] split page into distinct ideas --- .../spec/activitypub/confusion/note-vs-article.md | 4 +++- .../shortcomings/Mention-too-narrow.md | 5 +++++ ...lear-type-semantics.md => Note-distinction.md} | 15 +-------------- .../shortcomings/extensibility-in-plain-json.md | 3 --- .../activitypub/shortcomings/not-reusing-vcard.md | 3 --- 5 files changed, 9 insertions(+), 21 deletions(-) create mode 100644 content/tech/spec/activitypub/shortcomings/Mention-too-narrow.md rename content/tech/spec/activitypub/shortcomings/{unclear-type-semantics.md => Note-distinction.md} (68%) diff --git a/content/tech/spec/activitypub/confusion/note-vs-article.md b/content/tech/spec/activitypub/confusion/note-vs-article.md index 57168b3..be2a863 100644 --- a/content/tech/spec/activitypub/confusion/note-vs-article.md +++ b/content/tech/spec/activitypub/confusion/note-vs-article.md @@ -104,4 +104,6 @@ but it's really that last one that seems most salient to me. consider an Article type: Note name: "Pronouns" content: "they/them" -``` \ No newline at end of file +``` + +note that Note might still have an id, though... so really it's just a vague ill-defined "intention". for example, maybe use a Note for a "status update" in a chat/presence sense? like XMPP PEP. \ No newline at end of file diff --git a/content/tech/spec/activitypub/shortcomings/Mention-too-narrow.md b/content/tech/spec/activitypub/shortcomings/Mention-too-narrow.md new file mode 100644 index 0000000..2068a2f --- /dev/null +++ b/content/tech/spec/activitypub/shortcomings/Mention-too-narrow.md @@ -0,0 +1,5 @@ +> Mention: A specialized Link that represents an @mention. + +this is an incredibly narrow definition and also one that is often useless. what's so special about an @mention? + +it would have been better to define it in terms of, idk, generating a notification or something? like a webmention? \ No newline at end of file diff --git a/content/tech/spec/activitypub/shortcomings/unclear-type-semantics.md b/content/tech/spec/activitypub/shortcomings/Note-distinction.md similarity index 68% rename from content/tech/spec/activitypub/shortcomings/unclear-type-semantics.md rename to content/tech/spec/activitypub/shortcomings/Note-distinction.md index 290e614..31f8fc2 100644 --- a/content/tech/spec/activitypub/shortcomings/unclear-type-semantics.md +++ b/content/tech/spec/activitypub/shortcomings/Note-distinction.md @@ -1,10 +1,3 @@ -+++ -+++ - -# the semantics of some types are unclear or poorly defined - -## Note vs Article - see [Note vs Article]({{}}) for more. but basically: in summary: @@ -19,10 +12,4 @@ the messy general consensus post-spec seems to be about "intention", but this is it would have been better to define it similarly to HTML `
` perhaps? an independent unit of writing? one that is published and therefore might reasonably be syndicated? -## Mention - -> Mention: A specialized Link that represents an @mention. - -this is an incredibly narrow definition and also one that is often useless. what's so special about an @mention? - -it would have been better to define it in terms of, idk, generating a notification or something? like a webmention? \ No newline at end of file +and maybe Note should have been forced plaintext. idk. at the very least the distinction should be better explained. \ No newline at end of file diff --git a/content/tech/spec/activitypub/shortcomings/extensibility-in-plain-json.md b/content/tech/spec/activitypub/shortcomings/extensibility-in-plain-json.md index 04d00af..6ac9def 100644 --- a/content/tech/spec/activitypub/shortcomings/extensibility-in-plain-json.md +++ b/content/tech/spec/activitypub/shortcomings/extensibility-in-plain-json.md @@ -1,6 +1,3 @@ -+++ -+++ - # extensibility for plain-json consumers is underconstrained the recommendation in the spec is to use JSON-LD for extensions, which leaves open the "best practices" on how might one expect to serialize and parse those extensions. diff --git a/content/tech/spec/activitypub/shortcomings/not-reusing-vcard.md b/content/tech/spec/activitypub/shortcomings/not-reusing-vcard.md index 533bc59..62b4b2a 100644 --- a/content/tech/spec/activitypub/shortcomings/not-reusing-vcard.md +++ b/content/tech/spec/activitypub/shortcomings/not-reusing-vcard.md @@ -1,6 +1,3 @@ -+++ -+++ - activitystreams 2.0 defines some actor types like Person, Group, Organization these types should not have been defined at all. they should have reused the vcard properties. the semantics of the types have led to mistakes such as people looking at Group and assuming that it's a facebook-style group, when that's not the definition at all. \ No newline at end of file