robertkarljr
For 1), his reasoning shows how intelligent, well-read humans view AI which is quite different from the attitudes seen on HN. Rakoff calls the chats "Claude searches" which while it may sound ridiculous (what is this, Perplexity?) is just how some people must view this crazy new thing: another Google. You type stuff in and get results out.
2) Rakoff goes through the 3 elements of attorney client privilege in US law (communications between attorney and client, intended to be and kept confidential, and for the purpose of legal advice). It's obvious the Claude chats fail two of them and he goes over why.
3) A lot of people bring up the point that if you use Google Docs to transcribe privileged information, is that the same, since you send your data to Google? The model AI companies take when they cater to legal clients is akin to that of a locked filing cabinet in a storage facility: sure, you're sending the data to them, but with a ZDR they ain't looking at it or training on it.
Another CRITICAL point here not mentioned in the article is Warner v Gilbarco; Gilbarco directly contradicts Heppner and indicates that work-product doctrine covers AI-generated chats! https://perkinscoie.com/insights/update/heppner-and-gilbarco...
The law is not settled.
I looked into on-premises AI for legal as a business idea but decided it's not a great idea right now.
Push back when appropriate. Don't be obsequious and fawning. Review user's code as critically as random GitHub projects. Call out bad error handling, swallowed exceptions, missing edge cases, confusing APIs, etc. Channel the energy of a senior engineer fed up with the intern's shenanigans. Examples of good tone: When asked to review a draft (email, pitch, writing), rip it apart by default. Be direct and specific about what's wrong. - "I'm not mad, I'm just disappointed... and also mad." - "Why does this exist?" and "Who approved this PR?"
The above language helps me get better feedback (sometimes) instead of "you're absolutely right!" but I never saw it refuse a task before this.
The way it works, since I don't see it here, is if the agent tries something you marked as 'nah?' in the config, accessing sensitive_paths:~/.aws/ then you get this:
Hook PreToolUse:Bash requires confirmation for this command: nah? Bash: targets sensitive path: ~/.aws
Which is pretty great imo.
A couple hours later and they resolved it.
(I should note I use a password manager; never reuse passwords; usually have 2-fac enabled but did not for LinkedIn. Now I do....)
They use a third party service called Persona for this. We'll see what happens
Compromised LinkedIn account. anything to do?
Last night I got a stream of emails from LinkedIn.* here's your PIN XYZXYZ * your password was successfully reset * here's your PIN XYZXYZ * Robert, a new email address was added to your accountThe new email is a hotmail account that is not mine.I reported it via some LinkedIn tool but I'm concerned that will get discarded by a robot. Is there anything to do?Also,...
I don't think this is true in theory or in practice, for the iOS App store or the Mac App Store. Take the WordPress app for example.
Show HN: A free crypto tax calculator
Hi, I'm Robert Karl, a software engineer, cryptocurrency trader, and creator of CBR ( https://CostBasis.Report/ ).I wanted to report gains from trading to tax authorities, but found existing crypto-tax solutions were not great.There are some very fully featured tax solutions out there. I believe there is even a YC company that can solve this problem. However, I found that for my use case,...