ohhh crap i misread the nip, thought that the data would be in `event[2]`, but instead it's serialized to a string in `event[2].content`

["NOTICE","ERROR: too many concurrent REQs"]

darn, time to build another event juggler

#nostrdev

biggest thing for me is probably figuring out how it all fits together

trying it now, not sure about it yet

"The goal of this NIP is to create moderator-approved public communities around a topic and provide a simple solution to Reddit clients that might want to come into Nostr."

https://github.com/nostr-protocol/nips/pull/602

is anyone still convinced that #dogecoin is any good besides the copers

darn, #gnome web's content script support seems broken

takes effort for near zero gain

check your phone is on https://devices.ubuntu-touch.io/ :)

seems that moderating pwas wouldn't be worth the trouble

i have tested positive for at least a flavor of #autism

my thinking is if relay A and relay B have different ones, there isn't really any way to tell which one is newer right?

wait so what do i do about getting multiple set_metadata events #nostrdev

see fortnite for more information on the results of taking this approach

have been for a while afaict

it's pretty convenient that event ids are actually like universal

things are kind of coming together?? i am actually sorting events, and deduplicating events from multiple relays now.

i know people keep yelling about #walletofsatoshi and other custodial wallets, but i can't figure out how to get going with a non-custodial one without paying a few thousand sats and keeping the ability to receive zaps

WE ARE SO BACK

https://gist.github.com/grantonthenet/966d124ecae8a13b8a08d3dae6a2cc69

all i have to do is pretend that i'm working with an oversized websocket and things are working!

test #9001