Conversation

Notices

1. Embed this notice
   Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 09:34:38 JST Evan Prodromou

   • Hrefna (DHC)

   @hrefna I definitely get what you're saying. Using mixin types as the way to define different behaviours is a good strategy.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 07:13:55 JST Evan Prodromou

     • Hrefna (DHC)

     @hrefna anything you can follow or which can follow others can be an actor. That's a feature, not a bug.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 07:15:56 JST Evan Prodromou

     in reply to

     • Hrefna (DHC)

     @hrefna oh, and we should have _definitely_ used a different word for "actor types" in AS2 (not the only types that can be `actor` in an activity, btw) and `Actor` objects in AP. It's confusing. The `actor` of an activity doesn't have to be an AP `Actor`, nor does either of them have to have an AS2 "actor type".

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 07:18:22 JST Evan Prodromou

     in reply to

     • Hrefna (DHC)

     @hrefna Mastodon, for example, won't let you follow anything that doesn't have an "actor type", which is a bug.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 08:06:34 JST Evan Prodromou

     • Hrefna (DHC)

     @hrefna the inbox! If you can send it a 'Follow' activity, it is followable. It is a feature because there are lots of followable things, which makes the world more interesting.

     I'm going to flip your question: can you imagine any ways that it might be interesting to follow a Note or an Article?

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 09:22:18 JST Evan Prodromou

     • Hrefna (DHC)

     @hrefna I think the point is that we can build interesting applications on top of AP. I think FEPs or other light standards can be used for creating them.

     In the case of content objects as actors, best proposal I've seen is that the object shares all the activities that affect its history - creates, updates, replies, likes.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 09:33:10 JST Evan Prodromou

     • Hrefna (DHC)

     @hrefna so, it sounds like you think we should have used multi-typing for actors, or maybe a single Actor root class.

     But we didn't. We went with duck typing instead, which seems to work fine. Either of those other ideas would have worked, but this works, too.

     If you want to know if you can send an activity to an object's inbox, you check to see if it has an `inbox`. If you want to read its outbox, you check that it has an `outbox`.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Monday, 04-Dec-2023 09:38:47 JST Evan Prodromou

     in reply to

     • Hrefna (DHC)

     @hrefna I also want to say that I am *really* appreciating your implementation notes as you are going along. It's really hard seeing you struggle, and there are some painfully valid criticisms of the architecture and approach. I hope we can make the experience better for future devs.