“Hmm, this immutable system, container approach to the Linux desktop that the Universal Blue/Bluefin folks are doing sounds interesting. Let’s give it a try! I’ve got a spare SSD, it won’t mess up my main Windows install,” he said unaware of what’s to come.
Little did he know the devil BitLocker was sitting idly by, just waiting for the opportunity to deny him entrance back in.
“What’s that?”, BitLocker says with a grin, “Oh, you mean you don’t know your recovery key? Only your system administrators do, who are skeptical of Linux in the first place?”
He looks back and forth, the rears his head back and lets out a big belly laugh. “Well now! This certainly won’t help your case now will it? What did you think would happen? They know all and see all.”
I may not be able to get back into Windows at the moment — that’s going to have to wait till Monday when I either get the BitLocker recovery key or I just wipe and re-image it — but I’ve got my Bluefin/Aurora based Linux humming along pretty nicely.
Layered on my preferred terminal, browser, and password manager so they are all playing well together. Dotfiles and applications are installed and my typical dev environment is working damn well.
I want to play around with the containerized toolbox approach that this type of Linux setup enables and see what CLI tools and applications I can use that way to kick the tires on if all of this is even worth it.
It’s been such a breath of fresh air to work with too! Especially compared to my standard windows with WSL2 setup. I’m grateful that it let me use the OS and tools I’m comfortable with, but I forgot how bad the perf hit is to that approach.
Though part of that could be the heavy handed CheckPoint software mandated by the security team. My >2 year old laptop with an i7 and 64GB of RAM frequently slows to a crawl over in Windows land. But the past couple of days it’s been downright snappy.
Couldn’t sleep this morning so I game planned a new Django package based on how I’ve been confguring my published apps. After a while, I did a quick google search and realized I had basically reverse engineered django-appconf (at least the surface level API).
Got locked out of my Facebook account. First attempt at uploading my ID didn’t work, next up this dystopian level shit where I have to record myself holding up a code and proving I’m not AI or a deepfake.
Did the video, got back in to my account. What's concerning is I had 2FA enabled. Did someone actually breach my account? Or did they spam login enough to cause this grief?
What's fun is I went to update my 2FA just to be sure, but because I haven't used Facebook in who knows how long they won't let me set up a new one until I've used this device for a period of time. How long? "A while"
They sure let me delete my old 2FA before telling me that though! Now I'm extra secure!
Wrote a cursed custom Django field, OPField, that stores the location to a 1Password item using their custom URI (op://…) and has the ability to get the secret via the op cli.
op_uri, secret = OPField.with_secret()
I blame @CodenameTim and his blog post about the RegisterField that I haven’t been able to get out of my head since he wrote it months ago.
I guess I get what I deserve for complaining about django-stubs, after creating a package that dynamically adds fields to a model and trying to figure out how to support type hints for it 😬
@carlton But in all seriousness, it's a field that adds an additional attribute to the model using contribute_to_class -- https://github.com/westerveltco/django-opfield. I'm sure it's possible, I just need to dig in to how django-stubs/django-types adds things like the additional attrs that DateField or ForeignKey adds to a model. (Though TBH with those libraries in practice, I've never been able to feel like I've gotten it nailed down, so maybe it's a fools errand.)
So easy to get caught up in the churn of typing, so hard to stop yourself when it starts to become the problem you are solving instead of the thing you actually should be working on.
Or at least my stubbornness makes it hard to stop - “I will not let this tool get the better of me!” 😅
What’s that saying.. you can’t truly love something (language/framework) till you see all the skeletons in the closet? I don’t think that’s it but you get my drift 😄
I don’t know why I woke up this week and chose pain aka trying to nail down some typing problems that have been a thorn in my side for a while, but I did.
@carlton One of the benefits of Python is that it all ultimately doesn’t matter at runtime, as long as you have a robust test suite you trust. I just wish it wasn’t so painful. IMO it’s worse than everyone’s favorite bugbear — packaging.
@carlton I also hope this doesn’t come across as complaining about all the hard work that has gone into getting us to where we are now. Lots of people smarter than I am working voluntarily… I admire the hell out of every one of them.
