95
Trooster
956474f434df528596c0818828cf80044fec6789094a9dbe21df80ac62b34ebd
#AUStriches

Great chat boys nostr:nprofile1qqstl90p53datmzu5r2zpa84tngpv3w8sj040lw38wx94lkya0wvsjqpzamhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuegpzfmhxue69uhhqatjwpkx2urpvuhx2uc0ec68a nostr:nprofile1qqsf2ds69dp2ympzhtpmdd46f3w2cnfkjphtpnaesf5xs8z95vqu2xqpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7lz79eh

https://fountain.fm/episode/ZEDPyz6r3LZIy6P9EALi

Listening to the chat now @ BH. Solid start

(unsure the nomenclature for block height) 928211

Is this guy a Bitcoiner?

“…governments cannot continue to live beyond their means and rack up unmanageable debt.”

“It’s as if since COVID-19 everyone has decided money is an abstract concept.”

He cites Milei as “Milei means it when it comes to reining in spending…”

From a NewsCorp opinion piece today in ADL.

#AUStiches #Australia #journalism?

I miss Reddit groups - lurking, asking questions to groups who have signed up to chat about ‘this thing’.

I still have reddit , but is there a way to navigate like that on NOSTR? Is it just using hashtags?

lol -

protect your identify, hide amongst a crowd with your BTC

Crowd - crickets chirp

Access your porn without logging in

Crowd - WHO HAS BEST VPN?!?!!

Replying to Avatar Gigi

The shower. He’s describing the shower. 🚿

That’s more savings than most have, and many of those with >BTC would not have been able to squirrel away 1BTC at 2024 (probably even earlier) and beyond price.

So most don’t have that. To investigate how many have their savings in it you could frame it as ‘how many people self custody their own life savings?’

One thing I like about console gaming is that I like the games happening in the family room on a tv. More social, more open, more chances to interact while they game and I do chores.

So helpful, so powerful. Thanks for making this. Setting up. Now.

nostr:note15raep825r9rkccsa8wvt3xksasn6mj8te8xfssqel33fdkuqtt4sus2mnz

I like this framing. Take the red pill, discomfort in coming to know the enslavement of most of our lives and work to thread together an unstoppable money that frees us all nostr:note1l8yagth37ujnzs50m8g7s3wwh5mt0pn6ky4m76q39e37pgkm3tjqv0385l

Replying to Avatar Rusty Russell

It is important to empathize with frustrated users. It's sometimes an unattainable ideal, but who hasn't hit software that Just Doesn't Work? We don't really care if it's just something about our setup, or fundamentally broken, or a completely unhelpful error message: it's an incredibly frustrating feeling of impotence.

Sure, you shouldn't take it out on the devs you aren't paying, but we're all human.

I can't speak for all developers, but I became a FOSS coder in the Linux Kernel. That gave me a pretty thick skin: Linus could be an ass, and even when he was wrong there was no appeal. So I generally find it easier to sift through the users' frustrations and try to get to the problem they are having.

https://github.com/ElementsProject/lightning/issues/7180

And often it turns out, I agree! This shit should just Work Better!

CLN payments are the example here, and it was never my priority. That might seem weird, but the first production CLN node was the Blockstream store. So we're good at *receiving* payments! But the method of routing and actually making payments is neither spec-defined nor a way to lose money. It's also hard to measure success properly, since it depends on the vagaries of the network at the time

But it's important, turns out :). And now we see it first-hand since we host nodes at Greenlight. So this release, unlike most, was "get a new pay system in place" (hence we will miss our release date, for the first time since we switched to date-based releases). Here's a list of what we did:

1. I was Release Captain. I was next in the rotation anyway, but since this was going to be a weird release I wanted to take responsibility.

2. I wrote a compressor for the current topology snapshot. This lets us check a "known" realistic data set into the repo for CI.

3. I wrote a fake channel daemon, which uses the decompressed topology to simulate the entire network.

4. I pulled the min-cost-flow solver out of renepay into its own general plugin, "askrene". This lets anyone access it, lets @lagrange further enhance it, and makes it easier for custom pay plugins to exist: Michael of Boltz showed how important this is with mpay.

5. A new interface for sending HTLCs, which mirrors the path of payments coming from other nodes. In particular, this handles self-pay (including payments where part is self-pay and part remote!) and blinded path entry natively, just like any other payment.

6. Enhancements and cleanups to our "libplugin" library for built-in plugins, to avoid nasty hacks pay has to do.

7. Finally, a new "xpay" command and plug-in. After all the other work, this was fairly simple. In particular, I chose not to be bound to the current pay API, which is a bit painful in the short term.

8. nostr:nprofile1qqsx533y9axh8s2wz9xetcfnvsultwg339t3mkwz6nayrrdsrr9caagppemhxue69uhkummn9ekx7mp0fqcrlc changed our gossip code to be more aggressive: you can't route if you can't see the network well!

Importantly, I haven't closed this issue: we need to see how this works in the Real World! Engineers always love rewriting, but it can actually make things worse as lessons are lost, and workarounds people were using before stop being effective.

But after this fairly Herculean effort, I'm going to need to switch to other things for a while. There are always other things to work on!

Appreciate the work and the run down Rusty 👊