As a resource host (or an annotation creator?), I am concerned about third-parties eavesdropping on notifications about my resources

[blalbrit]

Jud Harward put forward a use-case as follows:

• Institution A declines to accept annotations from User B on Resource C
• 3rd-Party D feels this is an error and somehow accepts in their environment User B's annotations on Resource C

Conversation pointed to what expectations institutions and users might, or might not, have in this situation when discussing public annotations on public resources.

Perhaps not in-scope for the mechanism of notification, but a valid use-case in this space that could lead to further discussion of trust-systems for distributed annotation content in various contexts

[azaroth42]

If you don't want people to talk about your content, take it offline. There is absolutely nothing we can do to prevent third parties using their own systems to reference online resources. Propose out of scope and close.