Just rewrote The Immortal relay in Rust! Added some features and moderation is now much more clean. 👀 Wait for updates. You can see the current code here:

GitHub

GitHub - dezh-tech/immortal: An advanced Nostr relay implementation.

An advanced Nostr relay implementation. Contribute to dezh-tech/immortal development by creating an account on GitHub.

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

Vertex is wild. 👀 View quoted note →

[Event "Qeyhan vs Aleksave55"] [Site "Chess.com"] [Date "2025-11-18"] [White "Qeyhan"] [Black "Aleksave55"] [Result "1-0"] [WhiteElo "1287"] [BlackElo "1203"] [TimeControl "600"] [Termination "Qeyhan won by resignation"] 1. d4 d5 2. Nf3 Nf6 3. Bg5 Bf5 4. Bxf6 exf6 5. Nc3 Bb4 6. e3 Bxc3+ 7. bxc3 Nc6 8. Bd3 Bxd3 9. cxd3 O-O 10. O-O Re8 11. c4 Ne7 12. cxd5 Nxd5 13. Qb3 Rb8 14. e4 Nb6 15. Nh4 Qxd4 16. Nf5 Qe5 17. Rac1 c6 18. Rcd1 Nd7 19. d4 Qxe4 20. Nd6 Qe7 21. Nxe8 Qxe8 22. Rde1 Qd8 23. Re2 Nb6 24. Rfe1 Qd7 25. Qg3 Rc8 26. Re3 h6 27. a3 Qxd4 28. Re8+ Rxe8 29. Rxe8+ Kh7 30. h3 Qd7 31. Re3 Nd5 32. Rd3 Qe6 33. Qg4 Qe1+ 34. Kh2 Qxf2 35. Qd7 Qf4+ 36. Kg1 Qc1+ 37. Kh2 Qf4+ 38. Rg3 Ne3 39. Qd3+ g6 40. Qxe3 1-0

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 →

Good positions don't win games, good moves do!