hazardmack / HazardMack is on Nostr

"09db3847155de3c17fa7e1e567f5adfec488584924f7cce5d48439ed16fd7103a271b1f7b031ecbbde5fdfc973d0868a3ee3ba7e0f26195875703ad5be82f74d"

Last Notes

2024-09-09 02:16:38

- reply

Hey fiatjaf, I’m digging through khatru, cool stuff. I’m confused how botj read only and read/write permissions can be set with NIP-86 Authed pubkeys for a relay if the API only has one Allowed Pubkeys list? Any help would be appreciated, thanks.

2024-09-07 20:17:54

- reply

Thanks! I took a look and it and definitely in line with what I’m looking to do. Probably have to make a relay specific implementation to distinguish permissions amongst pubkeys.

2024-09-07 15:24:37

- reply

@npub1c3l…mpv4 @npub1man…n9tn @npub1qe3…zefe @npub1wmr…g240 @npub1awn…lrdz

2024-09-07 15:22:54

Is there or will there be a way for nostr relays to whitelist/blacklist read access? Relays can restrict write access but what about read access? Thinking about making subscription ids signed by a private key and then the nostr relay checks against whitelisted public keys and rejects unverified subscriptions. Could also use auth server. #AskNostr

2024-08-07 01:22:40

LETS GO NOSTRRRRR

2024-06-07 23:08:01

OFFER| MPN: stinky pants QTY: 51 @ $100 LT: 90 days FROM: rb

2024-06-07 22:54:39

OFFER| MPN: t QTY: h @ $y LT: y FROM: hj

2024-06-07 22:44:38

OFFER| MPN: WEBS QTY: QSEG @ $SBFEF LT: SEGSN FROM: SEGS @JACK

2024-06-07 22:43:54

OFFER| MPN: WEBS QTY: QSEG @ $SBFEF LT: SEGSN FROM: SEGS

2024-06-07 22:43:23

OFFER| MPN: DOG QTY: GOD @ $GOD LT: DOG FROM: DOG