member oink? ah yeah, peak hi fidelity

lmk if my zaps don't work. i've gone "off the ranch" as they'd say in texas 🕊️🦆🦅

true. although nostr is still a service where we can hope is decentralized enough to still be allowed to even use vpn.. bigtech services are all implementing vpn blocklists, tearing down that last semblance of privacy. (and cloudflare fogettaboutit)

huh, well, sorry to say that technology does not exist.

gm 🏝️

I think what nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9u2mk7fe is saying is for a normie to 'trust' a nostr relay provider, the relay provider must be a doxxed liable company that promises not to share your IP address with anyone unless they're under duress.

And then if they are under duress, they have a proper canary EULA that can be taken down on a deadman's switch.

If that's what customers want, I can update the EULAs in my next release of relay.tools as we are already mostly there. ⚡zap it if you like it.

this thread is so funny to me, #only on nostr

the entire internet is not private. including tor. so singling out nostr, yeah can you see how this is not a good marketing technique 😂

poor nostr. we are all too smart for our own good. gg vc funds. 😅

the whole collecting IDs and comparing before downloading events and then just downloading what is missing, that's what negentropy does, that's why i thjnk its neat having it built into the protocol..

as for uptime and redundancy, this always comes in at least double the cost. obviously it will take a super long time to compact a 1tb db. possibly on the order of days.. but you can run a replica, and still do a zero downtime failover once it is complete as long as you have enough disk space.

ive been spec'ing out some server tiers that could handle it, while also keeping cost in mind. i think having as low a server cost as possible is really important for nostr businesses.

i also like that clients have the distributed mindset here it should help with uptime by decreasing the odds of both relays experiencing unexpected downtime.

any open software you use, if you don't have a fork of it somewhere, not a good sign 😎

he's seen it, but, it's a very simple deletion of the offending code, i don't know what a better fix might be

https://github.com/jeremyd/amethyst

amethyst tries to act like a nostr blastr on every relay its on. it appears to continually send delete events for events that are already deleted as part of this. so i disabled the entire blastr part (i think) so now its logs are clean from the perpetual retries it was doing

right now, just "disable updating relays with events they already have". pretty clean

you jonesin 😅? i could be convinced

5th rebase in a row and my patch has no conflict 🐧🐕‍🦺

i reinstalled my custom amethyst 🎉

swipe up hold, and then swipe up again on the app, that does a harder reset of the app (and prob frees memory) is my understanding.

we should run nostr on kafka 😎

when you didnt quite cook the steak that well 😎

never gets old

woah, thanks for the new conspiracy lense, this was correlated with a hash dropoff right? :thinkingemoji:

same, but now im gonna have to delete firefox+nos2x as well 😂

its very carthardic

went on a good dump run today, then i got some nice groceries. the cycle continues.

so it'll say "could not find a route" and similar? huh, i wonder why no one else does this..

only issue i have with nwc is my clients dont know why payment failed. only way i know how to tell is if im reading my node logs. dont know if the spec has error reporting in it or not but that would be nice.

gm, those of us who are here, we reply with style 🤌

if you ever see a GM from me, it wasn't scheduled

I think there will definately be some traction for labels/hashtags/chats etc in the future, there has to be. I think on nostr, we basically started with a bunch of refugees from moderated platforms, and so there were not very many willing to moderate as they'd just been kicked off the system and see any form of moderation = bad. However, nostr has been churning like crazy partly due to having zero moderation controls available to the average new user. I find, the relay customers that are the happiest, are the ones who understand that to have a good experience means moderation. Many malicious practices have been coming at nostr one by one, and they tend to target vulnerable nostr population. Client devs are aloof just because their experience is good, does not mean that a majority of new users will get reply-tagged out, with almost zero recourse. Running a relay, generally it takes someone who has at least started in nostr journey, but it does not take that much. Clients can embrace this power of the relays, instead of fighting it and basically acting like they don't matter. Many a nostr platform, is sucking up all this data from 'good' relays for free and pretending like they did something. They didn't, they're leaches. And when people start using them, they don't have any form of spam controls in place that work.

Working on giving the relay landing pages and memberships pages a face-lift. Focusing on long-term feedback and stuff I've been wanting on there for a while. (Informative membership status, ease of payments, more of a relay 'profile' than the explorer was). The Trex will still be there, but behind a button. Still very hard to develop for nostr web since you can guarantee that more than half of your visitors will be un-able to sign in, but they still may want to buy a membership! Ah the dichotomy of nostr clients being the gateway to nostr, and shutting the gates on relays. But we will continue forward.. cc nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z , I haven't forgotten :)

huh, these 'people' are they in the room with us now? hehehe, kidding. sorry to hear that man. nostr has way more hackers than helpers that's for sure. someone read all my code and then tortured me for months with obscure bugs if it makes you feel any better.

what competitors even are there? nostr barely has any relay ops left that I'm aware. /me takes notes.

dont know how yet, yup

not as depressing as wasting sats 😂

seriously, how many times has this really worked for someone, its gotta be a 99% fail rate or something, and it just comes off as weird like youre trying to scam them..

ive been desktoping the notedeck, can notedeck have a private zap someday, bullish.

is it ok if i just dont upgrade. im still on v25. 😅

well, i see u in the timeline, so.. try posting stuff that lends itself to a discussion? you musta done somethin cool cause i followed ya..

whatchu wanna discuss?

you can just, not buy things

monthly

i think its kindof a big deal. one more thing we wont be gaslit about again. and who knows what else is in there hardly any of it has been really read through for more clues. like ufos! 😁

ill zap you if you manage to login to the site and report back how it went 🐳 i need feedbacks 😎

well, iphone or android? the website helps you configure the relay, but because i wanted it to be frictionless, all it requires is a payment (not a nostr login... i think..) 😂

(cant see the event youre quoting 🤔)

maybe it didnt work 😂🦍

sent, see how looks?

nice, i have some tools for this to turn it into a GUI like cpanel thing. it aint been ez 😁

hah, no. and since then i have classified the source of the noise. it was benign. in the absence of sound, the quietest signal can be as powerful as a waterfall

join the nostr mesh channel!

channel name: Nostr

psk: No==

#meshtastic

its still in draft, but its the real deal.. you have to search for its PR. (search nip66)

yes, nostr watch has a large list. and soon we can use nip66 draft to start building a distributed database of the relays in notes so that clients wont need to call nostr watch apis.

i do charge fees and etc.. i help people learn about relays and run relays for their communities. this software is fully opensource.

my cluster was under heavy load this time because a server was misbehaving. the network is growing, nostr is pretty busy.

relay.tools