it looks like this was a request sent by snort.social:

["REQ","65eab48c-63d5-49f3-8018-93ccc0f16934",{"authors":["8ccfa77bf43e3afd4076aa91d5c0e7c2dae9d279aeee72666aec02aac317447a"],"kinds":[10003,3,10015,10000,10002,10005,10001]},{"authors":["8ccfa77bf43e3afd4076aa91d5c0e7c2dae9d279aeee72666aec02aac317447a"],"kinds":[30078],"#d":["snort"]}]

event 30078 is application specific data

#snort developers, you should be authing NIP-42 to access this kind of event... i have categorised events that should not be given out to everyone, there is 4:

kind.EncryptedDirectMessage,

kind.GiftWrap,

kind.GiftWrapWithKind4,

kind.ApplicationSpecificData,

4, 1059, 1060 (h/t hodlbod) and 30078 are somewhat sensitive kinds of data and really should not be returned from a relay without the querant proving they are 8ccfa77bf43e3afd4076aa91d5c0e7c2dae9d279aeee72666aec02aac317447a in this case

good that there is starting to be a convention to label the client in the request tags now, or at least, i suppose that the Application Specific Data is for Snort that is not the right way to go about it...