picardo

Also, there is a competing interpretation of the law called "Mosaic Theory" that is at the root of the argument against the 1983 ruling. In Carpenter v. United States (2018)...

> [t]he Supreme Court ruled that law enforcement requires a warrant to access historical cell-site location information (CSLI). Chief Justice John Roberts noted that individuals do not surrender all Fourth Amendment protections simply by venturing into the public sphere. The Court determined that compiling a "detailed and comprehensive record of the person’s movements" is vastly different from a police officer casually observing a car drive by.

This is a clear application of "detailed and comprehensive record" creation, and I can't see how Flock could argue with this recent precedent.

The other problem with this opinion piece is that the author assumes that if a citizen is not physically pulled over, they are being "left alone." He completely dismisses the reality that capturing, logging, and storing the movements of millions of innocent, law-abiding citizens in a searchable database is inherently intrusive.

No problem! I hooked up dependabot to detect upstream changes, so when you bump up the version number, it should create a PR and bump the version number of the extension, and I will merge. I think the unit tests should catch any regression.

No thanks. If I have to listen to Mr. Meeseeks' screechy voice all day, I'd shoot myself.

I don't know why I didn't of this before. Thanks for the suggestion.

I tried it with Claude Code for a while but lack of WebSearch tool became a dealbreaker for me. Does anyone know of they will provide support for it?

They could have saved themselves 3MB by converting it to AVIF.

For most static UI surfaces, I probably wouldn't use it, but I can see a use case in this for testing generative UI workloads.

I'm curious what a "stripped down version" of Github can offer in terms of functionality that Github does not? Is it not simpler to have the agents register as Github repos since the infrastructure is already in place?

The key idea is not running constantly, but being always on, and being able to react to external events, not just your chat input. So you can set a claw up to do something every time you get a call.

Is AssemblyAI or Deepgram compatible with OpenAI Realtime API, esp. around voice activity detection and turn taking? How do you implement those?

This reads like a classic case of bureaucratic mission creep. When the budget depends on showing numbers, and the definition of a "threat" is loose enough, the agency naturally evolves into a political tool. The lack of uniform identification and masks just removes the final psychological barrier of accountability for the individual agents.

I'm curious how the unit economics actually play out here compared to traditional search. With Google, the compute cost to serve a query is negligible, so even low-CPM ads are profitable.

With an LLM, the inference cost per query is orders of magnitude higher. Unless thy have a way to command significantly higher CPMs -- perhaps by arguing intent signal is stringer in a conversation than a keyword search -- it feels like a difficult margin to sustain.

Happy thanksgiving all. In an era where algorithms on other platforms seem optimized for outrage and engagement bait, I'm grateful for HN's optimization for curiosity. It's one of the few places left where I can open a thread on a topic I disagree with and actually expect to have my mind changes -- or at least understand the opposing view better -- by the top comment.