Nostr Web Client

I agree, but fixing this is pretty actionable. njump screwed up by not sending him back to flotilla, and he managed to recover with nsec.app. Surprising it worked at all, especially since I handicapped myself by not accepting raw private keys.

daniele 5mo ago

The problem here is that the user visited njump.me to learn more about Nostr and then pressed "Join Nostr" from this page; this resets the calling app refer, and so it got the standard registration path.

Currently Nstart uses session storage to be sure the key is wiped ASAP after the workflow finishes, so it's tab specific. I could evaluate to migrate to localstorage only these additional settings, but then the user could be trapped in some old workflow and I should offer him the possibility to reset the procedure.

Probably the easiest solution is to remove the external link when Nstart is used by a third app, to create a direct path without distraction. What do you think?

Reply to this note

Please Login to reply.

Discussion

daniele 5mo ago

> remove the external link when Nstart is used by a third app

This already happens with the modal integration! But it's not present in the redirect one. Why don't you use the modal, I think it is a superior UX, it helps a lot keeping the context.

daniele 5mo ago

In the meantime I removed the link also for the redirect integration.

hodlbod 5mo ago

> Currently Nstart uses session storage to be sure the key is wiped ASAP after the workflow finishes, so it's tab specific

That makes sense, probably not worth confusing the user by persisting stuff, although maybe you could pass it from page to page. Removing the link works pretty well too, although it's clearly useful since he clicked it. Maybe you could open it in a new window? Anyhow, I'll take another look at the popup workflow.

hodlbod 5mo ago

One request, could you enable CORS on the popup script? I'm trying to load it via dynamic import and getting `Access to script at 'https://nstart.me/modal.js' from origin 'http://localhost:1847' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`

fiatjaf 5mo ago

Would be great if the FROST bunker worked too.

hodlbod 5mo ago

A couple other things:

- The font size is quite large when loaded in a popup, causing overflow/scrolling issues. Similarly, some screens show a big white section on the bottom if they're too short. Maybe adjust the font size if it's in a popup? Or use percents to control height? Screenshots below.

- `asf` isn't being applied in the popup version

daniele 5mo ago

The white block is weird!

I will take a look asap.

daniele 5mo ago

"Large" fonts are a design choice, I like them better and I think they are more accessibile.

Reducing the font size it's not the solution for the scrolling, it's inevitable with this kind of design (see the initial form); of course minimizing it would be preferable. I'm thinking about a solution, but offering a setting for the font size is quite hard with Tailwind.

Instead I cannot reproduce the white block. Jumble works just fine (with the npm):

Paulo 5mo ago

Tailwind uses rem, so if you want to globally affect the font size, that should be possible just by redefining the font-size of your html element.

daniele 5mo ago

Thanks for the advice, I will check that.

daniele 5mo ago

> - `asf` isn't being applied in the popup version

Fixed, use v2.1.0

daniele 5mo ago

Maybe the npm is a better approach?

https://www.npmjs.com/package/nstart-modal

hodlbod 5mo ago

Ah, I didn't realize that was an option

daniele 5mo ago

> t's clearly useful since he clicked it.

I think the calling application is responsible for explaining Nostr in relation to its nature, evaluating how far pushing it, and should do so before the user starts the sign up workflow. Having an outbound link in the first step (in this integration context) is dangerous for the funneling.