Conversation

Notices

1. Embed this notice
   infinite love ⴳ (trwnh@mastodon.social)'s status on Monday, 03-Feb-2025 19:17:55 JST infinite love ⴳ

   in reply to

   • Matthias Pfefferle

   @julian @pfefferle in terms of what kind of Object to use other than a Collection, i would say maybe don't use a Note because this is often not semantically correct. the current WIP idea is to define a `Conversation` entity that has something like a `posts` property. the thinking is that a conversation *has* a collection of posts, not that it *is* a collection of posts. this is the topic of a separate FEP though. nodeBB briefly went ahead and used Conversation before rolling it back as too early

   • Embed this notice
     Matthias Pfefferle (pfefferle@mastodon.social)'s status on Monday, 03-Feb-2025 19:17:55 JST Matthias Pfefferle

     in reply to

     @trwnh @julian thanks a lot for the guidance!

     I think even if an object is possible, I start with the collection because of interoperability reasons.

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Monday, 03-Feb-2025 19:17:56 JST infinite love ⴳ

     • Matthias Pfefferle

     @julian @pfefferle there's a few options on what it would ideally be, but it *can* be any Object

     1) group by `id`
     2) possibly moderated by `attributedTo`
     3) should have some collection associated with it somehow, just a flat list of everything included

     the jury's out on how best to do #3 because the goal is to eventually be able to Follow a conversation. but https://github.com/w3c/activitypub/issues/486 makes it problematic to try to Follow a Collection directly...