Tomas Bezouska

How would current relay implementations signal supporting this if it becomes part of 01? I think making this a separate NIP is better, with NIP 11 signaling. Much like NIP...

My question was more about the transition period after merging. The current relay implementations wouldn't magically start supporting this (let alone running instances), you would need a mechanism to check...

> The most important downside of feature signaling is that it makes changing things a much easier process than currently. But currently feature signaling is done by adding new NIPs,...

FYI I have this implemented in [netstr](https://github.com/bezysoftware/netstr/) relay and deployed to a dev instance: `wss://relay-dev.netstr.io` Feel free to play with it (e.g. according to meme sample: ```["REQ", "test", { "&t":...

I'm personally happy with this NIP and deployed it to production: https://relay.netstr.io/

Thanks, at first glance that does look like everything I'm looking for. So effectively if NIP-87 is merged it would supercede NIP-29? Are there some more side discussions taking place...

I must say this is bananas. Deploying firebase with `--token` was easy-peasy, but with the service account it requires a crazy amount of setup. Can't this be done directly in...

Should relays also not allow AUTH for locked user? Ideally relays should only serve DMs to authed clients who are part of the conversation, but when a user is locked...

This looks reasonable, but I'm curious about client side implementation. Since relays can send this at any point, would clients have to "guess" some default values before receiving anything? When...

> > I would consider making it mandatory for relays to send it right when a client connects. > > We can add that for those who opt to implement...