Michael Dilger

Just FYI from my reading, the following NIPs put a requirement on relays: 1, 4, 9, 11, 26, 29, 40, 42, 45, 50, 59, 65, 94, 96 The following NIPs...

> I think what's more interesting than what NIPs are supported is what types the relay accepts. I agree. But NIPs do go beyond just types. Deletion, for example. I...

+1. Simple enough to get implemented everywhere quickly. Implemented in chorus here: https://github.com/mikedilger/chorus/commit/1e2187b86c7a4cd8b33672cf7cf6f777f0baf526

I like the idea behind using a pubkey and a relay list to find events, rather than a relay hint. But I have a couple of reservations. Maybe they are...

> 'secret' passed to 'connect' is single-use short-lived token, which only works on first connect (if it hasn't expired yet), so leaking it is okey-ish. If it leaks, it's very...

Ok I just went back and read #523 and this issue again, and I have a few more things to say: First, I have not encountered the need to do...

> > it just pushes that filter operation to the relay to save on network bandwidth > > Interesting take. A caveat is it may mess with "limit" filter, like...

I am not against allowing clients to initiate AUTH. But I don't see the benefit when clients and relays are well-behaved. AUTH is for the benefit of the relay, not...

I want a delete_prefix, but as there is none I'm trying to use delete_range() but have encountered this issue. This is on 0.20.0-alpha6. Here's a snippet: ````rust // This is...

I'm using (and it works): ``` let range = ( Bound::Included(&*start_prefix), Bound::Excluded(&*end_prefix) ); ```