hwillis

I use codex daily and a moderately complex plan + a few files is more than enough context to make it blatantly ignore prompts like "stop and ask before adding new layers or data structures"

> Just look at how hard it's been to protest all the new gas plants that came up over the last ~20 years.

People have been talking about SMRs being the economic future for over 70 years. It has not happened because it not true.

1. those charges were dismissed

2. the article address that specifically:

> The case is an example of Flock cameras being used to arrest a wanted alleged criminal suspected of committing a violent crime. But it is also an example of police surveillance overreach *in that the cameras were specifically used to create a pretext to tack on additional petty crimes* based primarily on where a person’s vehicle had traveled.

dendrites are not really a significant problem in popular batteries. It's associated with lithium metal, vs lithium in normal batteries is in the form of salts. Solid state lets you use metal, which is much more energy dense since you don't need the salts.

The most common lithium battery failure mode is that you have a hole in the plastic separator between the +/- sheets inside the battery, which shorts and causes a hotspot that eventually starts a fire. Dendrites cause the short by growing across the gap. In normal batteries it is caused by a manufacturing defect. The outcome is pretty similar.

The energy "stored" in the light oil electrolyte of a battery is >10x more than the electrical energy or the energy released by reacting lithium alone.

An 18650 battery weighs ~50g and stores ~10 watt-hours. 10 watt-hours is 8,604 calories, enough to heat 50g of water by 172 C or 310 F. The battery would not even burn without a liquid electrolyte to ignite.

Scale obviously does not make this more okay; watching many intersections or cell towers is obviously less reasonable than a single intersection or tower.

> In comparison: license plates, when in public, are always visible, and very easy to discern from one-another (different state-unique numbers); so in my mind the expectation of privacy is far lower.

Legally, overhearing a conversation is not different. If you are loudly talking about your drug deals in public in front of an officer, they can use that as evidence. A police department could hire officers to stand everywhere in public and listen to every conversation nearby.

Or, more specifically, they could stand conspicuously close to every payphone and listen. The phones are in public; the officers don't need to be uniformed. Practically speaking this is not at all different from wiretapping. That's what the police did in Katz- wiretap a public payphone.

Flock cameras are not in any meaningful sense different from having officers follow around everyone and record everywhere they go. Its irrelevant whether one officer is following one person or if many people are following them, each within their own small area. That would absolutely not be legal without a warrant. The only difference is a private company is doing it and selling it to the police, something that should clearly not be legal.

"some caching gains" is a pretty huge understatement- snipping something out of the middle of the window requires rebuilding the entire context. Thats a shitload of tokens.

Afaik messing with the context also pretty reliably degrades performance still. The model responses reference things that no longer exist to it and it becomes more chaotic.

The real usefulness of parallel or sub-agents is not that they run at the same time, its that they isolate noisy or self-contained context away from the main window.

browsers aren't common either. Standards, formats, and interfaces are, which is exactly what WASM is and what this demonstrates. Native apps don't need a common operating system or even a common core like nix. They just need to support a common interface, like browsers do.

for me the eyes are also showing the unwrapped texture of character's own heads, which is extremely unnerving lol

Totally missing my point.

Say you have bladder pain and chatgpt tells you that is a common indicator of appendicitis. If you go to the doctor and tell them you think you have appendicitis, they will think you are saying your appendix hurts and look for causes of pain in that region. They will not look for bladder-related pain, because you did not tell them what hurts.

Extrapolate that to all the possibilities for all conditions- something that the system is not equipped for. Doctors do not know that bladder pain is a possible indicator of appendicitis because of experience or logic; they know because it is part of their education because the system has learned that over time. The system does not account for people filtering their symptoms through chatgpt.

Further, it's still bad. It still increases the permutations the doctor is required to consider for no reason. Doctors make mistakes- they make mistakes often. Knowing a bit of medicine can be very helpful for patients. Weaponizing them with a predictive text machine is not the same thing.

We have standards of care for a reason. They are the most basic requirements of testing. Ignoring them is not just being a bad doctor, its unethical treatment. Its the absolute bare minimum of a medical system.

> I do feel I actually biased the first doctors opinion with my "research."

It may feel easy to say doctors should just consider all the options. But telling them an option is worse than just biasing their thinking; they are going to interpret that as information about your symptoms.

If you feel pain in your abdomen but are only talking about your appendix, they are rightfully going to think the pain is in the region of your appendix. They are not going to treat you like you have kidney pain. How could they? If they have to treat all of your descriptions as all the things that you could be relating them to, then that information is practically useless.

not to mention turning off FSD milliseconds before impact