Proofs are useful insofar as the formal specification is sound. The problem is that building a sound formal specification is the hard part, and it's not something that LLMs are going to be particularly good at. Yes, they can write a formal specification. But, is this formal specification sound? Is it usable? Is it applicable? Is it complete? This all requires human level reasoning and perhaps beyond to verify.
Once you have a sound formal specification, building proofs that software follows this specification is actually fairly straightforward. LLMs aren't doing any magic here.
In my experience, LLMs are surprisingly good at it. Especially transforming user-visible promises (like "all transactions are replicated to three nodes before being acknowledged") into high-quality specifications. I'm not entirely clear on what it means, specifically, for this transformation to be sound or unsound. What definition do you have in mind?
What have you tried that isn't working?
Completeness is harder, for sure. Maybe not tractable, especially in context of the whole universe (which is a point OP makes). Applicability is pretty easy - it's a NLU problem, and we're pretty good at those so far.
I can give a real-life example. WPA2 was formally verified at the protocol level, but the formal specification -- while reviewed by multiple humans -- was flawed, which directly led to the KRACK attack.
The Needham-Schroeder Public-Key Protocol failed to include the responder's identity in the protocol, which led to a man-in-the middle attack found via model checking. This is despite numerous proofs -- some even machine-checked -- of implementations against specification.
When cryptocurrencies had their formal methods moment a few years ago, there were numerous vulnerabilities and attacks found in cryptocurrency protocols despite claims of being formally verified, and despite much of this verification being published in Rocq, Lean, etc. If the specifications are unsound or flawed, then the implementations will also be. While in these cases, it's quite clear that the folks performing the formal methods work were likely inexperienced, I don't see how an LLM will create anything more sound.
Remember that an LLM is trained on publicly available information. It's not going to make a leap above and beyond what has been published openly, and much of what has been published with respect to security is related to student projects (e.g. "Let's build a formally verified AES implementation") or one-off applications, some of which, like WPA2 KRACK, have incomplete specifications.
This is a difficult problem that experienced proof engineers get wrong, after performing rounds of threat modeling and review.
It's not just a matter of competence: it's a matter of knowledge, experience, and tenacity. Currently, frontier model companies are trying to tackle the problem of their models writing potentially unsafe software by demonstrating that their models can build formal proofs. However, someone who lacks formal verification experience, the domain knowledge to make such software safe, or the understanding to combine the two into formal specifications will build bad proofs, because the formal specifications will be unsound. LLMs don't necessarily improve this outcome. An inexperienced engineer, with or without LLM assistance, is just as likely to not add a property to verify that nonces aren't re-used as the WiFi Alliance.
WPA2 wasn't designed by a single individual. It was designed by a committee of people including respected cryptographers and information security folks. They missed the fact that nonces could be re-used in the design, and they trusted the formal specifications that lacked a check on nonce re-use. It happens. Unfortunately, formal specifications tend to trap folks into a sense of complacency. Soundness is a hard problem, and if it's not solved, folks will make bad assumptions. "But, it's been formally verified..."
Could LLMs accelerate tactics and Curry-Howard level hole filling of specifications? Absolutely. But, they aren't likely to do much better than humans at building sound specifications. This is a difficult problem, for experienced humans with a narrow specialization in formal methods.
The flaw exploited by KRACK was not in the proof. I thought that was obvious.
It's that a key property, that a nonce (a number only used once) was never reused, was never stated. So that property was not proven, and in fact, was false.
It takes one line of specification to state the nonce invariant. It is beyond incompetent to leave it unstated.
Once stated, any proof would have to also satisfy that invariant (and the existing proofs would, of course, fail since the current design does not prevent nonce reuse).
It's difficult to speculate about the future. We don't yet have the right kind of hardware -- whether it be performance, scale, etc -- to simulate the kind of synthetic intelligence necessary to outpace humans at reasoning.
It's not a matter of constructing proofs. This can be done via brute force with appropriately managed search trees. LLMs actually are not much better at this than other ML or search techniques; it's just that in practice, that's not what proof engineers have optimized for.
Building a sound specification, that as erichocean pointed out, would include measures to prevent nonce re-use, is a much more subtle and difficult thing. You can prove that software is correct with respect to a specification, but there is nothing beyond proving internal consistency, to verify that the specification itself is sound, complete, or appropriate. This is an open-ended problem, and one that humans have difficulty with. I don't think that any synthetic intelligence is likely to do better, because it can only do as well as the vetting of information provided to it, and it is very likely that this information will be flawed and incomplete. LLMs try to fill in the blanks with plausible things, based on their training. Even humans make assumptions. These assumptions are sometimes wrong.
Regarding proof automation, this is actually a double-edged sword. I can build systems today that will perform various optimization techniques to try to get further into a proof via tactic search, and will eventually converge on a solution. However, the tactics will be a mess, much like the 1600 pages of tactics in the OpenAI NS proof. A good proof engineer builds specifications and proofs that other humans can read and understand. Even the tactics are organized around what can be explained, so that these can be hand checked. If you're building proofs of software, you want auditors to be able to look at these as well as the specification to see if you are missing something, such as a nonce re-use policy.
In this case a reasonable conclusion would be that there are no sufficiently competent people and we should act on that basis. Or, at least, that we have no reliable way of marrying sufficient competence with the right problems.
Well yes, but this case is specifically about a time when the right thing wasn't tested for, because the team of wise, talented people attached missed it.
I think OP is referring to more of a fundamental problem that a spec has to be written down, and if it's not then AI is just guessing. Often it makes very good guesses, but it can fundamentally never solve the problem of producing a complete specification when the user hasn't got a "complete" picture in their mind.
In my own practical experience this is now what software development is about. If you can specify what you want, AI can implement it. But specifying it is actually very time consuming and hard.
In a sense every prompt you send to an LLM is a specification. And its tedious to write all those prompts, I feel. You have to be very precise, and also write it all into the prompt. And even then answers I get from the LLM are often lacking so I have to prompt again, and then often the LLM replies that it now agrees its previous answer indeed was wrong or inapplicable.
One obvious issue is that an LLM can claim it has formally verified your spec, only for careful inspection to reveal that the spec was subtly changed in some way during translation. Meanwhile the LLM continues to claim it implemented the spec exactly, then pulls a "you're absolutely right and here's why" when you point out the issue.
I think everyone who has used LLMs for coding will have run into this at some point, so it's not very convincing that LLMs are good at this sort of thing.
We have the case of the paper version of OpenAI's Navier-Stokes work turning out to be describing something slightly different from the Lean formalization, as a more public example.
Something like this likely went through his head. The problem with exotic snakes is that if they are venomous, the likelihood of there being antivenom obtainable within the time that it could serve you any therapeutic use is pretty low. That's true even today. In his case, he was probably documenting symptoms to be thorough at first, and then when he suspected that he had been envenomated, he did the calculus and realized he was already dead.
Envenomation is not necessarily a death sentence. It comes down to immune system response and dosage.
That being said, even today, people foolish enough in the US to own black mambas or cobras are taking significant risks. If bitten and envenomated, they would likely die before antivenom can be air lifted from whatever rare reserves may exist to their location. If one is going to own such snakes, one should be willing to spend six figures on many doses of one's own antivenom, which is only good for 2-5 years and must be replenished, or, to live near a location where such antivenom is stockpiled and be ready to pay to buy replacement antivenom afterward. The assumption should always be that if one owns a venomous snake, it is a question of when, and not if, one will be bit.
I have had a few tame (non-venomous) reptiles over the years. Very gentle things, but sometimes, they bite. The reasons why are numerous: They get scared. They aren't feeling well. They are trying to communicate something. Regardless, they will bite. Getting bitten by a 7 foot male iguana with beefy jowls is not fun. Thankfully, he just nipped me. I still had to clean out the wound and butterfly it.
There are a few species of colubrids that are venomous. What is surprising to most people is that the common garter snake is mildly venomous. The venom doesn't really affect humans like their more venomous cousins, but if their bites do manage to break the skin enough to mix in their saliva, it contains venom that has a mildly neurotoxic effect. This can cause swelling, bruising, and numbness in the affected area. Such a bite is often described as a "bee sting".
I'm not going to look it up (will leave it to discussion here to sort it out), but iirc the fangs of a garter snake are in the back of their mouth, so you'd have a finger fully bitten, or an otherwise "full" bite to likely be affected, no?
I wouldn't call their rear teeth "fangs". I don't think they are even grooved like rear fangs. In colubrids, the venom is in their saliva, so even if you are cut by one of the front teeth, that can be enough to get envenomated. How much of a dosage you get really comes down to how much the snake "chews" on your hand, which mixes in the saliva and thus the venom.
Regardless of how you feel about using LLMs or using products that are developed with LLMs, it is a good idea to have an ecosystem of open source projects with differing levels of LLM involvement, including pristine software written entirely by humans.
The pragmatic argument for hard no-LLM projects: if models are to be useful, they need good input. Hand-written software that has been carefully audited is free from the kinds of feedback errors that will eventually weaken LLM code generation. Otherwise, a bad pattern gets copied. In the next generation, this bad pattern is seen a bit more often as stochastic models converge on it and more open source code adopts it. This is reinforced in the next generation and it becomes a common pattern. Then, in the next generation, this pattern is seen all over. This could be inert "non-coding DNA" like weird naming conventions or pointless comments. Or, it could be bad edge cases that become commonly exploitable.
> What window managers is everyone running? I’m thinking i3 or dwm
everyone is running different managers... I use evilwm on linux and cwm on openbsd. They are very similar (keyboard-driven, floating windows with no frames) with different default keybindings.
The best place to go for curated patches is here. You can customize these or roll your own once you have a chance to examine the source code. dwm is very simple.
I've used OpenBSD as a laptop daily driver for nearly 20 years. It's small. It remains mostly consistent between updates. In fact, it's so stable that I barely notice changes when I upgrade until I go hunting for them.
The Lenovo laptop I use as my travel laptop and console display is a 2012. It still runs OpenBSD just fine.
Same here, but 10 years (6.1). The T420 I have is also my travel laptop. pledge(2) and unveil(2), which is in firefox, makes me feel even more secure while away from my home router.
Upgraded to 8.0, started it, made tea during download, ran sysmerge(8) amd pkg_add -u and done.
Is it possible to get a modern filesystem with openbsd or are they still stuck in the past? Also, is it possible to run openbsd without jumping through hoops on a laptop from 2025 including suspend, graphics, web browser?
I want this to be the case, because the more Linux petrifies, the more a free BSD option is needed.
By default, OpenBSD uses FFS / FFS2. There is an effort in place to port GeFS (from 9front) to OpenBSD. It's unlikely that ZFS will be ported to OpenBSD, due to licensing incompatibilities. For the same reason, btrfs is also unlikely. That's why I run FreeBSD on my big server, and OpenBSD on my laptop and other edge devices. I don't really have any issues running FFS on a laptop; it seems overkill to run anything more advanced than that.
I'd recommend taking a look on forums to see what other folks are running. If it's a modern Lenovo with integrated graphics or an AMD GPU, it will be supported before others. OpenBSD folks tend to use Lenovos. My best recommendation is to pick a laptop that a core maintainer is using, unless you feel comfortable making your own patches. They have AMD GPU support via DRM from Linux. Intel graphics typically works alright.
OpenBSD works well with relatively recent versions of Chromium and Firefox. That being said, they are on a six month release cycle. The Chromium port can fall behind if you stick to -stable or releases. Building Chromium or Firefox from source is... well, I have a 2012 laptop, so that's not something I am going to do. Regardless, you'd need to be pretty comfortable with applying OpenBSD specific patches to one of these browsers, which isn't always obvious, especially since they are moving targets.
If you're used to being on a rolling release Linux, this will be a bit disorienting. But, in my opinion, it's significantly more stable and better thought out.
> OpenBSD works well with relatively recent versions of Chromium and Firefox. That being said, they are on a six month release cycle. The Chromium port can fall behind if you stick to -stable or releases.
Just to clarify here, security patches are backported to -stable. So it is not like you stick to the same browser release for six months.
Personally, I run www/firefox-esr. In part because the ESR moves more slowly in general and in part because it is maintained by someone working for Mozilla.
Excellent answer. Thank you very much. I will keep this in mind when the next life cycling of my current laptop happens. I will keep an eye on the core teams laptop experiments as well if there's anything about that available. Will search the mailinglists.
OpenBSD usually has far fewer hoops than Linux on laptops - IME, either it works or it doesn't. Pretty much any x86 machine that isn't bleeding edge is going to work.
This would do to spirits what homebrewing has done to beer in this country. So many varieties were rediscovered and popularized when homebrewing and microbrewing were legalized during the Carter Administration.
Liquor has become consolidated among a half dozen global conglomerates. Varieties have been streamlined. Folks who are into making historical cocktails tend to hit roadblocks or make modern "almost" substitutions.
I'm in favor of this ban being struck down, even though I can't really take advantage of it. I brewed beer and wine when I was younger, but for health reasons, I can't drink alcohol anymore.
Striking this down won't mean you can resell your homemade liquor. It might lead to some experimentation and we may get more micro-distilleries as an indirect effect, but it won't change the local and state regulations around producing and selling liquor for public consumption.
No. It is not likely that it will be possible to sell homemade liquor. But, it's this experimentation that will lead to more businesses.
Many microbreweries and small breweries started when home brewers went pro. They had recipes that were popular. They decided to go through the fundraising and investment in order to build appropriate facilities and get licensed.
It's this permission to experiment and play that has inspired many of the popular ales available today.
Clandestine operations for most illicit substances tend to be quite dangerous. There are safe ways to distill alcohol, but given that one can't purchase quality distillation equipment in locations where it is illegal, folks often end up making their own.
I think it's perfectly acceptable if these is a reasonable and non-discriminatory licensing process, like for HAM radio or small game hunting, that covers safety. This doesn't eliminate the possibility of accidents, but it does reduce this possibility.
[federal] You can own a still. You can distill water with it. You can't distill alcohol with it unless you register it and get a permit, which carries all sorts of other location restrictions, fees, paperwork requirements, etc.
My friend is a chemist and we both like whiskey so we thought experimented this.
You can speed up the aging of whiskey by increasing the surface area of charred wood. It takes 3 years in a barrel, a couple days (hours? maybe? I'm an engineer not a scientist) if you splinter it into wood chips and char them first and agitate the solution.
What you can't really speed up is the oxidation of the tannins which for all we know (barring experimentation) are a key part of the flavor profile. What you could do is mix in oxidizers like bubbling oxygen through it.
The combination of oxygen and ethanol has a name though: "liquid rocket fuel." The idea of combining heat, ethanol, oxygen, and agitating at bottling volumes sounded kinda scary.
I hope people don't try it at home without knowing what they're doing.
More realistically though, the biggest danger comes from leaky apparatus and an open flame. The horror stories come from home distillation over gas burners. Electric heat is plentiful and home stills would most likely be basically kettles.
I think an ultrasonic cleaner can speed it up, just make sure your vessel with the alcohol in it is sealed first, so no vapors come out. I've tried it before, it isn't perfect, but it works better than you'd expect for maybe an hour or two of time spent.
Methanol is a natural fermentation byproduct of pectin breakdown of fruits like plums, cherries, apricots as well as grapes.
Methanol collects in a still easier than ethanol. Methanol boils at approximately 64.7°C (148.5°F), while ethanol boils at 78.4°C (173.1°F). Professional distillers carefully measure and discard the initial fraction (the heads/foreshots) of a distillation run to remove the methanol. Easy for a novice to miss this key safety step.
The heads only contain a slightly higher proportion of methanol than the rest of the distillate. They're discarded because they taste bad, not because of safety.
Though it has the result that distilled beverages generally contain slightly less methanol than not-distilled beverages.
bollocks. the methanol exists in tiny quantities and has the lowest boiling point of basically anything in your booze.
you don't need "to know how to get rid of it" -- there are no skills needed: just pour it out.
taking care of heads, tails, and "foreshots" -- the methanol -- are one of the most commonly taught, commonly discussed topics in distillation, be it professional or amature.
Not a chemist, but isn’t there something about azeotropic solutions and combined boiling points that make ethanol / methanol separation not as simple as basic lab technique?
It's reasonably hard to poison yourself (other than, you know, alcohol) with fermentation. We've been doing it for thousands of years without specialized equipment or training, and the first batches were probably accidental.
It is rather tricky to distill liquor and NOT poison whoever drinks it. Especially on home or poorly maintained equipment.
This is a bit misleading. While it is possible for distilled spirits to contain methanol, it's generally in very low amounts and removable. Often unless specific ingredients are used, it's not even much of a concern. And funny enough, ethanol itself is a competitive inhibitor for methanol and is an antidote of sorts for methanol ingestion. Most anecdotal stories around poisonous spirits are scare tactics and due to other more serious issues such as prohibition-era bootleggers using car radiators with leaded solder, adding adulterating chemicals to stretch profits, etc.
I'd say that it is actually fairly easy to poison oneself brewing different kinds of alcohols. It is a risky activity. So is driving. So is making fireworks. So is chemistry. So is making cheese, pickles, sauerkraut, and canned goods. People die of botulism every year because they don't follow basic safety procedures when canning, or they eat canned goods that someone else improperly prepared.
That doesn't mean that one shouldn't be allowed to do these things. It means that we should provide appropriate training and, in some jurisdictions, reasonable / non-discriminatory licensing for those who wish to do these things.
When it comes to distillation, the rules are pretty straight-forward:
Keep a log book. Use quality equipment. Measure temperatures. Learn to discard heads and tails. Use appropriate ventilation and fire safety protocols. Purchase qualitative test equipment to verify that the product does not contain harmful contaminants. Licensing is a great way to ensure that people know about these things and follow them. A blanket ban actually makes it more likely that people who violate this ban to distill alcohol will poison themselves or others.
bollocks. the methanol exists in tiny quantities and has the lowest boiling point of basically anything in your booze.
you don't need "to know how to get rid of it" -- there are no skills needed: just pour it out.
you literally just pour out the first 0.5% of whatever comes out of the still. water it down heavily and flush it down the toilet or burn it or whatever. I literally just take the first ~25-50ml of liquid and ditch it -- problem solved.
all other nasty compounds have a very noticeable smell and are fairly easy to detect coming out of the still.
if you're getting poisoned from a home distillation you probably shouldn't be allowed to drive a car or use open flames.
Asking an alcoholic to pour out any kind of liquor is mind-bending to many of them.
Look, you and I both know that it is literal poison, but, again, it's lushes we're talking about.
0.5% is already too technical a term here. What is that in glasses or drams? What do you mean you can't convert pints to percentages? What commie bullshit is a millyliter? Fuck you, I'm getting hammered for cheap!
If you can get a meme going to always piss on your first pint in the toilet, then maybe, just maybe you can get it to work.
And, yeah, a lot of drunks are no longer allowed to drive cars and really should not while drinking too. Doesn't mean they don't do it though.
OpenBSD has a strict "no GPL" policy. It does not incorporate GPL code in the kernel, and it has slowly weeded out GPL code from userland. This is one reason why it builds with Clang instead of GCC.
If Linux DRM weren't licensed under more permissive terms, OpenBSD simply wouldn't permit its inclusion.
I saw the movie Friday night. It is a mind job. You'll walk away with more questions than answers.
Without spoiling the movie, it's possible for people to be multiple things at once. That doesn't excuse what Elizabeth Holmes did or explain what others in her circle may be guilty of. The movie is a wild ride.
Maybe it's just because I've been around a bunch of people in startup circles, seaking angel and vc, etc and myself raised and had exits and been deposed in highly contentious situations.
Holmes doesn't talk like any innocent person has ever talked. Period. Not even like a naive rube either.
She explicitly initiated this whole thing as a narrative exercise and she just had to stick to the script for what, 45 days? While letting herself feel the genuine self pity all these types of people feel when they are experiencing the consequences for their actions instead of being able to foist them onto someone else?
Her only path forward is to FULLY commit to the bit as a way of deceiving the credulous, even a moment of cynicism and the whole thing falls apart.
Now, did she in fact succeed in that or was it a choice to show no cracks in the facade because it made a more engaging movie?
News flash, I love his media but Nathan Fielder is a monster as well he's my favorite monster but let's not pretend. We can just hold both things to be true instead of engaging in cognitive dissonance.
Other than the children (and that one flatulent horse) everyone involved in this is a monster, and the only way to hide that fact is to ensure the ending is ambiguous, otherwise it just feels like non-transcendent tabloid pap profiting off of bad behavior.
There is goodness, and people attempting to increase goodness and it looks and talks nothing like any of these people.
It really sounds like you would consider most people to be monsters. That is, the vast majority of us participate in exploitation to some degree and rationalize that exploitation as necessary, acceptable, minimal or merely something we cannot change.
That's an arguable position, but the problem with it is that it lacks any kind of gradient. Is the person who stole someone else's lunch from the fridge at work (an unfathomable act, to me) a monster in the same way that any person in federal prison is?
The film is relevant: initially, Amanda felt like a proxy for us, the viewers, someone to point out the abnormality in what we have seen. But then, she showed her unwillingness to even confront the possibility the miniseries was exploitative. She displayed a voyeuristic enthusiasm for more information and involvement. She blended into the film at that point, no longer our proxy as unsullied observer. But, can we really not think of a time we reacted defensively instead of with considered reason? Can we not think of a time we dove into a lurid topic that was fully irrelevant to our lives?
There are a number of cases where people involved in monstrous gang violence appear to show genuine rehabilitation. They devote significant effort toward encouraging others to avoid the mistakes they made. Do they do that because they are no longer monsters, or do they do it because it's one of the few acceptable choices available to someone in their position? I'm not sure we can reliably know.
The idea that anyone in this film has a lived experience close to those who grew up embedded in gang violence is a laughable comparison. The idea that anyone involved in this project has demonstrated, through proof of work, even .5% of what's involved in a person who has engaged in gang member reform is absurd. This is extreme category error.
Are you going to pretend that anyone in this film can be rightly considered a representation of the average persons lived experience?
I agree that Amanda Seyfried is an audience proxy in this movie initially. Are you going to assert that her lived experience and her role and place in society is representative of the norm? In this case is it reasonable to accept the films implicit presentation of her as a audience proxy? How is that reasonable? We do not have to accept or enter into the frame the film wishes us to, we do not have to allow it to anchor our starting point in how we engage with the piece of media.
Humans are the only monsters that actually exist, it doesn't make them less human and it doesn't mean they can't change their lived behavior.
Talking to someone outside of the situation confronts the possible compromising of Nathan's objectivity, and dialog is a common way to process experiences.
I felt it as a break from the intensity and absurdity of the initial half, a lull in the rollercoaster. Then the film reduced Amanda's distance from the subject matter and we were off again.
(I do think the intensity of the first half is partly manufactured by a soundtrack that almost cartoonishly conveys 'unsettling' and 'eerie.' That's probably my main complaint about the film.)
I did not suggest anyone in the film had done a single shred of work towards redemption. Not one person in the film recognizes or admits doing anything wrong, which is a usual first step. Nathan never second-guesses his personal rationalization for making a documentary that financially benefits a subject against his own values. Successfully emerging with clean hands in the end does not fully resolve that.
I did not equate anyone in the film with the lived experience of a gang member. When talking about the categorization of people as good or bad or monster, examples where the dichotomy is extreme are relevant.
And yes, of course, Amanda not having our lived experience is part of why she blends into the film. That's no accident. We are shown her farm, horses and a picture perfect fireside setting. Nathan doesn't need to narrate that "Amanda is comfortable and rich with a farm in the Catskills and a pied-à-terre in Manhattan at one of those buildings where you regularly peek into the courtyard you aren't allowed to enter while you walk past" for the film to make that point.
Whether or not the average person has a different lived experience is still a different question from whether or not the average person is classified as a monster by your measure. And the lived experience of the average HN poster could be closer in relative terms of privilege to that of Nathan and Amanda than to that of the much less privileged, even in the so-called developed world.
I do not believe that the average person would agree with your classification of Nathan and Amanda as monsters. That doesn't invalidate your argument, but it does suggest very broad boundaries, and it becomes unclear what, if anything, prevents a plurality or majority of people being defined as a monster by your worldview. My question was about the utility of the binary classification if it ends up being that overarching.
Explain what position you think is being taken? Is it a binary position? A spectrum? Discrete? Continuous? How can anyone understand what you are even arguing against?
The attempt to extrapolate a generalized formalism from a single specific analysis is really building a pattern out of a single data point.
The pattern you've chosen to build is one that allows you to take the negative position but no one knows what position you're actually complaining about?!?
Maybe where I went wrong is that, even knowing you weren't using a more common meaning of monster, I still made some assumptions based on it, namely: monsters are (or seem) inhuman, irredeemable, undeserving of sympathy, and best removed from society. I also assumed that what made Nathan and Amanda monsters to you is their respective exploitation of others, aka "profiting off of bad behavior."
But, monster is a superlative: there isn't much worse you can be. If you are calling a plurality or majority of people 'the worst kind of human,' does the term not lose utility? Do you use it as a mere stand-in for 'bad person?'
That is why I asked: Is the person who stole someone else's lunch from the fridge at work (an unfathomable act, to me) a monster in the same way that any person in federal prison is?
This may seem less serious than I intend it to be. I do think stealing a colleague's lunch is a sign of severely compromised morality, but I wouldn't default to calling them a monster.
This ultimately matters to me, because I am concerned about the outcome. If we characterize people who do bad things as monsters or 'bad people,' it may follow that they be denied any sympathy, humane treatment in prisons or a path to rehabilitation. None of this is to diminish the harm to victims, whose concerns are a priority. As such, I would posit this is a significant reason that sexual assault in men's prisons is tolerated or accepted as serving justice. The larger and more absolute the category, the more people are subject to that outcome.
I also tend to be a bit hypervigilant about anticipated objections. This may appear as a lack of clarity of opinion when it is intended to be concession for the sake of discussion.
> Every journalist who is not too stupid or too full of himself to notice what is going on knows that what he does is morally indefensible. He is a kind of confidence man, preying on people's vanity, ignorance or loneliness, gaining their trust and betraying them without remorse. Like the credulous widow who wakes up one day to find the charming young man and all her savings gone, so the consenting subject of a piece of nonfiction learns - when the article or book appears - his hard lesson.
> That doesn't excuse what Elizabeth Holmes did or explain what others in her circle may be guilty of.
Thanks!
Surely the documentaries are made in a way that's depicts that very accentued, manipulative, borderline psychopathic person. This is likely more than she was in real life. She might even have been motivated by genuine will to improve the diagnostics field. So yeah you might be "deceived" by these docudramas.
I fear that this kind of poetic write-up muddies the water into "oh, maybe things are more nuanced, and played on her weird personality and background to make things look worse, maybe it wasn't so bad".
People got misdiagnosed and suffered directly because of her. She's every bit guilty of that, as deserving of a harsh judgement as any person directly causing that kind of harm.
She was acquitted of several counts of wire fraud to defraud patients, but that does not mean harm was not found to customers. I haven’t been able to find the specific statute, but essentially the jury found that the prosecution didn’t prove all of the elements of that charge beyond a reasonable doubt. We’ll likely never know the details, jury deliberations are secret. But there was absolutely harm to patients. Balwani was also charged with patient fraud and WAS convicted on those counts.
I think it’s incredibly bad faith to knee-jerk respond that people unwilling to reveal the surprises that made the film enjoyable to them are LLMs or shills.
Almost everything you'd want to say about it would spoil something interesting about the film. (This is not hearsay. I've seen it and I can't think about how to say anything meaningful about it without spoiling it.)
So if the movie can be "spoiled" it's at least....entertaining? I'm not sure to think if people are just leaving disturbed and mildly traumatized or what
I felt the movie was entertaining, but also somewhat unsatisfying. You don't really get answers or catharsis from Holmes being further confronted and exposed. To me, the movie was about media narratives and how deceptive lies of omission can be.
Reading reviews about almost any movie is like this. But, I expect the comments on HN to be more genuine than I’m witnessing in this thread.
It almost as if the comment section is filled with HN-trained LLM-backed bots intentionally being absurdly vague; just like the trailer last month was.
I am seriously concerned this is all some sort of ingenious marketing ploy to get people to watch the movie instead of just saying, “I genuinely don’t give a shit about Holmes any more now than I did a decade ago.”
It's a movie with at least one surprising twist, which seems to be fairly central to enjoying the experience, and people who've seen it don't want to spoil it for others. Hence they're vague in their descriptions. It's as simple as that.
The general twist is that she doesn’t really come off as the villain of this film (though she certainly does not come off in a flattering light) - her current husband it turns out is actually a pretty terrifying sociopath who seems to possibly have a bit of a cocaine habit (inferred from the excessive sniffles and insane demeanor) - and he really becomes sort of the films main antagonist.
All of this is completely subjective so someone else could come away with a different take, but if there was a twist (which I would not say this is a film with an overt twist) - it would be this.
For me it was a window into insane wealth and privilege and the types of lives these people lead and the engines that power their sense of self importance and delusions. I do think it was a phenomenal documentary.
SPOILERs kinda: Notably, it's all in the presentation and form of everything that went on. There were about ten different moments in the packed theater where something was said or happened where the entire audience was... silent. tense. I've never felt that sort of palpable and shared tension anywhere in my life like that.
>I am seriously concerned this is all some sort of ingenious marketing ploy to get people to watch the movie instead of just saying, “I genuinely don’t give a shit about Holmes any more now than I did a decade ago.”
Yes, these comments look like a very serious well-funded astroturfing campaign.
I'd say that this would bring up a bigger issue: why would Uber Eats be in the business of using robot couriers to deliver vital medications? Sandwiches or non-essential goods? Sure, I can understand this maybe, bracketing societal issues that these machines represent.
Prescription medications are controlled. If this robot is damaged or destroyed, the patient may not get their insulin at all without further authorization from their doctor or their insurance company. Those logistical issues are much thornier than a retired professor blocking a delivery robot.
I'm not missing your point. I'm pointing out that it's an appeal to extremes that doesn't stand up to scrutiny.
Why insulin? Why not have the robot deliver premature babies from a regional hospital to a central hospital, on a battery powered NICU that only has 30 minutes of battery power?
Once you have a sound formal specification, building proofs that software follows this specification is actually fairly straightforward. LLMs aren't doing any magic here.
reply