The 4th Matrix movie was surprisingly just fine (I was expecting I'd give up on it in the first 30min).
Not nearly as terrible as #2 or #3. But it had no visual flair nor any of the intriguing, odd uniqueness that the sequels occasionally managed.
So kind of a weird stalemate: It's clearly better than the others, as a whole. But has absolutely nothing noteworthy about it.
IG links are weird when you trim the url params. Try this if the above jumps away.
https://www.instagram.com/reel/Cpf80BcNlgj/?igshid=YmMyMTA2M2Y=
~20sec handstand. Goal is to hold for 1sec for every year I've been alive (that's longer than you think!).
As a former English Composition teacher, I disagree. I liked the limitation and structure that threaded tweets imposed. Way better to force people to isolate/encapsulate each point in a concise 2-3 sentences.
Twitter allows essay-long posts now? Trash. 🤮
That would probably introduce enough complications to make an attack improbable, but I think someone could still get around it.
They could basically run your protected version through a secret internal emulator, pass the PIN you enter off to the emulator, and play back what the emulator produces.
This all being said, in most cases these exotic, sophisticated attacks wouldn't even happen; it'd just be a $5 wrench attack if they have physical access into your home.
Can't do TOTP if the device doesn't know what time it is! There's no Raspi Zero clock battery so it's the beginning of time every time you power it up.
There are a bunch of skills I could probably do **if my life depended on it** (and if I got like 3 tries) but that would be the END of my shoulders or knees or whatever.
But bouncy things from the trampoline into the pit? Wheee!!
Another bad idea: Someone previously asked if they could use one BIP-39 backup and then generate three BIP-85 child keys and use those as their 2-of-3 multisig.
😱
My preferred Uncle Jim solution is either:
* Just teach them (as we're all trying to do) and ease them into their own self-custody. But at some point they are off and flying on their own. If they screw up, they learn a valuable lesson. Too bad.
* If I really need to be able to bail them out, I'd maybe consider a 1-of-2 multisig.
But mostly I'm a "learn it + personal responsibility" maxi.
Yes, superhuman indeed! I didn't know you had that background! I wrote my college application essay on how Zen and sublime it feels to do a laid-out backflip.
The kid in the video is one of our senior captains. But he doesn't have a standing back because he's a PB specialist. We were like, "bro, you can't say you're a gymnast and not have a standing back!"
As a cautionary tale of what people should NOT do. Don't over-complicate your cold storage setups!
We added BIP-85 support to #[2] (and I even helped out on that PR) but I will never recommend it to anyone. Our UX (and my personal justification for including it) is more about verifying other BIP-85 implementations, but it's intentionally biased against promoting the resulting child seed to be a usable signing seed in the UI.
That makes sense. You'd think Chrome + macOS would be fine w/.mov since, afaik MOV only exists because of Apple! Actually, I guess the real test in that case would be Safari.
And as for ETA... Oof. Unfortunately my current fiat responsibilities are taking up a lot of my coding time, so progress is so much slower than I thought it would be. Haven't had the luxury of being full-time on SeedSigner since late last year.
However, some of the work I'm doing now in the test suite is actually helping to pave the way for the MicroPython code to move forward. And the next big push on the MicroPython side will/should/hopefully be a gigantic leap forward.
It's the best. All the most important life lessons that guide me as an adult were learned in gymnastics.
Our guys start as high school freshmen (~14yo) who can barely do a forward roll and then it's a race against time to see how far they can progress in their four-year high school career. The timing works out well for teenage boys. They almost never catch up to the level of fundamentals that the kids who started young attain, but it's an even playing field in terms of them maturing from boy strength to young man strength.
The basic plan is to use as much of the existing SeedSigner code as possible. So almost all of the walkthrough coding vids will still be relevant.
Only the UI/hardware-level code will be branched for Raspi dependencies vs MicroPython/esp32-S2/S3/etc deps.
Think biz logic vs rendering code.
Dunno. Chrome on macOS.
I wanted to find out how hard it is to manipulate the @SeedSigner
. It was easy as expected. Never give it out of hand! Simple swap to a manipulated sd-card and it logs your seed to it. Later the attacker can collect the sd-card and get your seed words.
Total lines added to the code are six.
Needless to say, it writes the seed also to sd-card if you scan your backup seed.
Yup. Python can do anything python can do (couldn't play the videos in Iris, but it all sounds right).
A lot of (er, all?) the onscreen security checks people occasionally ask for end up just being security theater since a compromised SD card can show you whatever it wants onscreen. Removing the SD card in the new SeedSigner OS def helps. And when the MicroPython port is done, there'll be firmware-level checks that will make "evil" SD cards much more difficult/impossible(?).