Conversation

Notices

1. Embed this notice
   Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 05-Oct-2024 03:31:39 JST Evan Prodromou

   • Darius Kazemi

   @julian @darius I started a new FEP to define a vocabulary specifically for threads.

   https://codeberg.org/fediverse/fep/pulls/406

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 05-Oct-2024 04:45:21 JST Evan Prodromou

     in reply to

     • Darius Kazemi
     • Erin 💽✨

     @erincandescent @julian @darius it's covered in the doc, which is free to read!

   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Saturday, 05-Oct-2024 04:45:23 JST Erin 💽✨

     in reply to

     • Darius Kazemi

     @evan @julian @darius How does the “thread” property differ from the “context” property which basically every implementer is already using and has been doing so for 6+ years?

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 05-Oct-2024 04:47:59 JST Evan Prodromou

     in reply to

     • Darius Kazemi
     • Erin 💽✨

     @erincandescent @julian @darius you can also file an issue here:

     https://codeberg.org/evanp/fep/issues

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 05-Oct-2024 04:58:02 JST Evan Prodromou

     in reply to

     • Darius Kazemi
     • Erin 💽✨

     @erincandescent @julian @darius great. You can definitely use both.

     `context` is fine for any kind of grouping of objects, as is noted in AV.

     https://www.w3.org/TR/activitystreams-vocabulary/#dfn-context

     If you want to specifically talk about a conversation tree, a more specific property is better.

   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Saturday, 05-Oct-2024 04:58:04 JST Erin 💽✨

     in reply to

     • Darius Kazemi

     @evan @julian @darius That doesn’t really cover the why other than “context is vaguely defined” (maybe, but its’ been used in this exact way for… 7 years now? And is being used in this way by multiple interoperating implementations)

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 05-Oct-2024 05:41:42 JST infinite love ⴳ

     in reply to

     • Darius Kazemi
     • Erin 💽✨

     @evan @erincandescent @julian @darius I can leave this as a comment on the PR or the issue tracker, but my position is that "conversation tree" is entirely the wrong way to look at it, because a "conversation" and a "reply tree" are not the same thing. You can fork the conversation, you can reply to something in a different conversation, and you can have your post moved to a different conversation. I could define a property for it, but my intent was to gracefully degrade to using it for grouping

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 05-Oct-2024 05:41:42 JST Evan Prodromou

     in reply to

     @trwnh @erincandescent @julian @darius great, definitely comment.

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Saturday, 05-Oct-2024 05:43:07 JST silverpill

     in reply to

     • Darius Kazemi

     @evan @darius @julian Merged: https://codeberg.org/fediverse/fep/src/branch/main/fep/76ea/fep-76ea.md

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 05-Oct-2024 05:47:50 JST Evan Prodromou

     in reply to

     • Darius Kazemi
     • silverpill

     @silverpill @darius @julian thank you!

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Saturday, 05-Oct-2024 09:03:46 JST Evan Prodromou

     in reply to

     • infinite love ⴳ
     • Darius Kazemi
     • Erin 💽✨

     @erincandescent @julian @darius @trwnh it was offered as an option and I vastly prefer being able to resolve question by question rather than a long conversation thread that doesn't ever finish.

   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Saturday, 05-Oct-2024 09:03:48 JST Erin 💽✨

     in reply to

     • infinite love ⴳ
     • Darius Kazemi
     • Erin 💽✨

     @trwnh @darius @evan @julian (I have converted these thoughts and a few more into an issue. It’s a bit strange to see discussion for a FEP moved to an issue tracker - for pretty much all of them historically a SocialHub thread has been made, and that has worked quite well)

   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Saturday, 05-Oct-2024 09:03:49 JST Erin 💽✨

     in reply to

     • infinite love ⴳ
     • Darius Kazemi

     @trwnh @darius @julian @evan I will be the first to admit that I’m not a massive fan of the “context” property name but given it is baked into likely billions of posts at this point I mostly feel it’s the lesser of two evils. If this were an misuse of the property that was blocking some preferable use (e.g. Mastodon’s abuse of the “summary” property for CWs) then I would agree that it would be worth dealing with the pain, but in this case I feel pretty much any use of the property would be better off picking a more specific name so we may as well grandfather the use of “context” for “conversational context” (which is a valid use, per the definition)

     Truthfully the Original Sin here is the inclusion of such vaguely defined terms in the original AS2 specification

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 05-Oct-2024 09:03:50 JST infinite love ⴳ

     in reply to

     • Darius Kazemi
     • Erin 💽✨

     @darius @erincandescent @julian @evan well, the json-ld keyword has an @ in front of it for a reason: https://www.w3.org/TR/json-ld11/#syntax-tokens-and-keywords

     id and type got aliased but they're really supposed to be @\id and @\type: https://github.com/w3c/activitystreams/issues/232

     other point of confusion re: @\context vs context was overruled: https://github.com/w3c/activitystreams/issues/238

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 05-Oct-2024 09:03:50 JST infinite love ⴳ

     in reply to

     • Darius Kazemi
     • Erin 💽✨

     @darius @erincandescent @julian @evan there was probably a time when `context` could've gotten renamed in the same way that `scope` was renamed to `audience`, but we're about 10 years too late on that discussion

   • Embed this notice
     Darius Kazemi (darius@friend.camp)'s status on Saturday, 05-Oct-2024 09:03:51 JST Darius Kazemi

     in reply to

     • Erin 💽✨

     @erincandescent @julian @evan it does mention the @context name collision which is imo a real point of confusion