Conversation

Notices

1. infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 20-Apr-2024 20:14:20 JST infinite love ⴳ

   i will not rest until fedi devs start using as:context properly. this is my single-issue. /hj

   • silverpill (silverpill@mitra.social)'s status on Saturday, 20-Apr-2024 20:14:18 JST silverpill

     in reply to

     @trwnh Conversations in streams now have attributedTo property (example: https://fediversity.site/conversation/7342c8d7-6ac2-4128-8168-6cbd0dc9a37c). Does it make streams a complete FEP-7888 implementation?

   • infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 20-Apr-2024 20:14:19 JST infinite love ⴳ

     in reply to

     real talk tho, if you want actually existing honest-to-god threads and threading and conversations... there's a property for that!

   • infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 20-Apr-2024 20:14:19 JST infinite love ⴳ

     in reply to

     pleroma and streams are like 80-90% of the way there, the only missing bit is signaling who owns the context via `attributedTo`

   • infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 20-Apr-2024 22:36:24 JST infinite love ⴳ

     in reply to

     • silverpill

     @silverpill reading through the "conversation containers" doc at https://codeberg.org/streams/streams/src/branch/release/doc/develop/en/Containers.mc i have the following comments

     - the notion of a "top level post" is kinda redundant with the context, and its definition as "without inReplyTo" can be problematic if your "top-level post" is actually a reply to something. imagine an article inReplyTo something, but with its own context

     - "the conversation owner (target->attributedTo)" seems to confirm not 2.2...

   • infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 20-Apr-2024 22:36:25 JST infinite love ⴳ

     in reply to

     • silverpill

     @silverpill i guess it does? it depends on whether comments are sent to context.attributedTo or not.

   • infinite love ⴳ (trwnh@mastodon.social)'s status on Saturday, 20-Apr-2024 22:36:25 JST infinite love ⴳ

     in reply to

     • silverpill

     @silverpill in any case if i had to describe "compliance levels" then it would be something like:

     0: does not use context (mastodon)
     1: uses non-dereferenceable context (pleroma)
     2.1: context resolves to a collection representing the conversation (streams?)
     2.2: context has attributedTo and participating objects are sent to this actor

     so all it would take for streams to be 2.2 compliant is for their "conversation containers" to be sent to `context.attributedTo` instead of `target.attributedTo`

   • silverpill (silverpill@mitra.social)'s status on Saturday, 20-Apr-2024 22:36:53 JST silverpill

     in reply to

     @trwnh If I understand correctly, target.id points to the context collection, and therefore context.attributedTo and target.attributedTo are the same actor.

     @mikedev could you confirm?