testing forest relay from orbit of endor
ah wait, no.. it's prob just gossip is double publishing for some reason looks like, weird (i just updated this morning from master branch)
I'll try from command line.. standby
ah, but it did say "wss://theforest.nostr1.com/: OK=true id=d1291b0e966abda624bf3e7f78bd05f04efb915ad86240fb9abef192b3c88cb7 message="duplicate: have this event""
so that would mean it blasted before gossip could publish there, a good sign it works?
gossip did not obey my setting, lol..
nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h Did we ever figure that one out?
lemme see.. i have gossip on blast right now, and i removed theforest.. lets see if this comment makes it
awww, that happy infinitely satisfied look makes me melt inside
is pablo forgot bout his servers? do we need to @ him? zaplife.lol not working for me either :)
I made one.. here ya go (if this paste doesn't screw it up) just put it in an ostrich.cow file and run with -f ostrich.cow
$the_cow = <<"EOC";
$thoughts
-=(')
;;
//
//
: '.---.__
| --_-_)__)
`.____,'
\\ \\
___\\ \\
( \\
\\
/
EOC
_________________________________________
/ nostr21.com autozap pre-flight sequence \
\ initiate /
-----------------------------------------
\
-=(')
;;
//
//
: '.---.__
| --_-_)__)
`.____,'
\ \
___\ \
( \
\
/
✅ snort.social NWC configured
✅ nostr21 global crosscheck complete
✅ CPU kernel settings to max-performance
Join nostr21.com for just 21 sats. Liftoff in 2h13m
#zapathon
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr is so distracting lol, this morning I'm distracted by my nip65 relay list.. I just re-configured gossip to diagnose this, it appears my relay list as published from gossip does not have the extra field in the array for "read/write" .. I was wondering, do you plan on expanding nip65 to include other types and also, why didn't gossip add any fields there?
on further inspection it appears to only publish the "read" relays... which I suppose makes sense from a single client POV.. IE, other clients can find where I read from. However, this makes it difficult to switch clients and having to re-configure the list.. 🤔
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr is so distracting lol, this morning I'm distracted by my nip65 relay list.. I just re-configured gossip to diagnose this, it appears my relay list as published from gossip does not have the extra field in the array for "read/write" .. I was wondering, do you plan on expanding nip65 to include other types and also, why didn't gossip add any fields there?
I missed it too, thx for the repost 🙏
Hello! This is the relay.tools support. Reply to any of my messages for questions/comments etc!
What it's like learning about and holding bitcoin.
https://video.nostr.build/e0cc69394a47eceb082d996130021e2901e7d4a50c8d1f558baf4408135cb8c1.mp4
#bitcoin
#ridetheorangewave
impressive recovery damn!
Check your ISP/VPN situation? Sounds like network problem.. they might be throttling you or etc.
Big relays only seem big because they're taking the notes from the smaller relays and not giving a shit about posting back reactions and comments. Leaves lots of nostr users that posted these notes unable to see the comments, and the commenters thinking the OP doesn't respond.
I never liked this, it's a fake way for them to seem like they have a bunch of users at the expense of broken coms.
The exceptions are wine (posts back), and damus (truly big).
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgjwaehxw309ahx7um5wgerztnrdakj7qgwwaehxw309ahx7uewd3hkctcqyp7vx29q3hdj4l0elxl800hlfjp538le09epsf7k9zj59ue2y37qug4pxuq Would it be possible to add a broadcasting relay-list to one of your relays?
So that we could all just use two of yours and broadcast to the others?
Not sure what you mean. So mutiny is a write only broadcaster, which means, you won't see reactions or comments if you don't read from those relays. Some people want this because they're more about reach than interaction. Or it can be useful for profiles and relay lists. The wine broadcaster goes and collects the reactions and comments for you so it is read and write..
Not really planning on doing either of those things, I am hoping that gossip outbox will catch on eventually and it won't be necessary. It's also a pattern that will hit some roadblocks when nip42 auth starts happening.
Exciting times in nostr backend world. We got libp2p QUIC, hornet, blossom, gitnestr, gossip outbox showdown, client devs building custom smarter relays, cornychat side chats 💥💥💥
Let that fridge in 🤙
💯 absolutely zero clients would support auth if it wasn't for Mazin pushing it forward. 🙏
That bad eh? Sometimes I wonder what those other medias are doing but I am ok to just vicariously live through reports like this 😎
Maybe an 'oops lemme just uncheck the box' button hehe.. all good
I very much regret telling gossip I want to approve all relay connections, now I have a dialog that is hundreds of questions long and won't go away 😅🤙
Imagine all the steps saved if he does this for every house? Postman lifehax 😁
Hell yeah! That is one badass kittah. Damn!

