First, one wants a mechanism to subscribe / unsubscribe to a conversation. Having an actor manage it, is a better mechanism than turning the conversation object into a quasi actor.
I have misgivings, because:
- The point of using acct-uris is to be more human readable. If one needs to generate them automatically for each thread, this will degrade quickly. IMO it would be better to drop the requirement on webfinger.
- Generating an observer for each object will lead to a lot of generated public / private keys. I'm not a fan. It would be good to address this somehow. Not sure what the ideal solution would be.