It's complicated, but yes, that's the idea. Plus, I can access my file server, gitlab server, sync calendars/contacts to my mobile device, have videoconferences, send and receive email... you get the idea. This is all the case now, I'm just rewriting the setup DNS setup scripts to be more reusable for others.

I currently already run 7 production DNS servers. Four of those are recursive DNS servers for my LAN and DMZ.

It would only be two instead of four, but I have two domains and I didn't want an admin of one to be able to mess with records of the other domain. Looking back on it, I probably could have also accomplished that with two servers, but now that I have them set up, I'm unlikely to change it unless I run into an issue. They're low resource utilization and having a couple redundant servers is never bad when it comes to DNS!

The other three DNS servers only resolve my domains. They do not recurse. They would not be useful if the internet went down, as they only speak to things on the internet side. This is because they give out the public IP address, whereas the recursive servers give out the internal IP addresses to local machines.

I also have my own PKI, which means I'll still be able to use HTTPS indefinitely, because I can renew my X.509 certificates. It also handles other TLS connections, sign SSH host keys, and sign SSH user keys... but I'll save that explanation for another time & another thread. 🤓

Tonight I was working on the automated deployment of a recusive DNS server. Why?

1. I want it for my home network

2. I want to make it easy for others

3. I want to be able to use the #bitcoin #lightning network **without the internet**

Well, sorta without the internet. I get that if there were two lightning nodes that didn't trust each other, on the same LAN, they'd want to have watchtowers and such, but the point is that payments could still go through when the internet is down as long as the lightning nodes tolerate it.

Yeah, USB cables seem way less reliable than they used to be! But in this case I tried plugging it directly into the motherboard and it acted the same as when it was plugged into a hub.

I'm sure I'll figure it out eventually

I'm still pissed that my computer (motherboard, it seems?) is screwing up USB devices in some elusive way that I don't understand at all.

I want to drop everything and work on it until I figure it out and fix it or work around it. But life doesn't work that way. There's cooking, and laundry, and a dozen other projects that are higher priority right now.

Heh. We're pushing lightning to the limit. 🤣 Good times.

Holy unused API keys batman! I cleared out all the old ones and created a new one and am back i'm business. Thanks!

Also, I wasn't able to use the button to launch my Nostr client (may be a limitation of Tor Browser), but more importantly the copy to clipboard does so in a way that can't effectively be pasted into Amethyst.

If there were 3 buttons to copy the key, URL, and secret (respectively), that would make your side of the system easier to use.

I was able to scroll around and carve out the values, and then guess at which one goes into which field, but when each value is longer than can be viewed in the text box, it's quite cumbersome.

I tired FlorisBoard and the stock keyboard in GrapheneOS and neither worked.

I'll just wait for Amythest to be fixed and if it doesn't happen then I can move to another client. I really shouldn't need to install a third keyboard in order to use a social media app.

Amethyst is still crashing when I tag people (yes, I updated earlier today), but hopefully this gets to hello@getalby.com

nostr:nevent1qqsqhyevcytu0k5qws2fx8fkfxn4nlr4na7gz63aa20g22sygs99vtspzemhxue69uhkummnw3ezumn0dahx2uewvdhk6q3q6v82nr4xt62nlydtj0mtxr49r6enc5r0sl2f7cq2zwdw7q92j5gsxpqqqqqqz835lv8

nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm

I really want to keep using your service, but I've been unable to zap people via Amythest for months now. Here is the error message from my latest attempt:

Your wallet connect provider returned the following error: Something went wrong while paying invoice: oauth2: cannot fetch token: 401 Unauthorized

Response: {"error":"invalid_grant","error_description":"The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client"}

You seem to have developers who are willing to look into these things, so I'm asking that they please take another look now that I am able to provide a specific error message that points to my "wallet connect provider".

And yes, I use Tor.

It'd be helpful to include your BTC address on your site in addition to the QR code. It's easier for people who are viewing the site on a mobile device, as it's not easy to scan a QR code there.

What concerns me is that I don't think this is motivated by "it'd be a good idea if we only allowed coinbase customers to pay in crypto". This smells of "we'll save more money by not taking the heat over KYC regulations than we will lose in customers".

If that's true, expect this to start happening in all US based payment processors, and then it'll spread across the globe.

I'm going to wait until I have personally set up a BTCPay server before I personally recommend that solution. Hopefully that will be something that rises to the top of my pirority list soon. 🤓

Matt, I'd be interested in hearing more about what you have.

We buy roasted coffee beans 5-10 lbs at a time and pay $9/lb, BUT we have a very specific bean and roast that we like AND we get it from the EqualExchange coop, which means the money goes to the farmers and roasters, not middlemen.

If you can compete with that, we'd consider switching to you and paying via lightning.

This report is 🔥. It lays it out plain and simple.

I'm about to get involved with precious plastics so I'm going to be dealing with these technical and logistical issues first hand in the coming months.

nostr:nevent1qqs8elxpr460jzg0h6lf2hkk3yyjt96842260f6p3awvqyxamql7vlgpzemhxue69uhkummnw3ezumn0dahx2uewvdhk6q3q8x5tzar4hcxmgn33870aqvhlmcvrez4avjvwfye2suenp5kdfp5qxpqqqqqqz0g8m4t

Lou Malnati's for life!

For web-based stufv, take something written without a bunch of heavyweight frameworks and hack it up to do your bidding. I'd suggest MagicWebStore.xyz

It's just static HTML/JS with minimal libraries. No npm, no vue or whatever, no bloat or big, hard-to-debug frameworks.

I can attest that Swappa is awesome, as is GrapheneOS. GrapheneOS now supports Google Play Services and so it should be able to run WhatsApp and any other app that requires those services be installed.

As for the bigger question about money and privacy in general, it's possible to get a lot of privacy for not a lot of money.

For example, riseup provides email and VPN service in exchange for donations. https://riseup.net/

It's often fairly simple things that can make a big difference. In my opinion, the biggest problem is that it's takes time to learn what protections are actually effective versus who is just trying to sell you something.

For what it's worth from a total stranger on the internet, I can say TheNewOil really hits a home run on that front. It's not aimed at "privacy at all costs" people. It's aimed at people who just want a reasonable amount of privacy online. You can spend a few minutes watching a video and then set up something to make you a little safer online. Do that a few times and you'll be in a much better situation.

https://youtube.com/thenewoil

Tonight I read about accessibility on a page by Eric Eggert and several pages by W3C. I'd suggest all developers who are compassionate and empathetic read this. It's not even that long.

https://yatil.net/blog/no-accessibility-without-disabilities

Wowee. 🤑

It was a fun contest, even when one of my bulletin board posts was denied without explanation. 🤣

Thanks for rallying ordinary people to be the bitcoin marketing machine.

Cereal is a geat way to start your day!

🤣