#asknostr #devs #lnd
Anyone got a working example of LND TrackPayment via REST?
I try this....
curl -k --header "Grpc-Metadata-macaroon:02010304whatevs" https://f.q.d.n:11234/v2/router/track/{payment_hash}
where {payment_hash} is passed as hexadecimal (string 64 in length for 32 bytes).
error returned claims invalid hash length of 48, want 32
my next move is to convert to bytes and base64 as that error about 48 could be thinking the 64 passed in is in base64.
#asknostr #devs #lnd
Anyone got a working example of LND TrackPayment via REST?
I try this....
curl -k --header "Grpc-Metadata-macaroon:02010304whatevs" https://f.q.d.n:11234/v2/router/track/{payment_hash}
where {payment_hash} is passed as hexadecimal (string 64 in length for 32 bytes).
error returned claims invalid hash length of 48, want 32
my next move is to convert to bytes and base64 as that error about 48 could be thinking the 64 passed in is in base64.
i didnt even know they supported unencrypted cloning
hell yeah this is awesome!
thats the podcast player i use!
sad part is no way to know where this is as a search returns multiple events for the day
but you arent slipping into my DMs like nostr:npub1jcjxjg92200kdp8guw8sysg8gr0ez29hahrfdy49h30hgnkpa4kqfvmtwx
what up party people?
Are you noting blockheight on the reverse?
im caught up on all episodes of propaganda daily
Nah. at best we ponder the thought
Yeah. Ideally bot would handle unlimited or up to a given amount. At the point you are at youre experiencing the labor cost side that doesnt scale well. A bot makes sense, just needs to be affordable to still be viable
got LND?
for a full service, no.
but for a single pass script run locally to zap possibly. this may be viable if you run your own LND node and dont mind using command line
This is something i feel that could be built by any coder familiar with nostr kinds.
If I were to do this Id build a service around it and probably base fees around both a time frame (e.g. base daily/monthly cost since its a monitoring service), and a fee per event handled.
Theres quite a bit of functionality needed to support such from the configuration and top up side
- auth with nostr and/or lnurl auth
- add/edit config (define rules for... relays to listen/check, pubkey for events to listen to references, phrases to look for in original post, phrases in reference posts, amount of sats to zap, comment to include in zap, start time, end time, limit number of posts to zap)
- check balance, add funds
and then extend with more rules and
- list campaigns (for multiple per acct)
- reports
I will sell you some shit for half that. Prebagged too.
im caught up on all episodes of Nostrovia
its a haiku based on an encounter in last nights D&D session
Id get up from my table, grab some napkins/wipes from the bar and offer to help clean them up.
If they attempt to puke on me ive at least got a makeshift napkin shield and some to clean my own.
And if they decline then ive got a bundle of napkins all to myself.
i think a nostr podcast app should leverage nostr events for comments to share between clients. right now comments for boosts on fountain or breez live and die solely on those platforms
as a user i dont care where content is hosted as long as i dont need to provide an kyc, credit card info to access. for listening to podcasts im currently using breez over fountain and stopped doing integrated zaps/boosts in both apps due to crazy high fees. prefer to just zap or lnurl pay someones account directly.
i guess i need more info by what is meant by platform
- hosting?
- tools to create?
- feeds for discovery?
- clients to listen?
what would it offer that rss does not?
trying to hamfist OO like concepts in most languages is stupid but is easier to mentally treat
This cant be true or theyve changed something as a recent install of the extension on a new machine and login resulted in the nsec being available
Debating whether I should create a new npub since I put my nsec into the alby extension which compromises it to alby in a similar way people were up in arms over zbd
Thats a bit of an inefficient approach, requires the endpoints to use lightning, and bolt on encryption after the fact the same as secure tunnels are done for http. To that end, Tor proxies are an improvement.