@eyeintheskyThe Eye
@smallcirclesπ«§ socialcoding.. (funnily enough, in AT Protocol, we only have collections we add records to, all the social layer is defined by applications above, which receive all the changes to records and infer meaning from that)
@thisismissemEmelia πΈπ»
@eyeintheskyThe Eye
I just responded in the other thread about #ForgeFed way of dealing with Issues and PR's, emphasizing the actor model in the #ActivityPub specs.
Guess it depends on the nature of your extension and its desired functionality how you model things, but ForgeFed chose to have a dedicated actor, a TicketTracker, to manage the collection. Big advantage is that it become a truly encapsulated service with its own business logic, fronted by an AP actor for interoperable network communication.
If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116096782456468210 on your instance and quote it. (Note that quoting is not supported in Mastodon.)