Dear NOSTR Developers.

Have a fucking Pow Wow. Like have a sweat box one.

Not a conference.

Get your heads together personally. Communicate and stop competing.

We need FIXES and not more features, yet.

DMs across multiple clients do not work. You can't have a DM chat here between clients at all. Last I heard it's supposed to be "one NPub for all clients".

Refreshing the cashe is pathetic too.

UX and UI devlopment seems to have stalled on some clients. Other clients depend on particular related relays that no one knows anything about to see anything. Users have to post relay lists and figure out how to talk to each other.

Participation and adoption depend on these things. The public does not know if you talk to each other. Someone have a dev party and let us know you are working on it and not just your personal preferences.

That's it.

I love a lot of you and I'm not trying to be mean. We need this or some clients are doomed.

Reply to this note

Please Login to reply.

Discussion

I been saying the same thing for a while....all we get is more fragmentation . I wish you knew how bad the server-side of nostr is

Devs dev for technology. Marketeers make products for customers. We're missing marketeers here at Nostr 😕

I offered my services as a former tech marketer..no job offers lol

do you have product ideas? I have so many pieces but no user centric product...

No. I want to see a single decent product made first

Agree.

O que uma pessoa que se exibe na internet sabe de tecnologia? Na verdade o nostr é ótimo o ruim são os clientes, que são ruim e centralizado a wallet.

E sim pelo que eu já teste os relay são padrão pra todos e podem adicionar alguns.

Unica coisa que falha é a edição de texto após envio.

I am currently fixing the 0xchat compatibility bug for receiving normal DMs so that it can be compatible with the Damus/Primal clients.

What's the nips for that problem? hasn't nip 04 everything necessary?

NIP04 DMs leak metadata; NIP17 can help prevent that.

https://github.com/nostr-protocol/nips/blob/master/17.md

If one minds their metadata to be revealed... use your own relay, that's simple.

This requires the person you DM to also trust the relay, but not everyone trusts the relays you trust.

hm, I think of the DM stuff more like an "inner circle" thing, where I talk to like minded. A group, that sets up their own relay. for the other cases, can't see harm in metadata.

DMs work across clients, there isnt anything to talk about because it's well documented how to do it. If you have a client that isn't working properly you should report in that client. You also did not specified wich clients aren't working wich doesn't help.

think she has different keys at the different clients. central Auth also has a use case 😁

You're right fam. Some of us are really working together though! I would definitely enjoy some meetups, although I think most of us are pretty sparse right now across the world, it's out of the budget for most of us to be flying all over the world to do these meetups too.

Specifically for DM's the encryption spec is changing weekly, honestly, I think it might be best for clients to just remove a DM feature until the spec gets worked out. The spec is moving WAY faster than developers can really keep up with. It needs it, but nostr development is at best, a side job without pay. Lots of peeps have families and a day job. IDK how were going to make this work, but I do know its going to take time, or lots of FOSS donations.

I do want to drop a few links to advertise some projects because we'd enjoy the collaboration.

https://github.com/vnuge/noscrypt - A C library for nostr cryptography (DM Encryption!)

https://github.com/buttercat1791/aedile-ndk - A C++ nostr devopment kit

There are a dozen other projects happening here:

https://gitworkshop.dev/repo/gitcitadel

Where's the DM spec changing?

NIP-44, NIP-59 and NIP-104 (pending). I'm sure I'm not the only one struggling to keep up

17...