Nostr.build isn’t recognizing nostore extension. I’m not sharing this to complain, I am sharing because I am also having issues trying to let the app recognize extensions other than Alby. I don’t understand what needs to be done.

Reply to this note

Please Login to reply.

Discussion

Did you try to refresh the page after the enablement of extension? I’ve had similar issues with other extensions besides Alby one. It is basically looking for availability of window.nost and if it is not, it will display this. 🐶🐾🫡

Hmmm…I did, I have been using nostore for as long I’ve been on nostr, I never had issues with nostore except on my app (which keeps telling me it’s a web accessibility issue), and now seeing it here.

Which device? I use it on iPhone and it works for me. Do you have the extension enabled for that specific site?🐶🐾🫡

I don’t want to bother you with this. I do believe I have it enabled. Not sure if there is anywhere else to go to refresh it.

When I open the extension setting I do see nostr.build in the list of apps as well.

Click on the “Nostore” thingy and see if account is selected. And this is not a bother to me at all, I love helping people after all 🐶🐾🤣🫂

Then refresh by pulling the window down 🐶🐾🫡

It is. I just tried zap.stream just to double check. Logged in as it always does.

And of course, for absolutely no reason at all, now it’s working. 😅🤣

I swear I didn’t do anything lol

Yeah right, didn’t do anything my ass. 🐶🐾🤣🤣🤣

Pro tip: use the Orion browser on iOS and you can install Chrome/Firefox extensions 😎

https://kagi.com/orion/

First time here about it..how private is Orion?

It's a fork of WebKit (the engine that powers Safari) but with no telemetry or other tracking. From the same dev behind Kagi search engine. They say they plan to open source it as some point. I've independently tested network logging and confirmed no outbound connections, unless you use their sync option. There's also a macOS version too.