Avatar
Nice and Kind Vic
21b419102da8fc0ba90484aec934bf55b7abcf75eedb39124e8d75e491f41a5e
https://i.nostr.build/Lqsu56YxOCvwc6G5.jpg 💬 cornychat.com - audio spaces 🖼️ nodeyez.com - bitcoin node images Recommends: 🥣 zap.cooking 🎵 tunestr.io 📲 relay.tools 💩 turdsoup.com 🥔 oddbean.com 🔣 listr.lol 🕹️My Nintendo Switch Code SW-7592-4594-7016 About: I do programming, databases, data parsing, reports, visualizations. Bitcoin maxi. Available for hire Corny Chat (https://cornychat.com) operator, running the first open source audio spaces integrated with Nostr with support for zaps, room customizations. Nodeyez developer (https://nodeyez.com) providing sovereign scripts to get more from your node. It can generate images from your node accessible in a website dashboard or slideshow output to an attached display.

but being debugged at the moment, but it will catch up and zap later

yeah thats why the price is up. nothing to do with rampant inflation and money printing. its climate stuff, and not just any climate stuff, but the MEXICAN kind. be afraid!!!

we may need to dig into this further but im predisposed at the moment. ill try to track what im doing and notices returned

Another example of nostr relay notices that are ambiguous... This one from nostr.wine

ERROR: event pubkey not unauthorized

have a plan of what you want and be prepared to walk. its my experience that rarely will orgs bend the knee to whats asked.

Doing more testing with higher payout. Reply to see if the bot zaps you

reply to this to help me with testing

Any lightning / LND experts know what is going on with this scenario... #asknostr #lightning

1. an invoice is presented for payment by a counterparty

2. successfully decode invoice, check conditions, decide to pay

3. call LND via /v2/router/send including payment request, a fee limit, and timeout.

4. returns payment hash. status IN_FLIGHT

5. check status via /v2/router/track and the payment hash bas64 encoded..

LND reports it as not found

And yet, counterparty has a record of it being paid.

Does LND retry and change the payment hash? if so, is there a way i can lookup from the original payment request?

LN Provider of kevinrav@noderunners.org does not support nostr. Zap not supported

Notices from relays need more info. I was getting this from relay.nostr.band and I have to guess what the issue is.

error: too fast, slow down please

- am i making too many requests in a period of time? if so, whats the rate limit

- am i retrieving events on a subscription too fast? is that possible or is that controlled by the relay and i get an eose to determine end?

im guessing its an unpublished rate limit and have added an arbitrary delay. but i wish i knew more of whats going on. relay model is really bad for comms without a standard message protocol or status indication when one side has a policy the other is unaware of.

Filled up the tank for less than $3/gallon today. Weird.

Doable but i believe would need to pull all the kind 9735 events, parse the description tag for originating pubkey that created the zap request compared to your pubkey.

To my understanding this is what zaplife does, possibly on an inbound stream routing from peered relays to gather it live and add a tally per pubkey receiver and sender.

Doing as an on demand type of call per pubkey would need to fetch chunks from relays. If you have a specific referenced event in mind, that narrows the data set. For what its worth, the Boost Zapper bot ive been working on tracks each zap it makes both to npub and lightning address.

During the Covid-Pandemonoum-Era, did your city/town erect makeshift barricades for side streets with signage that only local residents were permitted in those areas as a measure of health safety to slow the spread?

Went hiking and checked out a side mountain bike trail. Nice makeshift ramps on both sides of this felled tree.

QUESTION EVERYTHING

This is financial advice.

This is legal advice.

This is medical advice.

This is health advice.

This is nutrition advice.

This is political advice.

no. this is not it at all.

attacker (with collaborator) opens 2 channels with you, is routing through like this..

attacker -> you -> collab -> destination

funds locked in htlc along the way. while your funds locked, collab doesnt return and goes offline. fees go up higher then the transactions you and collab originally signed. eventually attacker can broadcast their older state before the spend you have locked in htlc without the preimage returned by collab. attacker can bid up tx for new fee rates.

Doing some more testing on the zapper bot. Reply to this note (once) with a message about satoshi to participate

Does anyone know how to interpet the profile relays panel on Amethyst?

It shows 11/7. The first 11 connected and matches mine. They end with a trailing slash (bug?). The next 7 are not, and have no slash at end. There is some overlap otherwise

#asknostr #coffee

i gotta plan a trip there some time when i get back that way