I'm impressed by the number of the implemented NIPs. Thanks ...

codonaft

npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94

hex

2707f5b90b9bdc3db65352306c57da1fbf2ea3a39e50ae2302be466b99dac63f

nevent

nevent1qqszwpl4hy9ehhpakef4yvrv2ldpl0ew5w3eu59wyvptu3ntn8dvv0cprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgswls4kuk2gpu89tny8c6d0q6mdrggl5f0ya226gwv833qhn8zncxgny3vk3

Kind-1 (TextNote)

2026-09-08T05:58:26Z

↳ 回复 事件不存在

c4da2fac56bdaa5bd9c7ffa34169662bd46a152644a0199091fc4b8047f80879...

I'm impressed by the number of the implemented NIPs. Thanks for building!

Interesting. I was looking for a relay written in Rust and skimming over existing sources—nothing felt right just a year ago or so, yet today from those that I liked, I noticed at least:

https://github.com/erskingardner/wok

https://git.4rs.nl/awiteb/n34-relay.git

I see you've got a Blossom server with an optional allow-list as well—this is awesome.

The REST API—I think I was missing something like that for some weird problem. It's probably worth creating a NIP.

I see you've got an Error type for a bunch of things—have you possibly considered using the anyhow crate? It's usually adequate for high-level code and helps to get rid of a lot of boring boilerplate.

I'm curious, does your relay possibly do something else better compared to competitors? Does it provide proper NIP-42 auth requirement for NIP-59 gift wraps compatible with both NIP-17 and Concord ("p"-tag and "authors"-requested events)? Can I require NIP-42 auth for arbitrary event kinds? Possibly plan to support wot-like write-policy plugins?

原始 JSON

{
  "kind": 1,
  "id": "2707f5b90b9bdc3db65352306c57da1fbf2ea3a39e50ae2302be466b99dac63f",
  "pubkey": "efc2b6e59480f0e55cc87c69af06b6d1a11fa25e4ea95a439878c41799c53c19",
  "created_at": 1788847106,
  "tags": [
    [
      "e",
      "c4da2fac56bdaa5bd9c7ffa34169662bd46a152644a0199091fc4b8047f80879",
      "",
      "root"
    ],
    [
      "p",
      "5f6dc275f3f9f8752d010a110c226148a9ba3399c5b63a0f469ee93b1394a53e"
    ]
  ],
  "content": "I'm impressed by the number of the implemented NIPs. Thanks for building!\n\nInteresting. I was looking for a relay written in Rust and skimming over existing sources—nothing felt right just a year ago or so, yet today from those that I liked, I noticed at least:\n\nhttps://github.com/erskingardner/wok\n\nhttps://git.4rs.nl/awiteb/n34-relay.git\n\nI see you've got a Blossom server with an optional allow-list as well—this is awesome.\n\nThe REST API—I think I was missing something like that for some weird problem. It's probably worth creating a NIP.\n\nI see you've got an `Error` type for a bunch of things—have you possibly considered using the `anyhow` crate? It's usually adequate for high-level code and helps to get rid of a lot of boring boilerplate.\n\nI'm curious, does your relay possibly do something else better compared to competitors? Does it provide proper NIP-42 auth requirement for NIP-59 gift wraps compatible with both NIP-17 and Concord (\"p\"-tag and \"authors\"-requested events)? Can I require NIP-42 auth for arbitrary event kinds? Possibly plan to support wot-like write-policy plugins?",
  "sig": "fddd9596a7311763ad7b7036ae1e5d111b7579577b2a08966998cbc599e49964fca2da346deba2890c3e4faff2b5186df624764a547e5711a6595870a8271608"
}