> 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.
Discussion
In the meantime I removed the link also for the redirect integration.
> 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.
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.`
Would be great if the FROST bunker worked too.
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
The white block is weird!
I will take a look asap.
"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):
> - `asf` isn't being applied in the popup version
Fixed, use v2.1.0
Maybe the npm is a better approach?
Ah, I didn't realize that was an option
> 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.