A note inspired by @Daniel Batten's latest newsletter: Dear Bitcoin evangalists, If you want to be effective, don't preach to the choir. When it **is relevant**, casually mention why you are excited about it to people in other areas of your life. Maybe that's your mountain biker crew where you're splitting the check at lunch. Perhaps you hear a friend gripe about prices going up. It does suck, and don't act like it doesn't affect you just because you save it bitcoin. Be humble. Acknowledge that. Bitcoin helps, but it could help a lot more if people accepted it more widely. Or maybe it's at a meeting of environmentalists who are concerns about the electricity usage of AI generating straining the grid, and the demand gas peaker plants that results. Or the rollout of solar being not as fast as needed/desired. If you are in any groups who are anti-fascist and sending money to others comes up, warn them that PayPal, Venmo and all the others might be watched by their county's leader. Advise sending cash in the mail, or bitcoin if it's a large amount or you want to get it there faster. If you know people who are anti-capitalist, find common ground. They don't like getting fleeced by the top 1%, and I bet you don't either. Undermining bankers ability to use your money for their personal gain is a common goal. Bottom line is to be humble. Only mention it if it happens to come up, don't act like it'll 100% solve every problem, and make it easy for them to ask questions. Try it and see if you don't have more genuine conversations. If I'm wrong, you can always go back to the hard sell.

After investing some more time, I have what I believe is a valid .well-known/lnurlp/drhax file, but the callback field is wrong. The official docs (lud-06) say the callback should be "The URL from LN SERVICE which will accept the pay request parameter" I tried putting in the URL of the page on my LNBits server that can create lightning invoices (/api/v1/payments). That didn't work, seemingly because LNBits wants an API key to hit that endpoint (based on the status code 401 that I see in the logs). I am also seeing a request for an invoice that results in a status code 404. There have been two requests for that, almost half an hour apart from one another. I believe that is unrelated, but I don't know what it is, so I can't be 💯 sure. I feel like I'm so close, and I hope that I don't need to run some middleware service to service that callback...

It's a bloody mess out there! 1. This guide links to a non-existant git repo called LightningTipBot

Massimo (Max) Musumeci

A complete LightningTipBot (with LNBITS) full setup on a VPS - Massimo (Max) Musumeci

Updated August 14th 2023 As a part of my research activity on the Lightning Network tools, i prepared this full guide to run a complete Lightning s...

2. Presumably this has been renamed to lightning-address. That repo also links to the non-existant LightningTipBot, but also says to use bridgeaddr. It links to documentation that doesn't exist.

GitHub

lightning-address/BRIDGE.md at master · LightningTipBot/lightning-address

Lightning Address - like an email address, but for your Bitcoin - LightningTipBot/lightning-address

3. It also links to the git repo for bridgeaddr, which has been archived and explains that the aforementioned documentation link has been shut down

GitHub

GitHub - fiatjaf/bridgeaddr

Contribute to fiatjaf/bridgeaddr development by creating an account on GitHub.

So it's just one dead end after another. Outdated links, projects that aren't maintained... When I get my systemset up, I'm going top fix this for everybody. Well maintained scripts and guides, using maintained and secure software. End of story. If you gave pointers, send 'em my way.

I have 20 minutes before guests start arriving. What are the odds that I can figure out how to map a lightning address to an exosting self-hosted wallet in time?

Are you Y2Q compliant? Will is happen by April 14, 2030?

This year, I'm automating self-hosting. My goal is to have all the services we use done by the end of the year. Nextcloud, jitsi, gitlab, matrix, element, bind, djbdns, the PKI/CA server... all of it. Sone of the things I've done have already starting to get reused. It's getting easier One I've got that rock solid foundation, it'll be time to rip. 🔥

GD mates. I'll try to fill that time between you GM and GN posts with this lovely picture I snapped today. Or is it AI generated? Can you even tell?

Some people still can't tell the difference between CDN #vulnerabilities and HTTP/1.1 vulnerabilities. 🤣 I guess the ol' saying is still worth its weight in gold... "It is difficult to get anybody to understand something, when their salary depends on them not understanding it." — Upton Sinclair

HTTP/1.1 Must Die

Upstream HTTP/1.1 is inherently insecure, and routinely exposes millions of websites to hostile takeover. Join the mission to kill HTTP/1.1 now

I've finally started to get some intuition with #3dPrinting issues. I was at our local #makerspace today and the Lulzbot Mini 1 was failing to bed level. I watched it closely snd saw the nozzle never made context with the corner pad. I though, "it doesn't seem to know where the bed is" which immediately led me to "z-axis offset wrong?" A few M851 commands later and lots of testing and I was able to get it high enough to pass the leveling process, but low enough to maybe print okay. We'll see. I also think I understand how to fix it so the nozzle passes the leveling process but isn't so high off the build plate when it goes to actually print (lowering it more causes the leveling to fail). So next time I'm in, I plan on trying to print some shims to raise the entire bed assembly. The only concern I have is the belt drive, as the shims will not raise the height of the stepper motor. It felt pretty good to be able to deduce the problem from first principles instead of guess & checking!

Scotch #Peatstr

This blog post has not aged well, or it has, depending on your perspective.

Buying eggs with bitcoins | FRED Blog

😍

Roces Sport Srl

5th Savosin Fire

I learned a fair amount about reprepro today. It's been 15 years since someone requested the feature to have multiple versions of a package in their repo. Patches to implement that feature arrived more than 10 years ago. I believe it was in an official release 6 years ago. It's still not in Debian stable, testing, nor sid. It is available in the EXPERIMENTAL repo and it worked great. Just can't seem to get the new version into testing, sadly. It mirrors (ha, pun intended!) my experience with trying to get a patchlevel bug fix into pamu2f. I spent a year submitting pull requests, following up on the tickets and pull request, tracking down people and emailinb them, finding people on IRC, trying to get a mentor so I could become a volunteer contributor... and in the end all that work died on the vine. Eventually someone got a minor version update and put it into testing directly. That's the power of having an @debian.org email address. If you don't have that, you can't really contribute to the project.