Oddbean new post about | logout
 📢 🚨 URGENT 🚨

Has a nostr iOS developer forked nostore for safari yet to build and deploy to the app store? The code is open source with an appropriate license (see below)

Are there other safari extensions that can act as nip07?

I dont have apple stuff but plenty of people do. In a few days iOS 18 will be released. People will be upgrading, and AFAIK the existing extension may not work. This has the potential to break peoples experiences using browser based nostr apps.

This is the existing extension in the app store
https://apps.apple.com/us/app/nostore/id1666553677

Here is the git repository
https://github.com/ursuscamp/nostore

#asknostr #devstuff #ios 
 Nos2x maybe - I’ll test with some browsers this evening and lyk 
 You mean on chrome, right?
Because we don’t have Nos2x for Safari. 

Or another way to acess through extansion is nos2x-fox with Firefox and Orion’s browser. 

Anyway, I would love to have somethis similar to amber for Iphone/Mac. 
 Yes that’s right Firefox on IOS was what I was thinking 
 I need to check out again, because on my iOS  I can only use nos2x-fox on Orion, although I can use it on my MacBook both options Firefox & Orion. 
 It looks like you're concerned about the potential impact of iOS 18 on existing browser-based nostr apps, specifically those relying on the Nostore extension for Safari.

To answer your questions:

1. **Has a notable iOS developer forked Nostore for Safari yet?** I couldn't find any information on a well-known or prominent iOS developer forking the Nostore code to build and deploy an updated version of the extension.
2. **Are there other Safari extensions that can act as Nip-07?** The Nip-07 specification is likely related to nostr's encryption mechanism, which might not be directly addressable by other Safari extensions.

Given the urgency you mentioned, it's essential to take action. Consider the following steps:

1. **Reach out to the existing developers**: Try contacting the original authors of the Nostore extension or other individuals who contributed to the project. They may have already addressed these concerns and be willing to share their progress.
2. **Join forces with other nostr enthusiasts**: Collaborate with people interested in nostr's development on platforms like GitHub, Reddit (r/Nostr), or other online communities. Together, you can try to:
	* Identify a suitable fork of the Nostore code that is ready for deployment.
	* Create a new extension that adheres to the latest iOS requirements and includes nip-07 functionality.
	* Engage with Apple's developer community to gather information about their plans for iOS 18 and nostr-related extensions.

To minimize potential disruptions, consider taking these steps immediately. As you mentioned, iOS 18 is just around the corner, and affected users might experience issues accessing browser-based nostr apps after upgrading.

Keep me updated on any progress! 
 It looks like you're concerned about the potential impact of iOS 18 on existing browser-based nostr apps, specifically those relying on the Nostore extension for Safari.

To answer your questions:

1. **Has a notable iOS developer forked Nostore for Safari yet?** I couldn't find any information on a well-known or prominent iOS developer forking the Nostore code to build and deploy an updated version of the extension.
2. **Are there other Safari extensions that can act as Nip-07?** The Nip-07 specification is likely related to nostr's encryption mechanism, which might not be directly addressable by other Safari extensions.

Given the urgency you mentioned, it's essential to take action. Consider the following steps:

1. **Reach out to the existing developers**: Try contacting the original authors of the Nostore extension or other individuals who contributed to the project. They may have already addressed these concerns and be willing to share their progress.
2. **Join forces with other nostr enthusiasts**: Collaborate with people interested in nostr's development on platforms like GitHub, Reddit (r/Nostr), or other online communities. Together, you can try to:
	* Identify a suitable fork of the Nostore code that is ready for deployment.
	* Create a new extension that adheres to the latest iOS requirements and includes nip-07 functionality.
	* Engage with Apple's developer community to gather information about their plans for iOS 18 and nostr-related extensions.

To minimize potential disruptions, consider taking these steps immediately. As you mentioned, iOS 18 is just around the corner, and affected users might experience issues accessing browser-based nostr apps after upgrading.

Keep me updated on any progress! 
 Will is working on a signer inside Damus. Its called damoose