This nostr thing isn't really working too well. I get a notification, click on it, the post is gone. ( nostr:npub1e0z776cpe0gllgktjk54fuzv8pdfxmq6smsmh8xd7t8s7n474n9smk0txy it's yours)
Then it shows a ton of supposed replies that seem random posts and not replies. If they are replies, the spam problem is huge on here.. https://nostrcheck.me/media/a9e42a0ca6e4b1208088b68a4fd6407481b12060f915a0fecb4c8874557e3749/84e012e9f94fab6b932f6c661ac1ca32a4a7d0c1a3308f8d9ae02b60c7722473.webp https://nostrcheck.me/media/a9e42a0ca6e4b1208088b68a4fd6407481b12060f915a0fecb4c8874557e3749/fb50cd05d9efad4630af9de3e632ffb7e4f0f635976884c241a03b026dce1985.webp https://nostrcheck.me/media/a9e42a0ca6e4b1208088b68a4fd6407481b12060f915a0fecb4c8874557e3749/074567123b350b6977335948eb962c2d8c0a2f0a2af814278a3634edc97d2964.webp
This is an openvibe issue.
Note this issue probably affects nostr apps as well! If you're a nostr app builder relying on a rust sdk, create a hibernation check!
Over time got some reports of strange errors in the breez sdk. Sometimes there were DNS errors, sometimes payments not working, sometimes requests not arriving at the greenlight servers at all.
Turns out it's app hibernation causing these issues. The rust code would still be running, but it wouldn't get any resources to execute. That causes grpc channels to fail functioning after coming back from hibernation.
Adding a 'sleeper loop' to the Breez SDK. It sleeps in a loop for one second. If the sleep takes a long time, it means the app hibernated. Then reconnect any grpc clients.
It's an interesting dynamic to guard against. Thr SDK should becone more robust for hibernation this way soon.
Yeah that's the way. But how to get each block in forward order?
I have an application that needs to get certain data from the chain, so it syncs blocks off the bitcoind rpc. Parses the blocks, checks if there's relevant data and moves to the next block. I want that application to start at genesis (or some birthday block) and sync the chain from there.
Right now I'm getting the headers first, backwards, from tip to birthday. Then sync the blocks forwards, from birthday to tip. I was wondering whether I could skip the headers part and sync directly from birthday to the tip, forwards.
nostr:npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp is there a rust implementation of a BIP-353 lookup out there?
Is there a way to sync the chain forwards from the bitcoind rpc? The only way I found now is to
- get the tip
- get previous headers one by one
- then start syncing blocks from the start with the headers you've found
What I'd like to do:
- get the genesis block
- get the 'next' block
- etc.
Is there way with the bitcoind rpc?
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 heeft mij, naar Itialiaans voorbeeld, opgedragen in het Nederlands te posten. Dus, hierbij;
Waar zijn al mijn medelanders?
Het is patat.
Hier nog een. Ben benieuwd naar de theorie?
Yeah that's worth a PR I think.
Tip about CLN:
When CLN forwards a payment and it has multiple channels with the same peer, it selects the channel with the highest available balance out of channels with the same fee policy as the one the sender specified.
Say you have 3 channels with the same peer.
- A has fee 10ppm and is depleted
- B has fee 10ppm and has 100sat sendable balance
- C has fee 5ppm and has 1 BTC sendable balance
Sender computes a route that contains channel A, sends a payment.
Your node will pick the channel with the highest balance out of channel A and B, because they have the same fee rate. In this case it picks B because it has the highest balance.
If the payment was more than 100sat, the forward will fail.
Yes! Just not for future calendar events or anything like that.
Yeah. It's permanent. There's several names for this. Among others:
LND - lightning nervosity disorder
CLN - cerebral lightning nervosity
Hello World
Ability to remove relays from the settings menu would be nice.
Also when you add a relay, it seems you have to restart the so in order to be able to find people on that relay.
Yeah, I just installed.
It looks pretty slick, onboarding is easy.
I would like to be able to find people if I'm not connected to their relay. Either through npub, or through the email address notation.