hodlbod

Yeah, I'll look into it

Nostrability is definitely helpful, I've seen multiple concrete issues resolved thanks to your efforts. I do feel like something is missing though, maybe just developer buy-in. Even reporting compatibility issues...

Coracle is behaving as expected, sciencedirect.com's robots.txt is blocking my link preview proxy.

> Is allowing the link to open in third party browser the only way? Yes, or ignoring the site's robots.txt. > Relatedly, what is your philosophy and decision process on...

Coracle both sends and accepts e and a tags.

New types (like choose your own adventure, but not long-form) should use NIP 22 comments rather than kind 1s. Clients that request kind 1s should support both `e` and `a`...

Yep, this is a very old issue. I happen to be working on this right now, so it should be resolved soon.

Normally, it's best practice to create a new kind for each new data type. What you're doing (and what nip 78 is doing) is creating a namespace-within-a-namespace. Better to just...

By convention (and implementation) kind 3xxxx are always parameterized replaceable events, you should choose something in the range 100-9999 for non-replaceables.

This is basically the same as `t`, NIP 29 `unmanaged` groups (but without all the other NIP 29 cruft confusing the issue), and reminds me a lot of NIP 28,...