Oddbean

How might we improve njump mobile view for folk who have no idea what nostr is? Is njump specifically for folk who know what nostr is? ~1/4 - 1/3 in purple highlight boxes is gibberish to normies Normie friendly note and profile info take ~1/4 - 1/3 space What is nostr appears as a footnote. Should this be explained? Open in your native client is clearly the main CTA. Many options follow - how does someone new to nostr know which option(s) to tap? Show more details is there to scare normies even further with more normie gibberish😅 cc @Karnage @elidy @dtonon @fiatjaf https://image.nostr.build/0b0f4b8e2fd2c72e33422f4c7a5ff2e8fb26eced57532a36dd88829ad6c0c77a.jpg

I don't know for a fact, but based on the usability test videos I have been watching, I think no normal person will understand njump. And I am not trying to trash on anyone or anything, it's just me coming to realization of how people see things. Of course, if they encounter it a few times, they may ask around or figure it out, and then it may make sense. But for a new experience I have a feeling it'll leave people totally clueless. I have designed what I believe to be a better experience (except for the issues that were pointed out regarding hover / mobile interaction). The gist of it is opening in one client and giving options for others, but tucked away behind a click. The theory is that seeing too many links is overwhelming and people won't understand what they're looking at. Of course, existing nostr users may be fine and it may actually work great for them, in which case they don't need explainers.

Njump target is *not* specifically people who do not know about Nostr. The main goal is to create a link between the web and Nostr, with several outcomes (e.g. be client neutral, permit a fast sharing without JS and relay glitches, improve indexing of content on current search engines, etc.). Of course, this means it will be used potentially by people that don't know anything about Nostr, and I agree that some elements can be initially confusing. Here are my thoughts about the "gibberish": nevent1qqsqqqqq2y9zslqg9rzs0q52u3mrfetwf52tnnpur0zrrg99h4vp7uspzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpzpmhxue69uhk2tnwdaejumr0dshszrnhwden5te0dehhxtnvdakz7e5huzf Finally, we are cooking up an update that will precisely address the newcomers, specifically the "what is nostr". Thanks for sharing!

Other note: Njump is great (IMHO) for sharing comprehensive and meaningful content that a user can appreciate, not an isolated response that requires discovering the context. If the content is valid, attention will focus first there, and all the gibberish will be an additional possibility of learning, later. Instead, if you want to point a Nostr newcomers to a whole discussion as valuable content, it is probably not the right tool for someone because it doesn't show the parent and replies. We do this purposefully because the main goal is not to create another full-featured client and capture the user, but to encourage the user to discover other Nostr clients and interact with them. And yes, discovering requires being a little adventurous and sometimes facing the unknown :) However, Njump remembers the most used client and moves it to the top, so after the same user tried a couple of clients and settled on one, the next time he will have a more direct CTA, without losing the possibility to explore the always updated clients list.

njump is about connecting people through conversation. If you can see the entire post in the page, what would encourage to jump into nostr? Wanting to comment. The focus should be on the message, not on all the technical details. It should display replies, without any extra clicks. Since spam might be a problem on replies, perhaps they could be filtered to replies in the network of the person posting. The button should be about commenting. Perhaps: “Jump into nostr to comment” or a simpler version: “Comment on nostr”

My two sats: 1) No strings of characters on high visibility pages. If you reaaally must, replace with QR codes (with strings below). 2) No acronyms or abbreviations. Reduce language like npub, nsec, json, njumps …etc. I believe we can brand/name these things. 3) Simplify functionality. If someone asks me to share my profile, my brain should immediately connect to one element. Whether that is my name, alias, address, or public key. Having four identifies is very confusing, especially since searching for them doesn’t always yield the expected result. And preferably, not use public key as it’s very scary.