doh
Joined 15 years ago
Karma
3,627
Submissions
736
Member since
Apr 11
Recent submissions
Comment · 1 month ago
Welcome to the capitalism 101. Everything has price. So far, I would say, humanity done quite well under this _oppressive_ regime when compared with others.
Comment · 1 month ago
Anytime you use absolutes you paint yourself in a corner. Definitely not 100% of things that big tech "democratized", as you put it, has been bad for people.
Presenting it as such does disservice to any serious conversation.
Comment · 2 months ago
I am no Apple, but this is not a vigilante app. All it does is to encrypt user’s own files on their own devices. There are no servers, no backend, no snooping. It uses apple’s services (icloud) for backup and user allows it, error tracking to hosted posthog.
Comment · 2 months ago
Me personally? Nothing.
I added it after users asked me to solve their problem of being strip searched like this.
I know some people keep crypto wallet keys in the vaults. Someone else wrote me that they carry sensitive documents they don’t want to be exposed.
Comment · 2 months ago
100% I have built similar behavior in my [0] encrypted storage app for iOS. User creates a "duress vault" which is an ordinary vault that user can store any data they want (usually something very inconspicuous). If this vault is opened, it will wipe out all the other vaults silently without actually showing any sign of doing so and still preserving the duress vault's data. Even if snapshot of files is made, the index and keys are gone and can't be recovered.
Comment · 3 months ago
I was always worried about situation like this. Wiping out the whole device is easy to prove.
When I was designing my secure vault app for iOS[0], my approach was to make one of the “folders” (I call them vaults), to trigger the wipe out without any sign of doing so while retaining the data in the opened vault. It technically only deletes the index and the keys, and obfuscates them by replacing them with random bytes.
I already heard from a person that was forced to open their app but was let go, because they complied.
Comment · 5 months ago
I built a very similar server myself [0] with a similar setup. I run different models for different purposes, but the primary one currently is kimi 2.6. I run kimi as the orchestrator model and then qwen, Gemma and others for specific tasks (sometimes loaded dynamically based on the task at hand), all exposed through the pi harness. I also use Hermes for some personal repeated tasks which connects to the same models, hosted on my local Mac Studio.
I am not even going to pretend that this is financially reasonable option. I simply wanted to have a local models. Maybe down the line, as cloud models become less subsidized, I might benefit from having a local setup, but for now, it wasn't the most prudent financial decision.
But one big benefit is that I never have worry about my account being randomly banned nor I have to worry about running out of quota. I still use codex and opus for some specific tasks, but as tools are improving, I need them less and less.
Comment · 5 months ago
I have built something like this and in process of collecting the data.
Frontier users: 527,865 Light indexed: 527,865 Ready to queue: 9,083 Fast scores ready: 0 Activity events 24h: 30,266 Fast scores completed 24h: 19,123 Deep jobs completed 24h: 3,043 Fast-score ETA: n/a Deep-hydrate ETA: 69h Stale running jobs: 0 GitHub backpressure jobs: 19,113 High automation signals: 4,608 Medium automation signals: 1,327 Completed jobs: 74,714
Biggest challenge is Github's rate limits. At this pace it will take two more months to have 98% coverage. But after that the maintenance should be quite straight forward.
Comment · 6 months ago
I don't want to defend LLM written code, but this is true regardless if code is written by a person or a machine. There are engineers that will put the time to learn and optimize their code for performance and focus on security and there are others that won't. That has nothing to do with AI writing code. There is a reason why most software is so buggy and all software has identified security vulnerabilities, regardless of who wrote it.
I remember how website security was before frameworks like Django and ROR added default security features. I think we will see something similar with coding agents, that just will run skills/checks/mcps/... that focus have performance, security, resource management, ... built in.
I have done this myself. For all apps I build I have linters, static code analyzers, etc running at the end of each session. It's cheapest default in a very strict mode. Cleans up most of the obvious stuff almost for free.
Comment · 1 year ago
I am in SD and would love an invite. I am keep thinking about uniting more like minded people for a while. My email is [email protected]
My most recent projects: - vaultaire.app - iOS vault for photos, videos, and files. Pattern-unlocked AES-256-GCM encryption. No account, zero-knowledge. Even we can't see in. - pdfpix.com - Set of PDF tools operating strictly in the browser. No accounts, no limits, no risk of loss. - gethasp.com - Local secret manager for AI coding agents. Hands encrypted credentials to a process for a short window, then takes them back. The values never leak.