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!