I tried to use nip-17 crash reports but the log files got bigger than 64kb and the relays rejected them.

Reply to this note

Please Login to reply.

Discussion

Doesnt seem like a good idea to store large payloads like this on nostr

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s whats the max event size you would feel comfortable with for the scenario all crash data is submitted in JSON? 0.64 kb? 6.4kb? Just under 64kb?

What advantage does this have over plain old tls?

A nostr only approach means that you dont have run email, run AWS, or some other thing. Max file size limitation aside it seems a natural fit for nostr

I liked the idea of nostr only for it, end to end encrypted, on protocol, but for divine it didn't work because our log files are big. And we could have done it with some way to connect to using blossom or something for log sharing, but we want those logs to be private.... I gave up and added zendesk support to divine, but i don't love it.

nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 whats the max file size you experienced, and you would prescribe for a “crash report NIP”. E.g. 70kb, 1MB, 10MB, 100MB ?