From 79d44ae131e40d96151b7afc4f0f0f8ca6d990ec Mon Sep 17 00:00:00 2001 From: Dave Jones Date: Thu, 25 Apr 2024 15:54:07 -0500 Subject: [PATCH] allow socialInteract in - closes #601 --- docs/1.0.md | 40 ++++++++++++++++++++++------------------ socialprotocols.txt | 3 ++- 2 files changed, 24 insertions(+), 19 deletions(-) diff --git a/docs/1.0.md b/docs/1.0.md index e354680..31d4de0 100644 --- a/docs/1.0.md +++ b/docs/1.0.md @@ -901,6 +901,9 @@ The node value is a string denoting one of the following possible values: version audio enclosure attached. - `blog` - Describes a feed of informally written articles. Similar to `newsletter` but more informal as in a traditional blog platform style. +- `publisher` - Describes a feed that links to other feeds a publisher owns using the `` element. + To understand the structure of how "publisher" feeds work, please see the dedicated document + (here)[publishers/publishers.md]. ### List Mediums In addition to the above mediums, each medium also has a counterpart "list" variant, where the original medium name @@ -1157,28 +1160,29 @@ of it's purpose.



## Social Interact ``

-The `socialInteract` tag allows a podcaster to attach the url of a "root post" of a comment thread to an episode. -This "root post" is treated as the canonical location of where the comments and discussion around this episode will -take place. This can be thought of as the "official" social media comment space for this episode. If a protocol -such as "activitypub" is used, or some other protocol that allows programmatic API access, these comments can be -directly pulled into the app, and replies can be posted back to the thread from the app itself. +The `socialInteract` tag allows a podcaster to attach the url of a "root post" of a comment thread to an episode, or +to the podcast as a whole. This "root post" is treated as the canonical location of where the comments and +discussion around the episode or podcast will take place. This can be thought of as the "official" social media +comment space for the episode or podcast. If a protocol such as "activitypub" is used, or some other protocol that +allows programmatic API access, these comments can be directly pulled into the app, and replies can be posted back +to the thread from the app itself. -If multiple `socialInteract` tags are given for an ``, the `priority` attribute is strongly recommended to -give the app an indication as to which comments to display first. +If multiple `socialInteract` tags are given for an `` or the ``, the `priority` attribute is strongly +recommended to give the app an indication as to which comments to display first. This tag can also be used as a signal to platforms and apps that the podcaster does not want public comments shown -alongside this episode. For this purpose a `protocol` value of "disabled" can be specified, with no other +alongside the episode or podcast. For this purpose a `protocol` value of "disabled" can be specified, with no other attributes or node value present. ### Parent -  `` +  `` or `` ### Count   Multiple ### Attributes -- **uri** (required) The uri/url of root post comment. - **protocol** (required) The [protocol](/socialprotocols.txt) in use for interacting with the comment root post. +- **uri** (required) The uri/url of root post comment. - **accountId** (recommended) The account id (on the commenting platform) of the account that created this root post. - **accountUrl** (optional) The public url (on the commenting platform) of the account that created this root post. - **priority** (optional) When multiple socialInteract tags are present, this integer gives order of priority. A @@ -1187,9 +1191,9 @@ attributes or node value present. Example (simple): ```xml - ``` @@ -1198,15 +1202,15 @@ Example (complex): ```xml diff --git a/socialprotocols.txt b/socialprotocols.txt index 10b35e2..874e2fc 100644 --- a/socialprotocols.txt +++ b/socialprotocols.txt @@ -1,4 +1,5 @@ disabled activitypub twitter -lightning \ No newline at end of file +lightning +bluesky \ No newline at end of file