Marco Argentieri

@maietta I do also believe Docker Swarm is low-hanging fruit here. But I guess the plan of the maintainer is to use k8s and should be in the working as...

You are right! Contributions are welcome, otherwise, need to wait until one of the next weekends to find time to work on it

> Looks like this is a duplicate of #85 It looks like to me a tiny subset, rather than a duplicate. On the specific of **only** signing a nostr event,...

> Does anyone see any areas of functional overlap that I've missed? @tiero is my understanding of what Nostr Connect is doing accurate? What you say it's correct, not much...

> I think involving Nostr relays introduces a lot of complexity and fragility Agreed . I do still think the two should be seen as "one" single thing to be...

Since the time of everyone is limited here a TL;DR of the current status @Semisol @fiatjaf @Cameri ## Changes - `Nostr Connect URI` has become `nostrconnect://?relay=&metadata=` - mandatory URL dropped...

> The website or app requesting the signature could provide its own metadata through the relay, such that the signer app would be able to show some nice metadata that...

> A URL like nostrconnect:tlvEncoded(pubkey, relay-url, method, other params), in which method could be "login" or "sign-event" or "connect", and flexible to add more stuff later. mmm but this means...

> in which the app Wait, when you say app you mean the web (most of the times) app (ie. the one that generates the ephemeral keypair) or the Signer...

> Concept ACK. > > I strongly dislike it using kind:4 even though the whole nip isn't even explicit about which kind it's using. Just that it's kind:4 encryption. >...