New features for

relay.guide - RelayCraft Certificate Portal

Configure your device proxy settings and install the RelayCraft certificate to enable HTTPS traffic debugging.

You'll be able to select preferred relays across Relay.Guide and then publish your preferred relays as a NIP 65 Relay List authorized via a nostr even tsigning browser extension. Next up is supporting both NIP 65 and NIP 02 versions of users' preferred relay lists so that it works on as many clients as possible!

I’ve been struggling with the NDK NIP 7 signer. Wondering if anyone that’s got some experience is open to DM-ing a bit. It’s so odd, I’m getting success from NDK but the events I’m publishing are not on the relays. #asknostr

When I move from one nostr client to another and log in, how does the client know the relays I want to send and receive events from? I'm struggling to find the event kind that's used for this (if there is one)

Just did some tweaking to my algo for measuring usage. Here's the top ten relays by zap activity. It's crude but it takes the latest 100 zap receipt events and measures the time between the latest and earliest one and ranks by the difference between those numbers. If there aren't 100 zap receipts they don't get a ranking for "usage" Doing this in python is pretty terrible so I'm sure it's buggy and I'm open to suggestions on ways to do this better. It was at least a fun exercise in how bad I am mat async operations in python.

Here’s this week’s summary! View quoted note →