I have to agree here as well. Unless you are in the spotlight as a client dev that ships a new shiny toy every few days, you are ignored. Many people do not realize that not everything on Nostr is clients that are updated multiple times a day. People behind the scenes that do things like infrastructure development, spec review, etc. also get ignored. There is also a lot that @The Fishcake (nostr.build) does (that you don’t see) to make everything work smoothly on Nostr.build. Many people do not know the following, for example: - I developed many specs like NWC and contributed to others like NSC - I have developed the Nostr Plebs service fully - I did spec review on NIPs to some extent until my access was revoked for fiatjaf for presumably not being an LGTM parrot - I took over the Nostr.land relay after it was going to shut down due to bad infrastructure I have recently started partially shifting my focus to work on a project where I feel properly valued for my efforts. I am still here for those that are still supporting (thank you). 🫂 View quoted note →

testing

I think the kind range 6xxxx should be reserved for relay-signed events. These have a sig field of “relay” but otherwise act mostly like normal events. One use case I am thinking of is a way for relays to notify users of information like them getting access, subscription expiry, or updates. You AUTH and then ask for kind 60001 events, which are from the relay.self pubkey.

gm.