News for hackers. Stuff that matters.

picardo

Re:A Cop's Case for Flock on Wednesday October 07, 2026 @01:40PM (#49996159)
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.
Love it! I created a VSCode extension to render it in markdown files and highlight its syntax: https://github.com/volkanunsal/relative-diagrams-vscode/
Re:Claude is just Mr. Meeseeks on Monday July 13, 2026 @06:53PM (#48900021)
No thanks. If I have to listen to Mr. Meeseeks' screechy voice all day, I'd shoot myself.
Re:DeepSeek makes the V4 Pro price discount permanent on Saturday May 23, 2026 @07:33AM (#48246799)
I don't know why I didn't of this before. Thanks for the suggestion.
Re:DeepSeek makes the V4 Pro price discount permanent on Friday May 22, 2026 @06:35PM (#48242491)
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.
Re:Autoresearch Hub on Sunday March 15, 2026 @04:41PM (#47391658)
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?
Re:Claws are now a new layer on top of LLM agents on Saturday February 21, 2026 @01:28PM (#47103307)
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.
Re:Asterisk AI Voice Agent on Thursday December 25, 2025 @10:56AM (#46385115)
Is AssemblyAI or Deepgram compatible with OpenAI Realtime API, esp. around voice activity detection and turn taking? How do you implement those?
Re: on Saturday November 29, 2025 @09:41AM (#46087898)
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.

This man is a legend. He's been working on making a better marble machine for more than a decade. The only payoff is the satisfaction of listening to the synchronized syncopation of falling marbles.

Here is a more recent video: https://www.youtube.com/watch?v=k8NXF2rtaEg

Re:Tell HN: Happy Thanksgiving on Thursday November 27, 2025 @02:28PM (#46072467)
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.
Re:React vs. Backbone in 2025 on Saturday October 25, 2025 @10:39AM (#45704265)
You're right about that, but that wasn't common practice at the time. We learned about side-effects from Elm and Flux.
Re:React vs. Backbone in 2025 on Saturday October 25, 2025 @09:03AM (#45703575)
> Isn't this just how the DOM works? Data flows down through attributes and properties; events bubble up?

That's right, but this communication pattern causes serious complexity. Imagine trying to find out what triggered a state change. You would have to listen to every event source to find out. With Flux, all state changes were mediated by the reducer in the store. It made things a lot simpler.

Re:React vs. Backbone in 2025 on Saturday October 25, 2025 @08:56AM (#45703530)
> Didn't they call it Flux rather than Flow?

Ah, you may be right. It's been a long time.

Re:React vs. Backbone in 2025 on Saturday October 25, 2025 @08:14AM (#45703288)
> For massive apps with 1,000 components on the same page, maybe React's complexity is justified. But what the other 99% of apps?

The number of components is not the only yardstick of complexity. Most of the complexity comes from state management and how state changes are propagated across the store and the UI.

I worked with Backbone for many years, and I can distinctly recall the hours of frustration I had debugging a UI because it was freezing due to cascading state changes. That was because we were using Backbone store, which had bidirectional data flow, and when one updated the store, it would trigger a change to the UI, which would change the state store, which would change the UI, etc.

You could argue that the real innovation of React was "unidirectional data flow," but React team made Flow architecture central to the framework, making it easier to adopt good practices, whereas Backbone remained store agnostic and even encouraged the Backbone Store which used the observer pattern for many years. I think you should choose a framework that allows you to fall into the Pit of Success, and React was that framework at the time, and for my money, it still is.

This should be higher. While the research question is interesting, the sample size makes the conclusion highly suspect. I'd like to see more research on this.
Re:Designing NotebookLM on Saturday September 20, 2025 @06:25PM (#45318155)
Thank you for your hard work. I gripe about it sometimes but it’s still the most compelling learning experience I’ve ever come across. I hope it keeps getting better and better.
Re:Designing NotebookLM on Saturday September 20, 2025 @04:28PM (#45317160)
Video explainers, for me, are better than the audio overviews.
Re:Designing NotebookLM on Saturday September 20, 2025 @04:05PM (#45316886)
I use NotebookLM everyday. The simplicity of the design is much appreciated. However, there are real issues scaling the design and keeping it user friendly as the team keeps adding new features.

The most recent example of this is with the addition of 2 new capabilities (Flashcards and Quiz), "Artifacts Button Container" now has 6 large buttons, and is 328px in height! There are users who are accessing the site from small screen devices in India and they have been asking for help on Discord forums because they cannot see their notes anymore. So I had to create a Tampermonkey script to let users collapse it.[0] I heard the team is fixing that soon, but they should have done more testing before releasing it.

There are other issues like this that I've fixed with scripts. The strangest one is the "notes." Why force the users read a 2000 word essay in a 360px sidebar? So I wrote a script I wrote to let you pop it into full screen mode.[1]

Another example is the chat input field. The follow up questions are hardly usable at all. And they're not stable after you select them.

I can go on all day, but I think it's better to fix things than to complain.

[0] https://gist.github.com/volkanunsal/94db50629cad816eca84c836...

[1] https://gist.github.com/volkanunsal/fded9124d62422c0d2672b8a...

Re:Dev Culture Is Dying the Curious Developer Is Gone on Friday September 19, 2025 @12:28PM (#45303519)
I'm regretting turning off my Ad Blocker. Do not click on the ads, folks -- especially if you're at work.
Re:Chrome's New AI Features on Thursday September 18, 2025 @04:26PM (#45294583)
Last time I checked the context window for the embedded Gemini Nano was 1024 tokens. I hope they have reconsidered that limitation.
Re:Learn Your Way: Reimagining Textbooks with Generative AI on Thursday September 18, 2025 @03:57PM (#45294226)
I'm excited by this multi-media approach. I've been avid self-learner for years, and I've often found the textbook format too dry, and forbidding, but ever since I started using NotebookLM, I'm diving into textbooks more and more. There is genuine value in creating a new format that meets learners where they are at.
Re:Famous cognitive psychology experiments that failed to replicate on Wednesday September 17, 2025 @05:15PM (#45281487)
Well, at least the growth mindset study is not fully debunked yet. It's basically a modern interpretation of what we've known to be true about self-fulfilling prophecies. If you tell children they are can be smart and competent if they work hard, then they will work hard and become smart and competent. This should be a given.
haha, I believe you!
131,484 people sought mental counseling from Claude in this time period. To put it into context, that's more than the number of psychologists in the US. This number points to the scale and impact of AI systems in making mental health more accessible to all.

Older »