Kieran

> Initially I liked this idea, but isn't this solvable by the client just querying the relay before publishing Yes and this is a way to force clients to implement...

I think its better to just include a new message response instead of lumping it into `EOSE` ```json ["CURSOR", ] ``` MUST be sent before `EOSE`, clients can resume fetching...

> I do wonder if we shouldn't just go for better addressable standards for e-tags, like: kind:pubkey:eventid and leapfrog the ntermediate solutions to this problem. Yea i was considering this...

Ok so we mostly agree that the full pubkey can be added to the `e` tags. I will add this to snort soon. > It's a breaking change, but I...

Implemented in snort https://njump.me/nevent1qqsxaxhk0r59fxn62wc2a4rv7cstnzu9wvue2sh6hhdk2exr2lafjagzyp3lucccm3v9s087z6qslpkap8schltk427zfgqgrn3g2menq5zw6qcyqqqqqqg0y9eej

Kind 1 is broadcast, so yea i guess you need another kind

It should be fixed by https://github.com/scsibug/nostr-rs-relay/pull/164

> I drafted [nip for this](https://gist.github.com/dskvr/abccd012f90f9771fc53fc173e005f33) a while back, but wasn't in the mood for nips so never published it. Someone please do this. Yep thats basically what i have...

It was only implemented in postgres, it also needs to be added to sqlite code, nothing blocking adding it for sqlite

Yes it still seems to be an issue:  Running: https://github.com/v0l/strfry/tree/nextneg ``` _start ??:? main /build/strfry/build/main.cpp:215 run(int, char**) /build/strfry/build/main.cpp:182 cmd_relay(std::vector const&) /build/strfry/src/apps/relay/cmd_relay.cpp:27 ThreadPool::join() /build/strfry/src/ThreadPool.h:57 ```