event kinds 30066 and 30166 seem like they can be self-published automatically by relays and contain useful data to clients implementing and publishing reports on this protocol feature
not high priority but would be good to implement this feature by end of MS3
requires the creation of a relay identity which represents automated reports and potentially later on could be part of a chat based interface
it is in draft still but NIP-66, relay metadata and monitoring is relevant to the ACL system:
https://github.com/dskvr/nips/blob/this-is-the-last-time/66.md
event kinds 30066 and 30166 seem like they can be self-published automatically by relays and contain useful data to clients implementing and publishing reports on this protocol feature
not high priority but would be good to implement this feature by end of MS3
requires the creation of a relay identity which represents automated reports and potentially later on could be part of a chat based interface