mleku ✝Ⓐ☯︎ @mleku - 5d
haha nip-47 was obviously written by #golang programmers check out the protocol message spec here and hypothetically imagine that it's supposed to be valid JSON (ignore the comments in the discussion for a moment, although they are // comments also what's wrong with them? commas on end of every line in Go you can only skip a comma at the end of a list if the closing brace/parethesis comes before the end of line technically you almost always minify json, making it one line per message anyway, no linebreaks even where valid, so the same syntax would apply but it's not readable but, funny... i should maek a PR to make the JSON actually correct, put it inside markdown tables so the comments can be lined up but not part of what you would copy
https://github.com/nostr-protocol/nips/blob/master/47.md
haha, yeah, there's no comments in json, but this is marked "jsonc" which is some thing that github does, my typora editor doesn't understand the format it just sees it as formatted text with indents jut the way that the messages al have got terminal commas in object lists is funny
oh, look at thet logo on this page defining this jsonc (and yes microsoft VSC uses it lolololol) https://github.com/muhammadmuzzammil1998/jsonc
also, i'm not touching it... there is no easy way in github flavored markdown to actually have proper json with annotations that aren't part of selecting the text
