Hacker News Reader

Comment by dvt | Hacker News Reader

I know it's a grey area, but I've started to really push back against this kind of low-effort reddit-style gotcha' posting on HN (especially on "Show HN" posts, which are meant to be—from what I've always understood—a safe space for creativity, entrepreneurship, and engineering). It used to be rare enough that we could just collectively ignore it, but it's been getting super bad in the last 2-3 years.

Also, your comment is just trivially unininteresting to begin with: what is "submitting," what is "private," what is a "privacy guarantee," what is a "crime"? It's just outrage slop. If you're a lawyer and have something substantive to say, please do so (and a lot of lawyers on HN do), but otherwise, Lincoln put it best: "Tis better to be silent and be thought a fool, than to speak and remove all doubt."

View on HN

I think OP's being hyperbolic, but defending an idea that is dangerous at worst and immature at best doesn't do much to forward creativity, entrepreneurship, or engineering. Engineers who build products that put people (or their data) in danger are bad engineers. We need to hold one another to a higher standard.

> doesn't do much to forward creativity, entrepreneurship, or engineering

Who are you (or who am I) to decide that? The entire point of a show HN is to be non-judgmental and charitable, otherwise it's just going to turn into a cynical echo-chamber. The famous Dropbox comment is a cautionary tale for a reason.

> Show HN: AI-enabled orphan grinder

> Person A: yo wtf is wrong with you

> Person B: Who are you (or who am I) to decide that? The entire point of a show HN is to be non-judgmental and charitable, otherwise it's just going to turn into a cynical echo-chamber. The famous Dropbox comment is a cautionary tale for a reason.

I could build the greatest healthcare tool in the world, but if it's not HIPAA compliant then it's worthless in the United States. More than that, if I built it without HIPAA compliance in mind as a first principle, what other mistakes did I make on the way?

I'm not trying to gatekeep and say that only domain experts should be allowed to build software, but part of being an engineer is doing due diligence to understand the domain well enough to build the product. If OP failed to recognize that any forensic accountant that gets caught uploading privileged documents into a random AI tool would be both breaking the chain of possession of that document AND client privilege, what other mistakes did they make along the way?

I went through the entire website and couldn't find a single mention about privacy. I'm not a domain expert, but I would expect the product site for any legal tool to at least have a disclaimer.

Fair my comment is perhaps a bit cynical but the point of it is deadly serious: like if one of the people involved in the mentioned divorce case finds out possible grounds for a mistrial/retrial. IANAL but I understand the restrictions the ACM puts on using LLMs for even paper reviews, which are far less sensitive than peoples private financial matters.

Regardless, I'm comfortable being a called fool.

Apologies for being a bit snarky, you're alright :)

Reply on news.ycombinator.com