For all the blossom server devs, nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fg729x4s nostr:nprofile1qqsgrz3ekhckgg6lscj5kyk2tph0enqljh5ck3wtrjguw8w9m9yxmksd5zhsj nostr:nprofil...
@Kieran thanks again for the compliance test. Your reports have been driving most of the work. nostrcheck.me is now at 90%, and once 0.7.1 ships every nostrcheck-server instance will inherit the same fixes.
I'm parking the report there on purpose. The remaining warnings come from my anti-replay system (the suite reuses the same auth event across consecutive flows, and I'd rather keep replay protection strict) and from rejecting application/octet-stream uploads when file-type sniffing can't identify the bytes. IMO both feel like the right trade-off for a public server.
I'm parking the report there on purpose. The remaining warnings come from my anti-replay system (the suite reuses the same auth event across consecutive flows, and I'd rather keep replay protection strict) and from rejecting application/octet-stream uploads when file-type sniffing can't identify the bytes. IMO both feel like the right trade-off for a public server.