AntonyGarand
Joined 9 years ago
Joined 9 years ago
You either should treat your passkeys with a backup like any data, this can mean multiple hardware keys or a cloud backup of your passkey, like bitwarden or the provider's native backups.
The current link is a 404, seems like they didn't redirect it properly.
an AI:DR; is enough: the models found unpatched vulnerabilities and managed to create an exploit to root the tablet, chinese models did it while American ones fell back to their safeguards.
While most of them would be pristine to a regular user, these small nitpicky details might matter to collectors and help differentiate between two of them.
Relevant read: https://news.ycombinator.com/item?id=48877371
> The practical takeaway for users: your entire codebase leaves (uploaded) your machine unencrypted on each Grok Build invocation, not just files you ask it to read, and no visible setting stops it.
While not all meetings need action items and summaries, having high level notes or the full transcript available when you actually get to implementing a task, or having an agent go through the dozen meetings you had on a project to identify its evolution has made finding and keeping knowledge up-to-date much better in my own experience.
It helps account for bias towards the most recent candidate in interviewing as you can now compare all notes, helps recall some niche details that were said in passing for projects, and holds everyone accountable to what they said.
I still haven't found a perfect solution to actually storing and querying this knowledge, single meetings are easy but wiki-fying them is my end goal, but I'm very happy about the direction dictation, transcriptions and AI parsing of all this knowledge is going.
https://web.archive.org/web/20260707202807/https://firespher...
[0] https://github.com/pingdotgg/ts-rust