ImgurRefugee114

I love grapheneos. Fun fact: I frequently swap my real and duress pins. I don't mean rotate. I mean swap. I've nuked my phone several times by accident just because I forgot what one was what at a given point in time. Think of it as disaster recovery validation; gotta regularly test your protocols otherwise they're useless. It's best to test under live circumstances I think, and without foreknowledge. Yep. Just part of the plan. Definitely didn't do it on accident twice and then decided to stick with it for the memes. The best part is that it gives me excellent plausible deniability. The worst part is I routinely lose my contacts list because I'm an actual idiot.

I think there's a distinction to make between a burner phone and number but yes that's still relevant

Yeah, that would do it...

I recently made a lua framework that constructs callable tables to be used as functions that take a table as a dictionary of named argument. The function declares a schema of parameters with associated required/default/optional policies that put their respective values through a transform and validation pipeline. A similar pipeline can also be put on the result to make explicit guarantees. Can also configure whether argument errors/violations should throw or return results,error shape

The wrapped function recieves a table of processed arguments in a known state, while keeping that noise separate from the business logic. Also configurable at runtime with introspection, and param pipelines are immutable so they can be composed.

If that sounds like it introduces a lot of overhead, you're right! But 1) it's Lua and 2) omg is it so worth it when used properly. The UX is great; the callsite ergonomics, maintainability, and self-documenting nature is always what I felt was missing. Ships with & plays pretty well with type annotations too.

Anyways, that all makes it really convenient to know what's responsible for what, and encourages pretty safe designs.

It's not a glass, it's the

hydrationContainerManagerObjectFactory

Not to be confused with the

hydrationContainerManagerTypeFactory

Which is the template

No, not to my nixos configuration. In fact I don't even have a global / system / user-wide Python interpreter. I rely on nix shells and package closures; no imperative use of python.

I'm not a big python dev; my meaningful experience is with systems languages. But for a release or project i intend to be consumed outside of nix, I'll use venvs and a requirements file because that's just the right way to do things.

But what I meant was that I'd use a nix shell or build package that uses py libs that are already packaged for nix, or package the ones that aren't myself, and just use the nix closure as my venv; no regular venv or pip workflow.

Devenv seems to let you just point at a requirements file and it builds the venv for you. Very clean for portability beyond nix consumers that way. But most of my Python projects are personal utilities and can target nix exclusively.

Asinine

Yeah. Believe it or not, when I saw him last, he was leaning left.

Really proud of him for toning down the rhetoric. Guy hasn't said a racist thing since he last went viral.

... I'll be living in a bunker, if anyone needs me. Ring the bell twice when it's over.

Lots of things are, but the right doesn't usually care. In fact, they don't seem to account for reality much at all.

Okay I hadn't heard that before; I lol'd in the traditional meaning