Used Primal to post an article for the first time today. Easy, straightforward rich text editor on the web app.

Yup. It’s simple also.

using desktop?

Both. Desktop and mobile

word... they recently got landscape mode for ipad up but pretty barebones to what i remember desktop being which I thought was really nice - split screen with thorough markdown capability and right half of split displays full preview of what you would see once published... @yakihonne recently said they are trying to get that going.

I am still using Longform.space and enjoying it.

I was having problems logging in with the nsec.app. It was also on mobile though. I’ll try again on my laptop.

Gotcha. I use a browser extension for signing into web apps. NIP-07 signing is still more reliable than NIP-46.

Copy. I’ll give that a go

You on Android or iOS? If Android, then Amber + @Keychat is a really powerful combination for all Nostr web apps.

iOS.

In that case, Keychat is still really good for web apps by itself, but you do have to trust it with your nsec on iOS.

Of course. Ya, I’ve held off from that for that reason.

@The Bullish ₿itcoiner, I just tried logging into Longform.space using Amber via NIP-46 connection string and it didn't work for me either. There may be something wonky with how Longform._ is handling NIP-46 signing.

Ok cool. It’s not just me.

What apps have you had success logging in with nsec.app? I haven’t had much luck with it but I’m down to try again.

I’ll try to revisit this. I was under the impression that the Nostr-login component would magically handle the bunker stuff. I haven’t had success with it in the past so I’ve stuck to NIP-07 via nos2x mostly.

Nostr-login does have some references to bunkers so maybe I need to do something differently with them.

GitHub

GitHub - nostrband/nostr-login

Contribute to nostrband/nostr-login development by creating an account on GitHub.

Copy that.

NIP-46 login is hit and miss across all Nostr apps, honestly. That's why I have also stuck with NIP-07. Folks on iOS don't have much choice, though. It's NIP-46 for everything there, or else just hand out your nsec to every app, like it's haloween candy.

I’ve noticed this also. Haha

Yeah man that’s what I’ve heard, hence why I’m reluctant to spend time on it. 😄

Is this still the case? I try to get amber (nip46) running with my PWA.. I'll check nip07 Thx 4 the hint

If you use Amber already, then I highly recommend pairing it with Keychat for all Nostr web apps. Keychat uses NIP-07 like a browser extension would, but when paired with Amber it uses NIP-55 to reach out to Amber to get the signature. Both NIP-07 and NIP-55 are very reliable, so I have never experienced an issue with signing in Keychat. Meanwhile, NIP-46 is very spotty, and it is hard to determine why. It seems like it works ok if you can initially get logged in using it. The problem is that it can take several tries before you can successfully log in. Apps that present you with a QR code to scan a connection string seem to work better than ones where you have to manually paste in the bunker string from your signer app, but that means you are using that client dev's preferred relay for passing messages back and forth between the client and the signer, rather than the relay you prefer to use. It's almost as if the client only looks for the signed connection request for a very short time, and if it doesn't see it on the relay in time then login fails and you have to try again. Highly annoying.

May I ask which signer app you use on iOS?

Yes, the biggest issue with NIP-46 is that it relies on relays for command interactions, and network connection problems can increase the number of failures.

It’s like trying to play Counter-Strike over nostr and every time you shoot you have to send a kind 999 shoot event.

Haha, By the time it responds, you’d already be headshotted 😆

Has anyone tried using a deep link with NIP-55 between PWA and Amber already? Is this possible? #asknostr

Thank u for your insights from a user's perspective. However, from my perspective, I need to create a solution that is as universal as possible, since I cannot assume that the users of my PWA have a specific app like Keychat installed. My question is therefore aimed at finding out how I can best support the different standards (NIP-07/55/46) directly in the web app to ensure broad compatibility.

Keychat is just one of many options for NIP-07 signing. Alby, nos2x, and a couple others are out there, as well. NIP-07 is the most universally adopted signing standard for all Nostr web apps. If you are building a PWA, then order of priority would probably be NIP-07, then NIP-46, and finally NIP-55 since it is Android specific.

That order of priority changes drastically if you are building a native Android app, though. Then you'd better have NIP-55 working out the gate or go home. Add NIP-46 when you can get around to it, and no need to bother with NIP-07 since the app isn't operating in a browser.

NIP-55 is not possible as it is not a native app

Replying to you now from snort.social in Brave mobile browser using NIP-55 signing. No NIP-46 bunker string exchanged whatsoever.

That is URI based and not very practical compared to NSC

Ah, yes. It does seem quite finicky. And now I notice that it seems to be communicating with Amber via my phone's clipboard. Not ideal.

Nsec.app