With new X update it turned out that a lot of Iranian politicians are using this platform with Iran IP addresses and meanwhile this platform is banned in Iran. It's the second time we find a proof that internet access in Iran have several levels this recent days.

Any alternatives to njump?

What is your standard idea about NIP-62? Should relay delete events without anything consideration? Should it give a time window for canceling? Should it let you recover? #asknostr #dev #devstr

Can we sync deleted events over NIP-77? For example if I received an event to delete event X, I delete the event X and I keep its ID to prevent rebroadcast. Then I sync with another relay. Can I send them the deletion request so they can delete it or just add an only ID event so we synced deleted events too? How about NIP-62 requests? #asknostr #dev #devstr

Any kind of Service Provider thing over Nostr is a waste of kinds that can be reserved for better stuff. At least, when providing such ideas, use one kind and make them different with a tag to show the type of request. Not just reserve another kind that probably only you need until the end of world. If you want to make a new HTTP API, you don't update the HTTP RFC spec, you define your own routes and stuff by changing parameters that you have access. So if you have a new service over Nostr (Using a DVM or anything similar) just use the same kind with a different tag, maybe called the type or function. View quoted note →

Happy October 29, Cyrus the Great Day