So, the reason I would want callbacks, is that I can generate all these lnurls per-pubkey given that the client performs the auth. I may still have to generate just as many (or i may be able to re-use them). But then, my backend does not know immediately that it was paid, the polling cycle has to check all the invoices and the less quick it is, the more likely the user will continue to receive the notify (and be blocked from access). This could be on the order of minutes. With a callback, the payment check can happen and we don't need to rely on polling. (polling bad, callbacks good, that's compsci)
For now, we just ping ipinfo. But the goal is to use an opensource DB of IP range -> location like this one https://github.com/sapics/ip-location-db
does it check that the relay is wide open for kind20000? i am realizing now this will only work on free and open relays. which there are probably very few of these days.. (for spam reasons).
as it is now, notify forces you to make new invoice for every connection.. and then poll those for payments. it makes the backend very busy and loaded with unpaid invoices.
need to think of a better way, with lnurl+callback was one possible way i could think of.
that is def no bueno, i do not like providing full signing at all.. double if i know it's a vibe. 😂
i was going to use lnurl w/included callback url, which can ping back and let the backend know to check the payment status after it was paid.
it is very hard to test but when i was looking in the code it looked like only invoices were rendered.. i suppose i need to create a real test for it.
speaking of this, can we get lnurl support in these? last i checked amethyst renders lnurl in regular messages but not in notify. (we need the callbacks for real stuff)
i duno, i guess.. it's the whole, i expected good things.. smart things.. now im annoyed.
but its just a vibepocalypse or something? with fancy fonts?
should have just ignored it till they go through their vibecycle.
i opened amethyst for the first time in a month.. yeah, i should prob just delete and go hide in my jumbles again, ... its just .. so dumb i can't.
theyre using a csv file of open relays.. i can't unsee
its a new kind1 for bitchat that needs open relays to spam those poor users into oblivion when they just wanted a local mesh 😂
wow, im so glad i dont have time to waste right now or id be shouting to the nostr void about how dumb kind 20000 is and trying to figure out how it can be possible anyone thinks this is a good idea 😂 good luck with that tho, or sorry that happened.
gn
apparently no one has ever seen spamworld
good to see the vibers have learned basically nothing from the last 3 years of #nostr
maybe this time is different, nobody will trust a viber twice, reputations matter.
the answer is that friction is necessary. we live in a world of AI and spam and scams.
pow with small micropayments, building reputations, would be my preferred solution.
in the past it was simply email addresses, but those can be farmed quite efficiently and sold to spam, but at least it still is a slowdown vs nostr keys are instant to create.
ironic to me that this is surprising at all, given the last 3 years of nostr comment spam..
i havent used it yet but it seems like after they did this geohash nostr thing, no. before that it was just bluetooth and no.
irc had moderation controls you could kick or ban someone from the room.
i too, thought it would be more like this.. and not just 'teleporting' scammers and spammers into the chats.
more like proof you were in a bt chat at some point, like you had a relationship w some other keys..
the weird thing about bitchat is.. well.. it creates new keys, so .. unless you want to get harrassed off the platform, probably gonna need (all the stuff we try to do to prevent spam and harrassment, like lightning payments, wot, etc.)
or provide some relays that are tightly integraged somehow with bitchat, using bluetooth proofs of location or something.
anyways..
if not it will probably get ruined just like free relays did.
this is what it looks like in jumble (since jumble knows what relay(s) you were browsing from.) the toggle sets the nip70 flag.
I dont think nostr:nprofile1qqsgydql3q4ka27d9wnlrmus4tvkrnc8ftc4h8h5fgyln54gl0a7dgsppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytc79p4zh can hear me, something about primal doesn't like my npub.
in amethyst you can tell which it is because if it knows the name, it has the event, or it just displays the name as npub.
are you using NIP66 for this? it has geo tags.. you can find them on monitorlizard.nostr1.com and relaypag.es
anyone can publish these, with a monitoring tool like https://github.com/relaytools/monitorlizard
to clarify my question a bit. I see you have a .csv file of relays and lat/long and im wondering how you generate it.
migrating to georelays on bitchat. find the closest relays for any one geohash and use them instead of the big default ones.
https://github.com/permissionlesstech/bitchat/tree/feat/georelay
hopefully this will inspire more relay ops to accept kind 20000 and better distribute relays globally (we need more smaller ones).
are you using NIP66 for this? it has geo tags.. you can find them on monitorlizard.nostr1.com and relaypag.es
anyone can publish these, with a monitoring tool like https://github.com/relaytools/monitorlizard
please hold, for the next available vibe representative 😅
ok so i guess.. when we hear back from nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 about testing, maybe he just didnt try build.. i dont know why it would matter but i am learning that blossom has an equivalent of a relay list, for your blossoms, and that it matters what you pick..
is there any reason why yakbak cant use blossom build? i dont think yak is encrypting..?
so, what's the verdict? i see nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 is using blossom.band to test, which i wasnt aware of. it sounds a bit like nostr:npub1cgcwm56v5hyrrzl5ty4vq4kdud63n5u4czgycdl2r3jshzk55ufqe52ndy 's problem is she tried to use, nostr build blossom and satellite.. does yakbak only support blossom band and haven? and then it sounds like nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn has a fix for flotilla but it also may not work with blossom build after the fix, which blossom does flotilla support?
thanks for all the comments everyone ♥️
i mean yea ultimately i would love to skip the cider and create great danger with some #medicinal 🌝shine. #ihaveadream
i really did, have a container and i swept it when i moved.. there was no dust on anything, only the dirt i tracked in.
nope, i dont think it would 😁
cleaning just mixes the dust back into the air, then it falls again like rain.
I actually don't mind these days that most of nostr uses primal and damus. That way, I only have to connect to two relays, pipe it through 100k brainstorm calculation and then I get a cool firehose minus the garbage.
Keep doin' what you're doing #nostr
#shirtless #jungle #zapless #primus feed
was the common name for "the NUT" already guessed?
and i will need to see it again, in december to see if you are really a line caller