The entire premise of Galt's Gulch is essentially this whole concept of "companion planting", where every Producer had a moral responsibility to create and grow a thriving ecosystem that worked together.

Dagny built railroads. Indigenous wisdom teaches us to build life roads, connecting us back to our own inherent nature.

Dagny was a Producer - a giver. That to me is very much the essence of Indigenous wisdom: create abundance. It is our moral responsibility to ourselves, each other, and the Earth.

And I very much resonate with that.

Simplex > Signal > Telegram 🫡

Companion Planting

In Indigenous land wisdom, there are 3 Sister plants that, when grown together, help each other thrive: Corn, Beans, and Squash.

Corn grows strong and tall. Beans twist and wind up long stalks, reaching for the sunlight. And Squash keeps the soil covered, protected and moist.

This is the holistic and integrated approach to planting. Creating a microcosm within a greater ecosystem.

Nature does not work alone. She has made puzzle pieces that fit together to make a whole.

-----------

Our people systems follow the same principles.

We need to thoughtfully plant ourselves with people, partners, teammates who help us grow and thrive.

We tend to our relational Social Soil when we build trust and find the symbiosis that allows us to help one another grow to our fullest potential. Which also requires us prune, weed, water, compost, harvest, and rest our relationships.

Order and harmony are not neat and tidy. In Nature, harmony looks messy but is a deeply complex system that has found equilibrium.

The best thing you could do today is to tend to the garden of you and yours.

Compiling dependancies is fun. You should try and install nix-bitcoin with all the features turned on. That builds the dependancies and runs all their tests. Many hours of the fan creating white noise.

The ESP32s are really neat and there's definitely some hardening that can be done with the secure boot, signed firmware features.

Key delegation with an expiry time would be really nice! Good idea.

I don't have any SE experience on ESP32s but from the research I've been doing, you're right, the ATECC608B can't do schnorr sigs. The Coldcard uses this SE and it is compatible with taproot so I'm wondering if there's a way of working this. Either that or CK are using the DS28C36BQ. I need to research more.

From 1996. Inflation gonna inflate.

You touch on a key aspect of the problem: while Vitor was able to make editing possible for Amethyst users, other clients do not see this edit. If Vitor added blocking so that blocked users can’t see your posts, that’s fine, but Vitor can’t control what damus or primal users see. You can’t stop other people from seeing your posts unless you don’t post them publicly.

rights aren’t given, they’re taken.

bitcoin and nostr help you take and defend them, peacefully.

So yeah, this sun thing.. pretty sweet 🌞🌱🦜

Just gonna sit in it for a while, the other stuff can wait.

👀

nostr:note1x0lkjpgvyf4htx4js04240ehlalwwrzcwrslwze5jwsj2np2va0qyq88f4

P2P all the way.

“40GBASE-T”

Is this fucking real

…

What the fuck

You do not need to trust me.

Maybe except for paying for my services but that’s it.

Has anyone used an ATECC608? The Adafruit breakout board looks handy.

There are (at least) two quite different problems here:

1) how do I decide which version of a dependency version I should use? Many projects trust package management tools (yarn, cargo, etc) and centralised repositories (crates.io, etc) to serve them the most suitable hashed state via commands like `yarn update` and `cargo update`. To what extent are these states signed by the dependency's maintainers and to what extent are these signatures validated on the developers machine across language and package management ecosystems? I'd be interested to see some analysis of this.

2) how can I download a specific version of a dependencies without relying on a centralised entity (github)