MurphyA/hacker-news huggingface dataset:
by davnicwil | 2025-12-23 10:47:35+00:00
yeah, I think I misunderstood the point you were making and I'm making a different but related point. So we probably don't disagree.

Interesting point on the word augment. I'd always took it to mean something more like a value-neutral addition, to which one is free to apply their own value judgements, which could be positive or negative and in any case aren't objective.

To take an example of the kind of thing I'm thinking of: you're out on a peaceful countryside walk yet are able to receive emails. The experience is augmented by this-- in my interpretation meaning you have something literally added to it. But the effect of this can be both positive or negative, to any degree, depending on the email itself and any number of other factors.

Anyway I think we're mostly just getting into semantics and I probably agree actually with your original point :-)
by pjc50 | 2025-12-23 10:48:39+00:00
> It would be an absolute game changer to be able to literally download hardware acceleration for a new video codec or encryption algorithm

That relies on "FPGAs everywhere", which is much further out than "GPUs everywhere".

I'm not sure where the state of the art is on this, but given the way that codecs work - bitstream splitting into tiles, each of which is numerically heavy but can be handled separately - how is development of hybrid codecs, where the GPU does the heavy lifting using its general purpose cores rather than fixed function decoder pipeline?
by rglynn | 2025-12-23 10:49:15+00:00
I've had a number of occasions where claude (et al.) have incorrectly carried out a task involving existing code (e.g. create a widget for foo, following bar's example). In these cases the way I would have done it would be to copy said existing code and then modify the copied code. I've always wondered if they should just be using copy tool (even just using xclip) instead of using context.
by KurSix | 2025-12-23 10:49:32+00:00
The problem goes even deeper than messy RBAC in a database. This story showed that the system's brains are pushed to the edge, and if you gain access to the device, you don't even need the central police database. You get a local, highly intelligent agent working autonomously. This breaks the traditional threat model where we worry about "someone leaking the database"; here, the camera itself becomes an active reconnaissance tool. It turns out that instead of hacking a complex, (hopefully) secured cloud, you just need to find a smart eye like this with default settings, and you already have a personal spy at an intersection, bypassing any police access protocols
by xnoreq | 2025-12-23 10:52:49+00:00
What?! Insane take. NixOS is where the most "magic" happens, over and under the hood. It brings it's own language!

Simple package based distros like Arch basically just extract archives. Very few packages trigger post-install steps which usually just (re)generate something like initrd.

Afaik, bricking Ubuntu is either due to user error (e.g. mixing incompatible package sources) or the devs released broken/buggy packages...
Show HN: CCQL – SQL Queries for Claude Code
by douglaswlance | 2025-12-23 10:52:51+00:00
I built *CCQL*, a CLI tool that lets you run SQL queries directly against your Claude Code data (history, transcripts, prompts, sessions, etc.).

If you use Claude Code regularly, you quickly accumulate a large amount of interaction data. CCQL makes that data queryable with SQL so you can analyze how you actually use the agent.

*Examples*

```bash
# What tools does Claude use most?
ccql "SELECT tool_name, COUNT() AS uses
FROM transcripts
GROUP BY tool_name
ORDER BY uses DESC
LIMIT 10"

# Find prompts mentioning a topic
ccql "SELECT display, timestamp
FROM history
WHERE display LIKE '%authentication%'"

# Cross-session analysis
ccql "SELECT _session_id, COUNT()
FROM transcripts
GROUP BY _session_id"
```

*Built-in commands*

```bash
ccql prompts --session ses_123
ccql duplicates --threshold 0.8
ccql search "error"
```

*Interesting technical bit*
Claude Code stores its data in a structured local format. CCQL loads that data into an embedded SQL engine (GlueSQL) with a clean, read-first model, so you can safely explore usage patterns without mutating anything.

*Features*

* SQL queries across history, transcripts, prompts, sessions, and todos
* Fuzzy duplicate detection (find repeated or near-duplicate prompts)
* Full-text search with regex
* Safe writes with automatic backups
* Output formats: table, JSON, JSONL

*Install*

```bash
# macOS
brew install douglance/tap/ccql

# npm (any platform)
npx @douglance/ccql "SELECT * FROM history LIMIT 10"

# Cargo
cargo install ccql
```

Built in Rust using GlueSQL. MIT licensed.

GitHub: [https://github.com/douglance/ccql](https://github.com/douglance/ccql)

I’ve been using this to understand my own Claude usage patterns—what prompts I repeat, which tools get called most, and how conversations evolve across sessions. Curious what queries others would find useful.
by bigfatkitten | 2025-12-23 10:52:51+00:00
Doesn't even require that many people. The analysis can mostly be automated, and the request process can be handled via peer review. Having one or two people for every 100-200 developers who can give sensible advice, provide some general oversight of what's going on, and step in to say 'no' occasionally does help though.

Also means you can put an end to a popular antipattern that has grown in recent years: letting your production infrastructure talk to whatever it likes to download whatever it likes from the Internet.
by pella | 2025-12-23 10:53:14+00:00
> especially from tech company blogs,

https://engineering.fb.com/

https://netflixtechblog.com/

https://stripe.com/blog/engineering

https://eng.uber.com

https://engineering.linkedin.com/

https://engineering.atspotify.com/

https://tailscale.com/blog

https://careersatdoordash.com/engineering-blog/

https://dropbox.tech/

--

Aggregators:( https://engineering.fyi/ ; https://diff.blog/ )

+ https://hn.algolia.com/?query=engineering%20blog

---

create a public engineering-blog SKILL.md.
( ~ collect the writing patterns that work on HN )
by poelzi | 2025-12-23 10:54:16+00:00
The difference is, you can create proper abstraction modules that put everything together, from dependencies, to config files, firewall rules etc and have nice options for your abstraction.

No other system provides this in that sane way. I used countless configuration systems, from custom bash hacks, ansible, chef, puppet, salt - I have seen a lot.

Nix is just on another level. Never going back
by 112233 | 2025-12-23 10:54:27+00:00
By "we" do you mean consumers? No, "we" will get neither. This is unexpected, irresistable opportunity to create a new class, by controlling the technology that people are required and are desiring to use (large genAI) with a comprehensive moat — financial, legislative and technological. Why make affordable devices that enable at least partial autonomy? Of course the focus will be on better remote operation (networking, on-device secure computation, advancing narrative that equates local computation with extremism and sociopathy).
by aquir | 2025-12-23 10:55:08+00:00
TLDR

"Ryanair’s tactics included rolling out facial recognition procedures for people who bought tickets via a third party, claiming that was necessary for security. It then “totally or intermittently blocked booking attempts by travel agencies”, including by blocking payment methods and mass-deleting accounts.
The airline then “imposed partnership agreements” on agencies which banned sales of Ryanair flights in combinations with other carriers, and blocked bookings to force them to sign up. Only in April this year did it allow agencies’ websites to link up with its own services, allowing effective competition.
The competition authority said Ryanair’s actions had “blocked, hindered or made such purchases more difficult and/or economically or technically burdensome when combined with flights operated by other carriers and/or other tourism and insurance services”.
by KurSix | 2025-12-23 10:55:10+00:00
Fair point but there's a crucial nuance: state surveillance used to be limited by human resources. You couldn't assign an agent to every citizen - there aren't enough people. Flock with their AI tracking has effectively removed this scalability constraint. This vulnerability just highlighted how powerful a tool they've built. If these were just dumb cameras, the state would have to hire an army of operators. As it stands, the technology allows for total surveillance with essentially zero marginal cost. And when they fix the security, that terrifying potential for infinite scale isn't going anywhere; it just goes back under the client's control
by thehamkercat | 2025-12-23 10:57:40+00:00
If i didn't work in tech, I would work for tech.

I'm a linux user, but I hate that majority of MacOS apps/tools are Paid, and I want to change that

If money was not an issue, and I had all the time in this world, I'd start giving it all to Open-source software.

Starting with rewriting all the paid/subscription apps created for macOS.

For example, I'll create an exact replica of:
- Alfred, Raycast, Bartender, BetterDisplayTool etc, but completely FOSS
by TZubiri | 2025-12-23 10:57:47+00:00
One aspect of sysadminship that I find cute (but suboptimal) is how we memorize this strings of commands that were clearly not quite designed to be used in that manner.
A slightly related example is how our intents in our mind end up having commands that don't resemble at all what we actually want, creating a map between intent and command that is almost exclusively arbitrary except for some obsucre etymological origin that might or might not help you remember the command in a time of need.

For example:

Intent: "create a file"

Command: "touch $FILE"

As it happens, touching a file doesn't mean to create, it was supposed to touch to modify the last access date, like a null op. But now if you want to create a file you do that.

Intent: "Print a file contents to screen"
Command: "cat $FILE"

Is this a reference to a feline? some slang for printing or reading? No it's short for concatenate, but if you pass just one argument instead of 2, it prints the concatenation of 1 file and nothing.

Even something as simple as

Intent: "Rename a file"
Command: "mv $FILE"

Of ocurse there's the fact that moving a file and renaming the file are very similar if not identical in most FS/OS, but also, the slight change from a word to a proper-name style command already creates a style of command line interaction that was very natural in the 80s, but is now being reinvented with the advent of more powerful language decoding technology. So even:

Intent: "Copy a file"
Command: "cp $FILE"

Now to the topic, you can see how my relationship with ss is the mapping:

Intent: "See a list of open ports"
Command: "ss -tulnp"

Which I remember mnmemotecnically because it is close to -tulip. This is similar to ps -aux in that the command includes a set of options and I remember it mnemotecnically ("auxiliary" or "auxilio"), and I use the options even when I don't need them, modifying the options from that baseline if needed, like removing "a" to get just the current user's processes.

That said. I don't know if the future is going to be "better" alternatives to old tools, but rather deconstructing or making use of the concept of "binary":"command", running man and --help has never been an optimal solution, and let's be honest, kids nowadays are googling, stackoverflowing and chatgpting their intent in order to get a magical command.

No easy way to improve upon this at the userspace level, the OS model of delegating control to binaries based on a hierarchical command structure is sensible, and "magic", or sharing commands across binaries without a clear ruleset would be too opaque. But I feel that creating new tools while barely revolutionizing the way they work is too small an incremental change, it adds more noise, I'm not sure that ss2 or network-manager instead of wpa_supplicant is a better outcome, now you are just linearly increasing the cognitive demand of new sysadmins linearly with time.

Sorry to be a bummer.
by ofalkaed | 2025-12-23 10:58:14+00:00
When this got released I really expected someone in the opensource community to run with it, but as far as I know no one has. Back around 1990 a Graphic designer that had his office n the same building as my mom worked in let me copy his Photoshop 1.x disks and nothing has ever compared to it for me. When will we get the linux port of Photoshop 1.0? I would love to see how it develops.
by Dylan16807 | 2025-12-23 10:58:28+00:00
> Still accepting writes when the system is in a degraded state _is_ stupid.

Again, I'm not concerned for new writes, I'm concerned for all existing data from the previous months and years.

And getting in this situation only takes one out of a wide outage or a bad push that takes down the cluster. Even if that's stupid, it's a common enough stupid that you should never risk your data on the certainty you won't make that mistake.

You can't protect against everything, but you should definitely protect against unclean shutdown.
by chakintosh | 2025-12-23 10:59:19+00:00
Watched the crash video. Coming out of the tunnel way too hot, combination of speed and driver likely being blinded by the light caused him to drive straight out (likely understeer too) into the concrete barrier and strike at the right angle for it to completely peel the car like a tin can. Passenger was ejected while still attached to his seat (this isn't supposed to happen in a 600k car!!!)
by TZubiri | 2025-12-23 10:59:55+00:00
Not necessarily designed for, but accessible to.

Additionally in sysadmin, blind-users are not just some random group, the ability not to use one's eyes is central to the Command Line Interface. You could always in theory get by with just a keyboard and a TTS that reads out the output, it's all based on the STDIO abstractions that are just string streams, completely compatible and accessible to blind, and even deaf users. (Unlike GUIs)
by tecleandor | 2025-12-23 11:01:32+00:00
Like pianos. Unless they are very good, their value tends to go in the negative numbers with time, as you have to move them somehow.

In my parents place, an apartment in a second floor, there's an upright Yamaha that my dad bought in the late 70s or early 80s. I think they brought them in through the stairs, but like 10 years ago an elevator was added to the building lobby, and I don't think there is enough space to move it around. I think the piano will remain with the apartment forever :D
by Tirrekp | 2025-12-23 11:01:43+00:00
I’m a 20-year-old founder building MotionOS – a shared memory and state layer for AI agents, with our first real focus on voice AI and call centers.

Right now most AI call / support systems still treat every conversation like a fresh session. Context is spread across chat history, tickets, CRMs, and ad-hoc notes. When the bot hands off to a human (or the customer calls back next week) a lot of what happened is lost.

MotionOS tries to make “memory” a first-class infra layer instead of an afterthought:
• per-caller timelines that merge events from calls, tickets, and tools
• APIs to read/write memory in a structured way from any agent stack
• policies for summarising, forgetting and governing long-term context
• a simple dashboard to inspect what an agent “remembers” and why

The current site still shows the more general “developer” version of MotionOS, but our design partners are all in voice AI / contact center land, and we’re shaping the product around those workloads first.

What’s live today:
• basic REST/SDK APIs for logging events and querying timelines
• a minimal dashboard to explore memory for a given caller / entity
• early integrations for typical AI agent stacks (Retell/Vapi-style flows)

What I’m looking for from HN:
• feedback on the data model (what’s missing for real-world agents)
• critiques of the API design and dashboard UX
• pointers from people running production AI voice / CCaaS systems

If you’re building agents (especially for calls / support) and the idea of a shared memory layer seems useful or misguided, I’d love to hear your take.
by masfoobar | 2025-12-23 11:01:59+00:00
They keep reminding you so you end up buying a new PC with Windows 11.
That's all it is. No extra code logic is needed. Just keep pestering the end user with a popup. They don't care for any variations.

The goal is to get everyone on Windows 11.

This is not 1998 or even 2008. Times have slowly and "progressively" moved on. Truth is you NEVER OWNED a copy of Windows. You always purchased the rights to USE it. Now that technology has improved especially the internet Microsoft have tried to gain more control over YOUR computer.

Look at Nintendo and their Switch 2. In their world you do not own it. If they think you are doing something "you shouldn't" they will brick it! Sure, I am not suggesting Microsoft does this with Windows but I am 100% certain this type of tactics has been discussed in high-end meetings. The key here is CONTROL.

Today - if Microsoft want to push a program and "encourage" you to use it.. they will install it without any form of consent. Sorry, but if I OWN a computer then I want control with the software installed, including an Operating System. Microsoft has always been a huge '??' in this field and, to me, it is getting worse. I am not even talking about government involvement with the big techs, either.

Copilot -- I dont care.

This rumour (is it a rumour) that Windows takes photos of your screen every so oftern... NO THANK YOU!

I might have to continue using Windows (11) in my job, being given a work laptop, etc. At the end of the day I do not care as its not my laptop and decisions are taken outside my control by specific IT departments. Whatever. At home I am 100% GNU/Linux. It is sooo much faster and programs loads in <1.5 seconds compared to 5-20 seconds on Windows 11.

My biggest concern is the future of GNU and Linux. Well, the Linux kernel more so especially when Linus hangs up his keyboard. Hopefully the next guy in charge cares about our Freedoms. Honestly I imagine an alternative world where a corporations takes control. The beauty, thanks to the GPL, is people can branch off an continue their own. Sadly... GNU/Linux MIGHT get infiltrated one day and most of that will be people NOT caring about our FREEDOM. This, in my opinion, is all dependent on the future generations.
by cyberroute | 2025-12-23 11:02:00+00:00
I found a critical RCE (XSS→code execution) in LocalStack in October.

I reported it twice to the vendor. They ghosted me completely.

They silently fixed it, called it "deprecation," never acknowledged it.

I requested a CVE from MITRE in October. Then again in December.

MITRE assigned CVE-2025-65200. It's been "RESERVED" for 7+ days since I submitted all required details.

The write-up has been public since December 11. Users need to know to update
from vulnerable versions, but without a published CVE, security
scanners can't detect it.

I followed every responsible disclosure guideline:
- 60+ days of silence
- Multiple vendor contact attempts
- Coordination efforts
- CVE request
- Complete documentation

The result? Vendor silence. CVE bureaucracy. Users left in the dark.

This is why researchers stop bothering with responsible disclosure.

Write-up: https://cyberroute.github.io/post/2025-12-11-localstack-hack...

/rant
by delaminator | 2025-12-23 11:04:06+00:00
If they did, they can only send you screenshots

> 2. Restrictions. Except as expressly specified in this Agreement, you may not: (a) transfer, sublicense, lease, lend, rent or otherwise distribute the Software or Derivative Works to any third party; or (b) make the functionality of the Software or Derivative Works available to multiple users through any means, including, but not limited to, by uploading the Software to a network or file-sharing service or through any hosting, application services provider, service bureau, software-as-a-service (SaaS) or any other type of services. You acknowledge and agree that portions of the Software, including, but not limited to, the source code and the specific design and structure of individual modules or programs, constitute or contain trade secrets of Museum and its licensors.
by ZeroGravitas | 2025-12-23 11:05:48+00:00
In hindsight switching to renewables from nuclear was a great idea.

It's also obvious in hindsight that politicians on the right have been sabotaging it all along, and despite that it still worked out okay and probably helped save the world.

Imagine the whole government was consistently behind wind, solar, EV, batteries, heat pumps etc. manufacturing and deployment, they'd be more resilient to Russia and better placed to compete with China.

It's notable that the more a German political party supports nuclear, the less they support EVs and heat pumps. Which suggests it's a disingenuous distraction for them.
by KurSix | 2025-12-23 11:10:09+00:00
But isn't that "auto-PTZ" exactly what changes the game here? Sure, there are plenty of open cameras, but usually, that's just a passive stream you have to stare at for hours to spot anything interesting. Here, we have a situation where technology has effectively removed the "friction" from the surveillance process. You don't need to monitor the screen for hours - the algorithm itself grabs the person, zooms in on the face, and tracks them. It’s like the difference between searching for a needle in a haystack by hand and having a powerful magnet. Because of the Flock leak, this magnet is now available to anyone with a link, and that is what's truly terrifying, not just the mere fact of filming a playground
by tkz1312 | 2025-12-23 11:12:16+00:00
If you're not making changes to the bootloader it's essentially impossible to brick nixos: updates are fully atomic and every change can be rolled back by booting into an old generation.

This combined with the fact that the full source code for the system is contained within a single monorepo that I can checkout and grep through makes NixOS the easiest to understand and most transparent distro I have ever used.
by reify | 2025-12-23 11:12:22+00:00
The best way to use claude in the browser is not to use it at all

It forgets! It doesn't forget, it doesn't have a memory or a human brain.

maybe!

Consider your own life. look back at your childhood and remember, running home from school on a beautiful sunny day, playing with your friends, remember the freedom. How many years ago was that? 20, 30, 40, 50, and you still remember it like it was yesterday

AI DOES NOT HAVE ANY MEMORIES SO IT CANNOT FORGET.
by nostrademons | 2025-12-23 11:12:58+00:00
Skydio? For a while they were #2 in consumer drones but found they couldn't compete with DJI and exited the consumer market in 2023. They now do > 50% of their business for the U.S. military and are in tight with the U.S. government. Could be a plan to re-enter the consumer market, this time with no competition.
by ImHereToVote | 2025-12-23 11:13:15+00:00
I can't instinctively process how many R's are in STRAWBERRY. I use my vision to get it though almost immediately.

I feel simple transformers simply don't get access to those modalities that a human would use. I can't use my "talking" centers to count letters in words either.

You just need to pay attention to understand you don't use your language skills to count words.
by rgoulter | 2025-12-23 11:13:53+00:00
> The difference is, you can create proper abstraction modules that put everything together, from dependencies, to config files, firewall rules etc and have nice options for your abstraction.

Yes, this is an understated benefit.

The declarative interface is nice.

That NixOS configs are modular allows you to create those abstractions. -- In the same sense terraform modules are "infrastructure as code", NixOS modules are "system configuration as code".