Alex Gleason

This should still use a replaceable event for votes. That was never addressed. Say something that actually makes sense about it please, that's all I ask.

@abhay-raizada You would simply query votes with the "until" filter, and you would HAVE to be querying from a trusted relay that enforces the created_at timestamp to be within a...

What you're describing is a buggy client behavior that does not benefit the person who voted in the poll. It would potentially allow a user to rescind their vote. People...

Okay so explain why people can't do that with kind 5 events.

If you have to build a custom relay for your implementation to work, then your argument against replaceable events is moot. Because no matter what you have to build a...

Have you implemented a relay? I can't even make tag queries fast as they are.

Postgres has a `@>` operator that is almost identical in functionality to Nostr filters, except it uses AND instead of OR for array values. If anything supporting OR was actually...

@arthurfranca I want to get these kinds in the nips sometime this decade, and I think there's a better chance when it's kept simple. We can always expand this document...

I decided to strip it down because of https://github.com/nostr-protocol/nips/pull/1264 > They should be fully implemented in at least two clients and one relay -- when applicable. I have not actually...

The idea proposed here is simple. I would compare it to NIP-78. It is an emergent property of parameterized replaceable events. It seems obvious to me to have a generic...