Nostr Web Client

If thinking in the nostr email model, this is like saying “why doesn’t my client autocomplete the address when I type bob@“.

Well why would it? What bob are we talking about? What email server is he on?”

A big part of what we’ve been masking in our clients is feigning decentralization via a centralized blob of relays. Thats what damus has been doing to make it friendly to users. But its a lie. There is no one global feed. If we want nostr to take off we need to change our clients and ux to stop pretending there is a constant set of relays that eveyone is on.

Damus is the worst offender here, i will start putting more effort into this front. nostr:note10d2l6p28q2q3p4jrv6xl4cp2wgq34wjmr34qsfjgagjy7l5qqtrshvxnj0

Reply to this note

Please Login to reply.

Discussion

utxo the webmaster 🧑‍💻 2y ago

Nuke the damus relay. Force our hands

jb55 2y ago

Lemme improve the app a bit first 😆

utxo the webmaster 🧑‍💻 2y ago

🫡🫡📱

Bill Cypher 2y ago

Email does do this, if the recipient is in your contacts. #nostr at least on amethyst, usually does not even if they are in your follows.

daniele 2y ago

Yeah, this is a stage problem I've never figured out... we are talking about few hundreds elements. When it happens I usually open my followed list to refresh the cached contacts.

/cc nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

hsoc 2y ago

Very enlightening note. Thank you

daniele 2y ago

Interesting topic!

> What bob are we talking about?

I would start from the user's curated contact list. Then probably give suggestions using the relationships graph to Nth degree. Finally offer a full search with some filter options (ex. Last seen on X relay).

ben 2y ago

please and thank you. I’ve been hung up on the idea of community/content-centric relays for a while and strongly believe this is the way.

excited to see some movement in the space, especially from the flagship ios client.

Welliv 2y ago

Hey nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s I find your exploration of email design on Nostr intriguing, especially the idea of using relays as mailing lists. It's a step towards decentralization. By the way, I DM'd you with thoughts on how Nostr can revolutionize business, like improving sign-ins. Let's keep pondering these ideas in the social context too!

jb55 2y ago

Hmm sorry my dms are a mess as i have no good tools to filter or sort them, so im relying on email for now jb55@jb55.com until i finish my nostr email client

🇦🇷🧡 Marcel 🟠⚡️ #Bitcoin is Hope 🙏 2y ago

So now your email will be a mess 😊

jb55 2y ago

I can at least archive stuff there and have different folders 😅

damus dms suck atm

🇦🇷🧡 Marcel 🟠⚡️ #Bitcoin is Hope 🙏 2y ago

you are right 😊

Vanessa 2y ago

You have not responded to my email 😂

Derek Ross 2y ago

🤣

Derek Ross 2y ago

DMs sucks all around on Nostr. I am excited to see what we can do with SimpleX.

Carman 2y ago

Bob isn't tied to a relay though. You can use easy metrics like looking through profiles cached. Most likely the person being tagged is someone the user recently viewed.

jb55 2y ago

My point is that we are pretending when you @ someone they will get it based on the relays you have configured. What an @ should mean in a social context is “make sure this note gets delivered to some well-known set of public-writable relays that the user has configured”. A big problem right now is that relays are hidden and there is no well-defined meaning of how a note should be delivered when you address someone.

ben 2y ago

doesnt nip-05 have a section for defining a user’s relays?

jb55 2y ago

Yes but clients cant set that up automatically for a user (yet?)

ben 2y ago

seems like a good fit for an onboarding workflow.

just need an index of communities(relays) and could surface these to the user for selection (+payment if required).

andre 2y ago

Yes! NPROFILES w home relays

leo 2y ago

I thought nip65 does exactly that

jb55 2y ago

Yes I guess I didn’t appreciate how good it is until now. I thought it was just a relay list replacement, but it looks like it goes into specifics on how clients should read events from certain people. Will definitely implement this. In other words nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c is bad at marketing his nip or i was too busy to understand it until now.

idsera 2y ago

I saw a new version of Camelus. So the development is still active, right?

n 2y ago

💯

Dark Fusion 2y ago

Appreciate the work you do! 🔥

andre 2y ago

🫡🫡🫡

Komi_Hartman 2y ago

Thank you for this crucial point consulted & which deserves to be designed!

Everything should be based on the 'NIP-05'... A single key to have access to all services & almost..

Thus, Nostr & Damus will prevail over traditional services.🏴‍☠️

Beemo 2y ago 💬 5

The limited reachability was the first thing that bothered me when I first started playing with Nostr.

Since january, I'm conducting a research paper on implementing Gossip and other dissemination algorithms on relays. It really brings me joy and irritates me at the same time 🤣😁....

I feel like everybody's starting to finally aknowledge that there's an issue and what I've been laughed at in 2022 is finally a great concern now

nostr:npub1nftkhktqglvcsj5n4wetkpzxpy4e5x78wwj9y9p70ar9u5u8wh6qsxmzqs nostr:npub1dy7zsvk7jwd547xvmpptzlc9muhd64g7txvf60zwlxjyj4aj78as6hljz5 nostr:npub16zlc26xk7qjlfa4dquqvvs3s5zl2yw989lprj63nfw4g7ndnuahslcevpc nostr:npub1x2kakfryyzw7gfh9n8d53w7669ck0ly9k2ayj0l9h7wfa829n7dqyp6jgd nostr:note1akmlmnhjc6u98vlsc580cf088e725audqnsxuqn2s6ryh5p4n0assw6ju8