Conversation

Notices

1. silverpill (silverpill@mitra.social)'s status on Sunday, 08-Sep-2024 20:05:37 JST silverpill

   • Emelia 👸🏻
   • infinite love ⴳ

   @mikedev @trwnh @thisismissem @julian As far as I can tell, Containers not simply co-exist with FEP-7888 but fully satisfy its requirements.

   • infinite love ⴳ (trwnh@mastodon.social)'s status on Sunday, 08-Sep-2024 21:14:54 JST infinite love ⴳ

     in reply to

     • Emelia 👸🏻

     @silverpill @thisismissem @mikedev @julian yeah, the only point of difference i recall when reading about comversation containers was a bit about using target.attributedTo (FEP-400e) instead, which i would personally discourage in favor of context.attributedTo so that there is only one source of truth. aside from that, FEP-7888 certainly covers this implementation in at least spirit if not fully in letter -- the core of it is as simple as "please use `context` for tracking the conversation".

   • silverpill (silverpill@mitra.social)'s status on Sunday, 08-Sep-2024 21:14:54 JST silverpill

     in reply to

     • Emelia 👸🏻
     • infinite love ⴳ

     @trwnh @thisismissem @mikedev @julian

     >In a constrained conversation, the target->id and the context are identical.

     So target.attributedTo and context.attributedTo would be identical too