Yes, throw that "spyPhone" into the ocean immediately!
#grapheneOS then is your next step...
My darling Mr Muscles nostr:npub1uense4apn73tvh4u20tzlp6u72g4kdustzsm0k0sqy6yuwh5jxlsy97y76 has picked nearly 30 lb of pecans, which I have now toasted. The kitchen clean up can begin after being tied up in limbo for too many days. The yield is amazing. Maybe a lb of nots (as opposed to nuts), and more than a 5 gallon bucket of shells for our compost heap. 
Nothing better than pecan pie... 😃
So this is perfect--and what should happen.
We find a bug, and it's now opening up a great dialog on potential ways to improve Nostr and the log-in / account creation and maintenance processes.
"Making a mistake is a gift...you now get to fix it AND make things better!" 😃
Love this thread!!
Agree...(in theory).
How many times to devs pull from a library of "trusted" code, only to find at some point in the future that "oops, we found a bug in library x"...
Often it's no one's fault--but it happens.
So modular applications / libraries come with potentially even a greater risk... 😃
Well, there's the rub...unless you go in and review the code yourself, you must end up trusting others...
And when someone like nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn posts "hey, we have an issue" I automatically trust that developer even more.
What I *really* worry about is dishonest projects / developers, and you see it all the time. Someone releases an app on the Play Store that does something nefarious...happens more often that most realize.
And look at all the data breaches out there--those are code mistakes that ARE audited (heavily) and still they happen...
Agree...I use "browser isolation" for most of my surfing, where I use different browsers and different extensions for different purposes (e.g., I only sign into Google on Chrome, and I only surf using Chrome at websites that I'm ok with Google knowing about). I can envision doing something similar with Nostr...
Nostr is so new, we're still on the bleeding edge--things will evolve and get better...
Right now we're driving Nostr's "Model T" - transformational at the time, but quickly evolving as technology and development leaps ahead...
Just wait until we develop the twin-turbo V8 Nostr apps... 😃
Ah...ok. (Not a soccer guy, but I do recognize it's got quite a following).
It's kind of like ice hockey, but not as fast, and you don't get to hit people with a stick. 😃
Your last sentence is important--what you're really asking (or assuming) is that we can "trust" the code more in signing extensions (and frankly that may not be the case).
This is one of the weaknesses in the open source community. We all assume that because the code is available to all, it's "good".
But what really happens (in more cases that we might want to admit) is the only "audit" the code receives is from the original developer--I'd even dare to say that most projects out on git hub probably receive very little (if any) code review prior to being released.
Not necessarily...there's nothing that ensures remote signers and extensions don't have similar issues...
This is how bug should be handled--openly and honestly.
Kudos to you. 😃 We all make mistakes...we're not God, and while we try to be perfect...well...
And (frankly) at some point everyone on Nostr needs to understand their nsec is effectivley not private, as AI will be able to dox any of us (so long as you have enough posts to begin developing a "profile"). Sorry, but it's true...
In fact, I've been thinking that perhaps a good practice would be to abandon a profile (nsec) periodically and start over...thinking about how that might (or might not) help...
Regardless, nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn you've gone up a few notches in my book.
Thanks for all you do, and for updating us.
footy?
Bunnies are always a bit too skittish out here...not sure why. But they do enjoy carrot peels...but "Just leave them over there please, I'll eat them in a bit once you leave"...
For hardware? Absolutely.
Better security, lower price.
And then #grapheneOS on top.
Seriously, think of it this way--you load Linux on someone else's hardware. AND that hardware comes with a base set of requirements needed by Linux in order to function.
To meet the security requirements of graphene (which is why most of us want to use it) most hardware manufacturers devices don't meet that specification.
If you want to have a less secure phone, you can certainly load #lineageOS that works with multiple hardware vendors.
But why would you want to do that?
If you're going to break away from Apple and Google, wouldn't you want to use the very best and most secure hardware out there as a starting point?
GM Nostr!
Happy Friday!
Hope everyone is teeing up a great weekend. I recommend half-days on Friday! (Best way to do that is to put in one extra hour each day M-F).
Oh--and turn off your phone at noon on those Fridays (or it'll still bother you).
Time for some coffee and zaps!
#coffechain
(Do we have a #zapchain?)
So...next time you need to upgrade your phone, switch to Google, load #GrapheneOS and you'll (finally) be free! 😃
(And you'll spend a LOT less than upgrading that "spyPhone")
And to think we'll likely never change that "save" icon as it's now an ubiquitous standard...
A tip 'o the hat to history...
Looks like FreeCAD might be my best choice to start. OpenSCAD seems more programmatic and less visual...might move into that though later (as I can see the benefits). Just need to get started I think...
libreCAD is 2D (no?) so again maybe a bit harder to visualize a 3D model from that for me....
Hmmm...this is helpful. Assuming you use some kind of CAD program? What would you recommend? (I use Linux exclusively)
What CAD software would you recommend? (Only running Linux, so would have to work on that platform). FreeCAD seems like an option, but just starting to investigate. Any opinions welcome.
(Thinking of the Bambu A1 to start off...)
I'm primarily looking at PLA--SLM and DMLS (or even the toxic resins) would be well beyond my current budget...