Dear fooock:
I don't know who you are, but thank you for writing and publishing an ansible role to install a bitcoind instance.
Hoe this message reaches you.
I want to work on my 802.11 #mesh #network, which can use pretty much whatever random hardware you have lying around (no special mesh boards required)
but I also want to work on #Qubes/motherboard
And #Signet
And my #SelfHosted #infrastructure
And work on the rainfall detection device that will provide real time data via #ZigBee (or maybe #LoRa?) for an early warning system for flooding
And helping out two local non-profits with tech problems they're having
And help the community run, handmade goods marketplace (artisans.coop)
And the project that determines the type of network traffic without looking at the port, nor contents, which means the technique works on encrypted protocols (spoiler: it looks at packet sizes and timings to infer things about what is going on). This technique was used to determine what was being said on encrypted VoIP calls! 😈 (pro tip: use a constant bitrate audio codec to thwart this attack).
And at least 3 non-attrib projects that I will never mention here. 🤐
And setting up a #bitcoin full node, and #lightning node, and being an #LSP
And cataloging lightning wallets, and #ln software, and packages that include said software (like BTCPay), and custodial lightning services
And... crap I think I need to prioritize!
I backed up, reinstalled, and restored my desktop in an attempt to get Qubes to cooperate with Signet. I learned that this didn't help.
I realized that i do have another computer that I could borrow, yank the disk and pop in a new one, install Qubes 4.2 and see if I can repro the problem there.
I expect I will not be able to repro it. If that turns out to be the case, then I guess I'll buy yet another motherboard and start all over again.
But I guess a new motherboard is a lot cheaper than a Framework Laptop, which is the type of project I'd be likely to want to support if I were buying a whole new machine.
I'm saying it publicly right now: if I don't make a post about this in the next week, then either I'm slackin' or I forgot (perhaps because I was very much not slacking).
Either way, feel free to ping me and inquire.
...and then different ways to run your own node... I mean, where would it end?
I like the pic. Is that your tandum recumbent? Based on the seat heights, I'm guessing the steering must be in the front?
Of course, if I did this, I'd also feel compelled to do something similar with custodial wallet providers and lightning service providers.
I guess I should stop this low time commitment thing and try installing a dozen different wallets on a test phone and make a chart showing which ones are, closed source, mostly open source, 100% open source, available in the default F-Droid repos, available in a 3rd party repo, non-custodial, available on iOS, and so forth.
That way when I see someone suggest some wallet, I can look at my chart and remind myself why I like/dislike it.
I really want people to be able to receive to their lightning wallet when their node is offline (e.g. the node in their phone is closed). I hear some people are working on it...
Haha, nevermind. Apparently it didn't work when inputting the lnd url into the lndurl field, instead I had to "import wallet".
Same creds don't work in Zeus though, so I'm not sure ehat's going on there...
Has anyone on here set up a lightning wallet on BlueWallet with an LNDHub like #Alby?
The lndurl that alby gave me doesn't seem to work in #Zeus nor #BlueWallet
"On BlueWallet, users own their private keys themselves. Therefore, it is referred to as a custodial wallet." --TheLuWizz
🤦
That's... not what those words mean.
https://medium.com/coinmonks/the-ultimative-bluewallet-bitcoin-lightning-guide-b076e0b1fb20
Affiliate links. I think I'm just annoyed because their posts are less fun/entertaining then they used to be. Maybe it's just temporary.
I'm sad to see a popular account suddenly start overly promoting specific products. Like I get it, but it still makes me sad.
#Bitcoin is now more valuable than Meta. Financially, I mean. It's been more valuable than #Meta/#Facebook for a long time. 🤣
I wish Phoenix would have the option to install it without the closed source code that routes messages through Google.
People have been asking for this for literally years now so it can go into F-Droid. People have even offered help with the submission process. https://github.com/ACINQ/phoenix/issues/152
And, yes, I know there might not be any sensotive information that goes through Google, but many people (myself included) do not want to rely on Google. For anything. Full stop.
#Zeus has the same problem: it's not good enough to get into F-Droid.
Whoever levels up their game to get into the stock #FDroid repos first is going to get a significant boost in users and popularity.
Oh, 26,999 years to mine 1 block with a bitaxe. Yeah, no. I think I can find a heater and fan for less than $230
Some real talk about #bitcoin usability:
I gave away bitcoin at the last 2600 meeting. The goal was to show how easy it was and out didn't really go well. My go-to wallet has a bunch of security checks and education:
- phone pin required for app to work
- removing the pin, even temporarially, wipes keys
- lots of explanations before you van use the app
- forced backup and test before you can receive
It made for a crummy demo to be perfectly honest.
One person asked if he had to accept the terms (specifically the wiping keys if a PIN was removed). I told him no (which was the only part that really went well) and set him up with BlueWallet.
And after I sent the funds, they didn't see anything because it takes a bit to confirm.
In the end, I sent people a few bucks in coin and it probably arrived by now. Everyone who got set up on Friday was self-custodied, using entirely open source wallets, and have some KYC coins. So it wasn't a complete failure.
I wasn't going to set people up with a closed source wallet, or a custodial solution, so lightning was right out for a simple demo. It's way too complicated and cumbersome. Heck, it felt like on-chain was too complicated in this case!
So I need to work on leveling up my game of showing people how fast and easy it can be. That's the main takeaway here. 🤓
I came close to getting involved in a #LoRa #mesh project again today. Turns out the project uses #ZigBee instead.
Given the range and node density, it really should user LoRa, but the project is in such shambles, I'd just be happy if the MCU could be flashed, let alone have it read a sensor and record it to an SD card.
The idea of even having a radio of any kind is simply beyond the planning horizon. When we get there, I do want to consider LoRa though. The more experience I get with it, the easier it'll be to design my own crazy #gadgets. 🤓
I started on this last night. Most of last night's work was infrastructure stuff, so I don't have anytbing to share publicly yet.
I refactored my main terraform module to make my new VMs absolutely gorgious.
Added a DNS entry for a test full node and spun up a test VM to put it on. I have someone else's Ansible role that should set up bitcoin core automatically, but I haven't tried it.
I also didn't realize that it's possible to run a full node without 500+GB of storage! Glad to see there's a more streamlined option now to prune out data without having to trust anyone.
I'm not sure when I'll work on this next. But when I do, I'll probably finish setting up my test VM and then put everything through our code review process so it can get merged into the default branch. I try to make my merge requests small, and this one already scope creeped with the refactor, so I don't wasn't it to get unweildly.
I'm not sure if it'll be a production full node after that or a test lightning node. We'll see what kind of mood I'm in at the time.