Is this the day's outline for WEF plans, or at least the plans they want us to see?
Gm #nostr.
Didn't make it to the river yesterday, wife was too hungover. So maybe today!
Gn #nostr. Y'all badass mofos.
I'm reading all of the NIPs. After getting through the first dozen or so, I am so hyper-bullshit on Nostr the protocol. Simple genius.
Yeah, nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg is send only for now. My goal is to have epic in-bound liquidity by the time they implement that 😅
If you have Strike, you can use your strike handle to receive sats, or use strike.army. but alas, Strike is custodial if you leave them there.
Gn boho 🌜
That goodness doesn't justvstay here, we take it with us wherevervwe go. 🫶
Can't send you zaps yet, says you aren't set up to receive.
I rode my motorcycle again today.
Missed a gear and had to stop on the way up the hill. Good for me, was able to stop and start safely on the hill without stalling.
Every day I am learning to ride my motorcycle. 🏍️
And today? (Saturday)
5 eggs (cooked in butter & lard, pepper)
- normally I put some shredded fiesta blend cheese on them, but my tummy has had some irration after eating them rhis way lately, so I didn't today, and no irritation. This aversion to cheese started when I had covid in January.
Milk (4-8 oz)
Top sirloin (wife made), maybe 16oz
Steelhead (wife made), ~8 oz
- my wife over-seasons, over-salts, but she is really trying to help me on my path, and I appreciate it.
That's it. Coffee and water. May feel cute and have a few bites of cheesecake later!
Gn Stella 🌜
I think that is my struggle in a nutshell, I tend to either be verbose or dense.
I believe training is implicit in anything we attempt seriously. I'm not a published writer (simce my high school newspaper), and writing isn't explicitly part of my current fiat job responsibilities (outside of writing professional emails and other customer and internal communication).
So if I am to pursue technical writing as my value add, I will need to train and improve. That is all. Right now, reading advice articles on writing good PRs.
I almost bought a domain last night. It would have been for a product I would never create, because I don't really create products. I think it might have been an affinity play, being able to flash a domain that sounds nostr-y.
But that clearly isn't what I need.
I think Nostr is making it clear that I like writing, and thinking, and explaining, and writing about what I'm thinking and explaining.
I've never trained as a writer professionally. I've been poking around at it a little over the last few years, I tried a Medium blog. I think I ran out of material to cover pretty quickly, and I was spending as much time sorting out the art as I was writing my articles.
Apperently there may be a need here to write NIPs, PRs, even just documentation. Maybe here is where I could be of service.
I think it is something I could learn quickly, and improve at with some simple pointers and feedback.
Maybe I just found my own product market fit - for now.
Wow, great observations! 100% agree with this assessment. Who mad? Nervous just means you care enough to question.
Don't fall into paralysis by trying to design the perfect system on the first try. Make changes, try things, test things, break things.
Slow improvements. Money is boring, remember?
This is actually a really important point that most novices probably don't really understand.
The addresses where Bitcoin are sent are derived from your private key (or more than one private key) However, they are derived in a way that does not reveal your private key.
Your seed phrase is also derived from your private key. But it is derived in a way that can be reversed, so your private key is encoded into a seed phrase, which can be decoded into your private key.
Taking an address from a bitcoin transaction, you are not able to use it to derive a private key, or to derive any other addresses that may be able to be derived from your private key.
You can make assumptions about related addresses, based on transactions between them, and even more assumptions if addresses are used in multiple transactions. This is why many privacy-minded folks try to NOT re-use addresses.
If you use a coin-join or whirlpool or ither coin mixing service that moves your coins from one address to one or more other addresses, it doesn't really matter if those addresses are derived from the same private key(s) or not, as long as the addresses are new.
If you are trying to remove the KYC stink from your transaction history, and build the story that those KYC coins are no longer under your control, and you accidentally dox an address that you used previously in your hidden wallet by sending some KYC transactions to it, you can send the contents of that wallet back through mixing to new addresses under your same private key. You haven't doxed thr private key, or any other addresses derived from it.
I had this scare once when I accidentally withdrew from Strike to the wrong wallet. It was to a new address, though. Took me a long night of thinking to realize I was fine. My only danger would be combining that utxo with other utxos in my secure wallet when creating future transactions, so I just swept that utxo (by itself) into a new address of the wallet it was supposed to go to, where I normally collect KYC withdrawals.
How did I learn all this? I largely credit Sparrow Wallet, which separates a lot of this stuff out and shows you a lot about how everything works and the steps involved.
Yeah, but compromised - maybe you accidentally (or ignorantly) mixed kyc coin with non-kyc coin in your multi-sig. Maybe one of your storage locations is sketchy.
And why not dispose every so often? Let's challenge that belief.
Really thinking hard about things I've kept or remembered for 30 years.
Ok, been chatting about bitcoin wallets, and here's a UX problem.
Let's say I moved my bitcoin off exchanges, now on to the later stages of diamond hands.
I then backed up my seed phrase on steel (plates, washers, whatever).
Ok, now I want to make a change. Maybe do some coin joins, or switch to multi-sig. Now I have a problem, I'm going to need to save another seed phrase. Even worse, that seed phrase in steel? Not needed anymore.
How often would you want to do this? Buy more steel. Stamp more. Test.
Consider that password hygiene includes changing your password. Shouldn't seed hygiene be similar, sweeping or joining to a new set of addresses under a new private key?
Not sure how to approach this. Maybe use a TOTP? Base the address off of something else entirely? Encoding a phrase as RGB values and storing it in an image is interesting.
I might spend the weekend thinking about how I would store anything for a long period of time, but be able to update/change it easily whenever I want.