I've started tagging relays that are monitored by my NIP66 monitor to include the "T" tag. What does this mean? It means client devs could use this to find "Directory" or "PrivateInbox" relays by searching NIP66 events. This solves nostr discovery. It also means that if you run a relay(s) that provide a service described by this list you should monitor and tag them! This will make them searchable via the PascalCase descriptions.

GitHub

Relay Type Nomenclature · Issue #1282 · nostr-protocol/nips

We need to find good labels for each relay type. Apps need to request users to put a relay of a given type in certain fields, and relays need help ...

As per the NIP66 Specification https://github.com/nostr-protocol/nips/blob/master/66.md The tool I use to publish monitors (possibly the only open source one) has these changes on master branch. Release soon.

GitHub

GitHub - relaytools/monitorlizard: Monitoring of relays with output formats for distribution over nostr (nip66) and InfluxDB

Monitoring of relays with output formats for distribution over nostr (nip66) and InfluxDB - relaytools/monitorlizard

GM! Take a break from the doom and try browsing wss://aquaticchickentheory.nostr1.com in your favorite relay-centric client today! It's full of cats, food recipes and other theories curated by @Dawn ♥️ #shillstr

160$ for pixel10a .. this may be the cheapest phone I ever bought, tho I cant remember what the nokia cost 🤔 banking on graphene support #soon.

someone pulls an invoice for 100k from my node, i have 5M inbound liquidity... doesn't get paid. sure hope that was a mistake cause this is just depressing. ⚡ wen onchain zaps?

devs hate having to re-work their ill-conceived libraries that they made just to shill. that's all i know. fuck the fuckers View quoted note →