I put it in pots outside. I know better.
It's starting to warm up. Time to think about tapping your maple trees.
https://video.nostr.build/9683c7ee0b730a72e6dad0f6aaebff6bd7999b43ebb9f8288754c9d47c608dc2.mp4
#Gardening #Homesteading #Garden #Homestead #foodstr #prepper #prepping #MapleSyrup
I always laugh when I think of this clip.
Mine died off when I brought it in. I watered it for a while and thrn gave up
But then, after months of absolute neglect (no water, no grow lights, not near a window), I saw some thing sprouting in that pot. Some of it was goldenrod, but some was the mint, seemingly back from the dead! So I think I'm set for life on this front.
I plan on propagating it in the foreseeable future. After I have a few, well established pots for myself, I'd be happy to share.
That was before my time, but I've heard about it and it sounds like it was a clever & fun system!
I'm giving up on this hydroponic stevia. I also had trouble getting mint started indoors (I know, right?), but when I chucked some seeds in a pot, set it outside and then ignored it, it did just fine. So maybe stevia will enjoy the great outdoors in this same manner.
Next up, I'm trying spinach in this same setup. Sown today, just now. Seed packet said 85% germination rate and I planted 2 seeds. No details on germination time, but it said 50 days to harvest.
"Machankura is a result of that bank account account being frozen... Do I spend time figuring out and getting my account unfrozen, or do I build something else?”
— nostr:npub1773r2y5zl3sa7xufmye96un3hf02rse8j82hkd45ps0wvk2hrkasslesjt on nostr:npub10qrssqjsydd38j8mv7h27dq0ynpns3djgu88mhr7cr2qcqrgyezspkxqj8
#BitcoinTalk
https://youtu.be/tRjoWsc08h0 nostr:note17nmcl4qnggrtn8mwgsrtavh08lnac6m6fz2wg7d0kkgqk9lh2nvqfasnk3
Cool to see others are also interested in getting #bitcoin to work without the internet. What nostr:npub1773r2y5zl3sa7xufmye96un3hf02rse8j82hkd45ps0wvk2hrkasslesjt is doing is far more practical and he's actually done it where my offline bitcoin is not tangible yet.
OK, I got this figured out. The core issue is that Alby forces the recipient to dictate how much is sent, not the sender.
They can't handle invoices that don't specify an amount. I'm not sure why, nor do I understand why the error message I received didn't just tell me that, but that was the answer in the end.
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm
You solved my problem the other day, lets see if you can go 2 for 2. I can't send sats to a Zeus LSP user. I try to send, get an error, and verify the recipient has inbound liquidity. (See pics below)
The "No Route" part makes it look like you don't have any channels open with Olympus (or anyone who has a channel to Olympus). Can you confirm this is not true? Do you know where I should look next to fix this?
I'm now getting emails telling me I need to move some sats out of my account to be below the 1M sats level. I'd appreciate your help here, as that's what I am unable to do...
I am not
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm
You solved my problem the other day, lets see if you can go 2 for 2. I can't send sats to a Zeus LSP user. I try to send, get an error, and verify the recipient has inbound liquidity. (See pics below)
The "No Route" part makes it look like you don't have any channels open with Olympus (or anyone who has a channel to Olympus). Can you confirm this is not true? Do you know where I should look next to fix this?
The deflationary aspect is a good one to lean on to explain the conection to being more resourceful (or thrifty, frugal, economical, etc.).
I can't really use myself as an example because I already tried to save money at every opportunity, so it's not like bitcoin pushed me in this direction.
Now that I think of it, I can't recall any stories about people who got in early on bitcoin going out and buying a lamborghini or a mansion. Maybe it happened and I missed it or it went unreported, but it seems unlikely because critics would LOVE to connect btc to what they consider wasteful spending.
Thank you all so much for your patience while I paid out all of our contest prizes! I learned a lot about Lightning during this experience:
1. Some wallets limit users to a total balance of 1M sats
2. Some wallets won't accept a single zap of 1M sats
3. When these restrictions are removed, it works great!
Here is the status of payments:
nostr:npub1gcfaxg923qp8j2j69ue5ng3q0ce0vu0gcpqqtqxacv8d5m7a7c4qmhchdf - PAID
nostr:npub1jk9h2jsa8hjmtm9qlcca942473gnyhuynz5rmgve0dlu6hpeazxqc3lqz7 - PAID
nostr:npub1e3mx09yq53gyh9368qyuhfstgk8t7p5vvfcnvgwa4994y7rqg37s20qvr5 - PAID
nostr:npub14uu85mzg332ggzyt5u2ahdpt2h889dr4u83ts6l8jxeyhr23ug2sq8gk69 - HALF PAID
nostr:npub1z4m7gkva6yxgvdyclc7zp0vz4ta0s2d9jh8g83w03tp5vdf3kzdsxana6p - PAID
nostr:npub1d7k8mz2jvajyjvjlhtg5qcg4rhhfm0nrytqn5ay2rq4708tk74ss95llmc - NEEDS LN ADDRESS
nostr:npub1wpualymnks9vadsultel3kqaea4fj4zj3cnp9f5qzqtprxq0k8ssfnh5l9 - PAID
nostr:npub1fazvg3rzx5p6hdx43l8gyz32rs40arkwgca765dwsvtylfjdelqs32nt4k - PAID
nostr:npub16v82nr4xt62nlydtj0mtxr49r6enc5r0sl2f7cq2zwdw7q92j5gs8meqha - PAID
nostr:npub1n0aq6vafymeezu8rgyuluw2nsvwwf0e0qdpc9d2uvcfgclsf4d8s3qqu2z - PAID
nostr:npub1dk5pn7gad897tywq3vcl24wx6z4ejpge0663tptwxwgynsqccxhsn65sgk - PAID
nostr:npub182geseqlaxv20ptu3k0u06zqhgf6rmalv5ssjm9n8jvz0ss6anaqsthzsc - PAID
nostr:npub1c9s2dnan337kywugpn4jm2uzpmds7geysyyme5ew9g6d8y2x572sum5tew - PAID
nostr:npub15ypxpg429uyjmp0zczuza902chuvvr4pn35wfzv8rx6cej4z8clq6jmpcx - HALF PAID
nostr:npub16dhgpql60vmd4mnydjut87vla23a38j689jssaqlqqlzrtqtd0kqex0nkq - PAID
nostr:npub16e3vzr7dk2uepjcnl85nfare3kdapxge08gr42s99n9kg7xs8xhs90y9v6 - PAID
nostr:npub1vdaeclr2mnntmywm93h2p3xfkgnqcxe8prrzcny4s07q735j6d7sfkmnxz - HALF PAID
nostr:npub19vem9txx6xl9j2dx0pm2g76g8grsccguq5lsfz8l8u0yek5lynzshkgqpq - PAID
nostr:npub16wy27uj48r82gskq48uvxku8076h0y9xcngsgry7j4yn6zxmnznqu4hy6a - PAID
nostr:npub1y448jswp88k7qeny6865tmhga450v84kafkddggxjjnsawpgh2xs364rhy - HALF PAID
nostr:npub15pl6u3s6dlq0hfskercdu74jd6w6ec0hzcrg434nhgj4ylvrm7fq8e8439 - PAID
If you are HALF PAID, you need to withdraw your sats from your wallet. Let me know when you've done that and I'll be able to send the other half.
The end of this contest was really rough timing with an IRL event that required my full attention. Thank you again for your patience and for never doubting you would be paid 🧡
This Vote For Better Money account is 🔥. I got my million exactly as promised. If they ever run a contest again, hopefully someone boosts this post to show everyone that yes, they will just hand out like $10,000 USD worth of sats to semi-random people on the internet! 🫂
...and they'll post about the practical, real world problems that come up with the lighting providers too. Calling it like it is. 😃
I've been thinking about distributed, rag tag tech solutions for decades, but theyve been in sharp focus the past few weeks and days in particular.
I'm imagining a community of people who each run some services which will be down some of the time, but you always want everyone to be able to use everything all the time.
At first I was thinking load balancers, round robin DNS, failover... you know, the tried and true solutions. But those all have huge problems in this type of environment.
Then it hit me. Go back to computing in the 80s and 90s, where it was expected that people and even servers would be offline regularly. Take inspiration from BBSes, email, and the more modern systems like git, RSS (with auto-downloading).
#Nostr is designed along these same lines too. Nostr clients don't let you post while offline like you can send an email while offline, but that's just a client implementation decision.
Effectively, the point is to make things work well offline.
This strategy doesn't work well for some things like real time communications (video teleconferencing, voice calls, etc.) or when multiple people make changes to the same file at the same time. So we need different solutions there.
That could be a low-tech solution like scheduling a meeting on a meet.jit.si server but if that's down then falling back to https://vc.autistici.org/ You could have a tertiary option if needed, or even more.
Most important is that I want solutions that work today, not things that are yet to be built.
That's the whole point of a rag tag setup: it's low time preference. Don't invest huge amounts of dev time, just make it happen now with what you've got.
We can start with the easy things first.
I've been thinking about distributed, rag tag tech solutions for decades, but theyve been in sharp focus the past few weeks and days in particular.
I'm imagining a community of people who each run some services which will be down some of the time, but you always want everyone to be able to use everything all the time.
At first I was thinking load balancers, round robin DNS, failover... you know, the tried and true solutions. But those all have huge problems in this type of environment.
Then it hit me. Go back to computing in the 80s and 90s, where it was expected that people and even servers would be offline regularly. Take inspiration from BBSes, email, and the more modern systems like git, RSS (with auto-downloading).
#Nostr is designed along these same lines too. Nostr clients don't let you post while offline like you can send an email while offline, but that's just a client implementation decision.
Effectively, the point is to make things work well offline.
This strategy doesn't work well for some things like real time communications (video teleconferencing, voice calls, etc.) or when multiple people make changes to the same file at the same time. So we need different solutions there.
That could be a low-tech solution like scheduling a meeting on a meet.jit.si server but if that's down then falling back to https://vc.autistici.org/ You could have a tertiary option if needed, or even more.
I want to believe that #bitcoin will encourage society to move towards using durable goods and sustainability instead of infinite growth.
Lets steel man this idea.
Counterarguments:
- While the theory sounds romantic, what has been built in practice by bitcoiners are things like Mt Gox and FTX. Trading platforms that just serve financial markets, which is the very core of this infinite growth mentality
- After 10+ years, it's still generally not accepted as payment
- The energy required can't be ignored, especially in light of the above. I understand the benefits of replacing load banks, heating, and green energy, but there are more efficent ways to generate heat, and mankind's energy would be a higger percentage of renewables if bitcoin weren't using so much electricity. Even if using miners as load banks is 100% justified, that doesn't justify all the other mining operations.
- The theory that it's decentralized is wonderful, but on real life, mining is fairly centralized,
Help convince me (one way or the other) using evidence. Better yet, help convince a zero-coiner who is thinking these same things.
I want the arguments that really hit hard, not potential solutions. Not the usual suspects like "BitAxe wants to disrupt centralized mining". Yeah, that's great, and I support them, but until they prove they can do it, lets just acknowledge that this is a problem yet to be solved.
The same goes for the "Lightning is going to solve the efficency problem". It hasn't yet. #bitcoin is seriously easy to use. Lightning is not. Honestly, I feel that downloading a wallet is easier than signing up for a custodial lightning account, and if we're talking about self-custody, let's come back to that in another 4 years.
I'm sure some maxis are going to jump in and call me a fiat shill or whatever, and that's fine, I can ignore anyone who doesn't wasnt to have a constructive conversation. It's the actual discourse that I am interested in.
Give me your evidence that #bitcoin is just the ticket to eliminating the growth at all costs mindset.
RiseUp.net
If you use it, please do donate if you can.
I use cloud-init to set up authorized_keys when the VM is created. Among them is an entry generated for this specific deployment.
After I connect to what should be my VM over SSH, I send it an encrypted one-time-use token that it can use to have the CA sign it's SSH host key.
It's symmetrically encrypted using that SSH pubkey as the password. So if it's my VM, it can be decrypted. If it's an attackers VM, it can't.
Once the host key is signed, I remove that extra SSH key since it's no longer needed.
I had someone else look it over and they didn't find any flaws in the design (or implementation for that matter). It's a little awkward, but highly effective, and it uses only technology that exists now.
This also works for deploying the CA server itself, even on the initial. Anything that needs to be secret gets encrypted with that public key. If I can decrypt the public CA certificate, then it must have been generated by my server and not an imposter.
If I am restoring the CA from a backup, only the legitimate server can decrypt the CA private key. So the same trick works everywhere.
After you spin up a new VM in your cloud environment, how do you know you're connecting to the right machine when you SSH in for the first time?
Unless you manually verify the SSH host key's fingerprint with what you see on the console of your VM, changes are good that you don't. It's just trusting that there's no hijacking traffic with DNS, ARP, or elsewhere.
I devised a scheme to automatically be sure I'm connecting to the same machine I deployed. And I just saw it work in practice! 🤓