lol, I just assumed this was a reference to the old workflow for bypassing code-signing on OS X, which was you had to click 'Cancel' in the popup then right-click and select "open" (no indication in the UI that this did something different than double-clicking).
I'm like you, and a big fan of Pigallery2 precisely for its simplicity. But it turns out that Immich does support external libraries, so you can keep your manual file management in your filesystem and still use Immich for efficient indexing, face recognition, quick picture retrieval by year, location, people etc...
I'd recommend you try Immich (there's a docker compose version) and if you don't like it, you can just remove it and move on.
> If there's one that I really need to be on, I'm going to spin up a VM on my computer so that it has no idea of the other files laying around, such as my ~/passcodes.csv. If you are such a negligent bullhead as to get me onto your call, you'll be unable to see me because my VM cannot access my camera! By design! Same for my microphone, so I'll plug in a USB mic if I really need to speak up. More likely than not though, I'm exhausted by now. I'll spend the full duration of the call eeking a small echo of pleasure from the continuation of this rambling alarm, for your sheepish audience to rub their enablist shame in.
This is written in an edgy tone but it's pretty much SOP with QubesOS. Why would you install _anything_ in your main VM? Not just Zoom, but anything you import in a deep dependency graph can access your figurative ~/passcodes.csv anyway.
furthermore why would you give ~/passcodes.csv access to ~/nuke_launch_codes.csv and ~/incriminating_evidence.csv let alone connect the computer they are on to the internet
I agree with Dijkstra on this one: “The question of whether a computer can think is no more interesting than the question of whether a submarine can swim.”
I really wish all these LessWrong, what is the meaning of intelligence types cared enough to study Wittgenstein a bit rather than hear themselves talk; it would save us all a lot of time.
Serious question: can you point out some serious complaints? They seem to have an exhaustive justification for their reasons to only support Pixels, see https://grapheneos.org/faq#future-devices
We would happily support other devices meeting these requirements and have limited what we include in the requirements to enable that. We're actively working with a major OEM towards a subset of their devices meeting these standards and providing official GrapheneOS support.
It's not our fault that the only other devices providing the security features we need don't allow GrapheneOS to be installed or to use those features. Massively lowering our standards and using low security hardware missing the basics we depend on and have built major protections around wouldn't make sense. It's not what GrapheneOS exists to provide. People can use LineageOS if they don't have the same priorities we do.
This list always bugged me. If Pixel - for example - starts to introduce security patches slower, they will change this list... or even ignore it. If something more secure comes into the picture, they will change this list, and they will ditch supporting Pixel. If they don't, then it will be quite obvious, that they formed this list only to meet only Pixel's feature list. Also Google can obviously satisfy this list more easily, than any other company, so basically they created a moot for them.
We haven't removed any requirements from our list. Many things Pixels provide are omitted from the list in order to enable another device to meet our requirements. There are other devices meeting the security feature requirements, but they don't allow us to support them. We're actively working with a major Android OEM towards a subset of their devices meeting these requirements and providing official GrapheneOS support. Providing the requirements on our list is not easier for Google and any OEM should be able to make a Snapdragon device meeting these requirements in 2026. It's already possible to meet all the listed requirements via multiple non-Snapdragon SoC platforms, but we'd prefer the upcoming Snapdragon generation with MTE support. The list has been deliberately kept limited to what is provided elsewhere than Pixels so that other devices can meet the requirements, which is in the process of happening.
Main work: tokenization of real-world assets, but on the side I’m building two projects as a solo dev:
- XRoll.io — a fully on-chain gaming framework on the XRP Ledger, inspired by SatoshiDice but built for compliance. Commit-reveal fairness (HMAC_SHA256(secret, bet_txn_hash)), full transparency on-chain. Integrated KYC, AML, self-limits at the protocol level. Frontend is optional; ledger is the source of truth.
- Nexula — an evolutionary image generation system. Embeddings extracted with CLIP, clustered via HDBSCAN, visualized with UMAP. User behavior (time spent) drives fitness scores; top samples recombine through weighted interpolation to generate new images. Built on Django backend, session-based personalization without login.
Looking for like-minded people interested in exploring both the technical and business sides of these systems.
I can also recommend Trilium Notes [1], which I have been happily using for years. It's currently in "maintenance mode", which I personally see as a feature (no risk of bloatware).
Self-hosted, great webapp, optional native clients and works offline.
If you're using print debugging in python try this instead:
> import IPython; IPython.embed()
That'll drop you into an interactive shell in whatever context you place the line (e.g. a nested loop inside a `with` inside a class inside a function etc).
You can print the value, change it, run whatever functions are visible there... And once you're done, the code will keep running with your changes (unless you `sys.exit()` manually)
In case you're wondering like me, this is the advert in question: https://www.youtube.com/watch?v=8CwoluNRSSc&t=0
reply