I think it's better to use DMs clients for DMs, they know how to work with DMs.

I would trust a DMs client with my DMs more than a client that focus on something else.

I agree, @AilliA is awesome and helpful :chibimonerochan_AilliA:

Uncle Turtle

I don't like the client being in control of my nsec. Not because I don't trust the developers only, also because they'd be able to encrypt and decrypt anything they want. They'll make stupid events, like that one that let everyone know you were browsing Nostr for no reason.

Okay, it took me a couple of seconds to recognize you. There is someone I'm following who I really don't know why I did, I think they just changed their profile picture so now I don't know who they are anymore :(

not ngit only, there is n34.dev, gitplaza.net, nak, gittr.space and Shakespeare. Check https://gitgrasp.com/

it works good for decentralized git issues and patches also. Instead of using email because it's federated, the patch/issue is only stored in the email server. Nostr is decentralized, the patch/issue can be stored in 10+ relays.

oh, I mean the client you reply from right now, not your awesome app one :)

just asking, what client you are using? it doesn't respect my READ relays, it should sent your reply to my note to my READ/inbox relays so I can actually read it.

Can you let me know the name so I can report this bug?

nprofile is good because it embeds the relays, so we don't have to share the same relay to see my notes. The relays in my nprofile likely have my relays list (NIP-65) and my notes, so you can just ask those relays for my notes.

check this: https://persona.nstr.app/nprofile1qqsqqqqqq9g9uljgjfcyd6dm4fegk8em2yfz0c3qp3tc6mntkrrhawgpzfmhxue69uhkummnw3ezudrjwvhxumq3dg0ly

It say: "Analysis failed Could not resolve identifier to a pubkey". It work tho when I entered my npub.

nprofile doesn’t seem to work for me