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

Bitcoin Core Onboarding

Consensus specification

Bitcoin Core developer onboarding documentation

The requirements to be compliant with "the bitcoin spec" are to be bug-for-bug compatible with the Bitcoin Core implementation. --- We need a Bitcoin specification. So we can develop more core alternatives, more options to select and run.

Zapstore new relay is now using WoT. Onward. 🫡🚀 View quoted note →

WTFFFFFF🥶🥶🥶🥶🥶🥶🥶🥶