MurphyA/hacker-news huggingface dataset:
by aldovincenti | 2026-02-22 11:46:35+00:00
What you’re describing is actually the flaw of the traditional model. Engineers end up accountable for everything, including decisions they didn’t make, because they are the final gate. In my proposal, responsibility follows decision power and is explicitly shared. Whoever proposes a change owns its behaviour, which is why sufficient product context is essential. This only works if everyone in the team operates as a product person, understanding the impact of their proposals beyond just implementation. The product manager owns product direction, engineering owns system integrity, and ownership is distributed rather than concentrated.

The final engineering review is not full ownership of every diff, but a focused technical judgment about whether the change preserves core invariants and integrates coherently within the system. If engineers still have to review exponentially more code while remaining responsible for everything, then the model has failed. The goal is to distribute accountability together with autonomy, so engineering safeguards systemic coherence while the entire team shares responsibility for product outcomes.
by Degorath | 2026-02-22 11:46:56+00:00
My experience has so far been similar to the root commenter - at the stage where you need to have a long cycle with planning it's just slower than doing the writing + theory building on my own.

It's an okay mental energy saver for simpler things, but for me the self review in an actual production code context is much more draining than writing is.

I guess we're seeing the split of people for whom reviewing is easy and writing is difficult and vice versa.
by adrian_b | 2026-02-22 11:46:59+00:00
Esperanto has succeeded to become the best known of the artificially-constructed languages.

Unfortunately, its creator had only modest knowledge of linguistics, so there are many features of Esperanto that can be considered as mistakes, and they have contributed to its little success.

Some of the artificial languages that have been designed later are much better than Esperanto, but they have achieved even less notoriety than it.

What has doomed all artificial languages, despite the fact that some of them would have been much better than English for international relations and for the publication of scientific and technical literature, has been the absolute dominance of USA over the entire world after the end of WWII.

This unbalanced relationship between USA and everyone else has forced the use of English both in commercial relations and in the scientific and technical publications, excluding all alternatives and replacing not only any artificial languages, but also the European languages that previously had been more important than English, i.e. German and French.
Show HN: Persona AI – A decision engine that outputs binary verdicts, not chat
by kmish9685 | 2026-02-22 11:48:37+00:00
I noticed that LLMs are terrible at being decisive. To get around RLHF hedging (e.g., "it's important to consider both sides"), I built a system that forces constraints.

Instead of a chat interface, Persona AI acts as a computational decision engine. You provide the stakes and constraints of a specific problem. Under the hood, it runs the input against specific mental models (inversion, survivorship bias checks) modeled after specific operators (Musk, Thiel, etc.).

The UI enforces a strict output: a binary YES/NO verdict, a generated conviction score, and "Kill Signals" (falsifiable conditions where you must abandon the path).

I'd be interested in feedback regarding the UI approach to enforcing these AI constraints versus an open-ended chat window.
by embedding-shape | 2026-02-22 11:50:36+00:00
The motivation/justification from the author why they believe removing lisp but adding Electron somehow sums up to being "lightweight"?

Maybe the author thought of the UX/baggage/legacy or something else when they thought about "lightweight", rather than how much memory/cpu cycles something is using? Not sure, but maybe there is a more charitable reading of it out there.
by blensor | 2026-02-22 11:51:19+00:00
I've only just started to dive into it from the documentation side of things. They have ( maybe recently? ) started to create this Gateway Protocol https://docs.openclaw.ai/gateway/protocol to connect the stuff together.

It may be a "we are changing the wheels while driving" thing, but if enough people make nodes for openclaw it will become somewhat of a standard. And then we probably see 100 different claw offshots that all use the same nodes but with a different claw in the center
by NoiseBert69 | 2026-02-22 11:51:24+00:00
My tip:

Move to the country where your language is being spoken and get a private teacher over Teams/Jitsi/Whatever who teaches it to you using the "classical" school way with books and homework.

This forces you the speak the new language in real life but also has comfort that you don't have to learn a third language using your second language - which is most likely English.

Sounds like billionaire stuff - but it's honestly not overly expensive.
by rramadass | 2026-02-22 11:51:27+00:00
Why don't you put your real identity on your profile instead of hiding behind anonymity and spewing negative agenda-driven points on HN?

@dang can easily verify that userid "freethinker101" was created for just one comment to introduce a negative agenda-driven point to which you i.e. "thisislife2" responded with a convenient but false anecdotal story to build a specific narrative.

All of which i have shown up.

HN can easily correlate network metadata for both userids and take appropriate action.
by abanana | 2026-02-22 11:52:02+00:00
Yeah, that's exactly it - there were all those history blogposts, full of very interesting stuff, but all about before the ribbon was in active use. (Pity about the image rot.) No usability studies of the ribbon itself.

Parts of those blog posts were unintentionally revealing of the groupthink of an enclosed bubble of people who couldn't see the wood for the trees. A great example is this piece about moving menu entries around so you couldn't build muscle memory, and had to take the time to look for what you wanted:

> First, remember that we're analyzing this with 20/20 hindsight... there was a lot of excitement (not just at Microsoft) about "auto-customization"... to present exactly the right UI for the person at hand. Now, it's easy to say that today people are generally against this idea... but we know that mainly through trying... the adaptive UI in Office 2000

As I recall it, the vast majority at the time - users, reviewers, UI/UX writers - considered its downsides to be completely obvious and were firmly against it. Its designers were apparently the only ones who needed 20/20 hindsight to see that.

> I remember thinking that the thought process behind the ribbon was very solid

I agree, the historical research, and the work on identifying the problems, was very solid. But the massive criticisms of the ribbon suggest it was not an entirely successful attempt at a solution.

I've seen it said that there's no way Microsoft would have neglected to carry out major usability studies on such a major UI change, and that the fact that nothing's been published, after all the blogposts and talks beforehand, suggests they chose to bury a bad result. No idea whether there's any truth in that of course, but it does sound plausible.
by arboles | 2026-02-22 11:52:40+00:00
A list of hashes (tuple of [hashed url+date metadata, hashed content]) takes much less disk space than the archive contents themselves. Archive websites could publish the list for all their content so it can be compared against in the future. People would save copies of the list. If you didn't store the list yourself ahead of time, and don't trust a third-party to be "the source of truth", the archive could've uploaded the hashes to the blockchain at archive time:

https://gwern.net/timestamping
by mentos | 2026-02-22 11:52:56+00:00
Ha funny I had a similar idea I was calling ‘GameFlock’ but game date is much better.

To the creators I think there is something here worth continuing to push and try to find traction. As a game developer this is just a matchmaking algorithm with a week to month long wait time :)

My plan was to try to prime the pump with a few popular games and reaching out to existing communities to make them aware and possibly help organize the software/tools to help onboard new players.

For example Ultima Online has Outlands. Tribes2 has a popular discord that arranges matches. I imagine WoW classic and I know C&C Generals have active communities on Discord and I think they’d be willing to work with you to help prime the pump.

Then once you’ve got that critical mass of usage hope that players will participate in other games outside their main passion to make other game dates a success.
by bonoboTP | 2026-02-22 11:53:16+00:00
It feels like retracing the history of software project management. The post is quite waterfall-like. Writing a lot of docs and specs upfront then implementing. Another approach is to just YOLO (on a new branch) make it write up the lessons afterwards, then start a new more informed try and throw away the first. Or any other combo.

For me what works well is to ask it to write some code upfront to verify its assumptions against actual reality, not just be telling it to review the sources "in detail". It gains much more from real output from the code and clears up wrong assumptions. Do some smaller jobs, write up md files, then plan the big thing, then execute.
by entrox | 2026-02-22 11:53:29+00:00
I believe you misunderstood the point of my comment, or rather I didn't make it clear enough. The quotes I quickly picked out feel like they represent a majority opinion on HN, namely that this is progress and disruption. I don't share that opinion.

My own gut feeling is that this sentiment comes out of a position of superiority and a definite lack of empathy. It is software engineers building the technology that is leading to job loss, sloppification of everything as well as second order effects like storage and RAM prices soaring because of the hype.

As such, I find it ironic to complain about being replaced. After all, your profession is the one responsible for all of this, so now please take a look in the mirror and take responsibility for the actions of the industry you choose to work in.

Personally, I think the current trajectory of AI is an overall net negative to society. I sincerely hope it all comes crashing down in another AI winter, but we'll see.
by abustamam | 2026-02-22 11:53:43+00:00
> Developers should work by wasting lots of time making the wrong thing?

Yes? I can't even count how many times I worked on something my company deemed was valuable only for it to be deprecated or thrown away soon after. Or, how many times I solved a problem but apparently misunderstood the specs slightly and had to redo it. Or how many times we've had to refactor our code because scope increased. In fact, the very existence of the concepts of refactoring and tech debt proves that devs often spend a lot of time making the "wrong" thing.

Is it a waste? No, it solved the problem as understood at the time. And we learned stuff along the way.
by georgefrowny | 2026-02-22 11:53:43+00:00
> This is a known good state; write tests to enforce this state" is something that takes minutes now instead of days.

Pointing the AI agentic SLoC cannon at that sounds like a way to speedrun a set of tests that completely ossify the codebase.

Careless slapping down of tests feels great and looks good in the CI at first but a good test that only tests what it needs to do and leaves flexibility for maneuver is at least as hard to write as the code to start with.
by constantcrying | 2026-02-22 11:53:47+00:00
>Is it? Then why isn't it cheaper to produce and cheaper to own?

Because batteries are very expensive. But they aren't particularly complex.

This argument just does not make any sense at all. Of course simple components can be more expensive. The cost of ownership is even less relevant, since it depends almost entirely on outside factors, which vary by region and government.

>It's a standard combustion engine, nothing special.

This is totally false. The hydrogen storage alone is enormously complicated. Hydrogen, especially at the pressures needed for a car to be viable is far more complex to store safely then fuel storage for a regular diesel/gasoline car.

Pretending this is not the case is just delusional.
Show HN: Electron IPC Bridge- Auto-generated type-safety without the boilerplate
by StrangeSound | 2026-02-22 11:53:49+00:00
Hey HN,

In 2024 my son was born, and during the long nights of frequent wake-ups, I started (and never finished...) building an Electron app. I very quickly found that the boilerplate required to wire up the main and renderer processes to be very cumbersome, and I'm sure like many others, started to build abstractions around it to make life easier.

Having been heavily indoctrinated in the NestJS ecosystem through my workplace, I started to grow fond of DI, decorators, and the declarative style of working.

My first attempt at abstraction was fairly mediocre, but I recently decided to have a second crack. I leaned more heavily into decorators so that I could give the library a clean syntax that was simple to use. I then packaged it up so that others can use it too.

Electron IPC Bridge allows you to decorate your classes in the main process, and automatically configures the contracts in the preload. The accompanying vite plugin generates types from those contracts and ensures type-safety in the renderer. Change your contracts? The types update too. Easy!

Before:

// Main
ipcMain.handle("users.get_profile", async (_event, userId: string) => {
return userService.getProfile(userId);
});

// Preload
// Easy to make a mistake with the channel, or forget to register
contextBridge.exposeInMainWorld("api", {
getProfile: (id: string) => ipcRenderer.invoke("users.get_profile", id),
});

// Renderer
// No type-safety
const profile = await window.api.getProfile(userId);

After:

// Main
@IpcController()
class UsersController {
@IpcHandle()
async getProfile(userId: string) {
return userService.getProfile(userId);
}
}

// Preload
setupPreload();

// Renderer
// 100% Type-safe, auto-generated contracts with IDE autocomplete
const profile = await window.api.users.getProfile(userId);

I've also tried to supply a few different DI library examples too to help people get started. I took my original unfinished app and managed to migrate it fairly painlessly! It's also using Nest now instead of typedi.

AI Disclosure:
Core: About ~90% handwritten with some assistance and refactoring in places
Vite plugin: Around 50/50, leaning towards AI leading where my experience with Vite is lacking
Docs: Mostly written by me, but AI planned site structure, and reviewed and edited what I wrote. It also wrote the troubleshooting page and generated some diagrams for me.

This post was all me!
Show HN: TurboStitchGIF GIF decoder that lets you choose: safety or speed
by DenisDolya | 2026-02-22 11:54:25+00:00
Version 1.2 introduces two LZW backends (safe bounds-checked vs unsafe turbo), micro-cache for 30-40% faster decoding, three output formats (RGB888/RGB565LE/RGBA8888), span-based turbo blit, optional 256KB RGB565 map2 for 2-pixel-at-once rendering, proper disposal method 3 support, renderer API for indexed output, safety toggles to disable checks when you need raw speed, and prefix mode to avoid symbol conflicts — all while staying 100% malloc-free on a user-provided scratch buffer.

Repo: https://github.com/Ferki-git-creator/TurboStitchGIF-HeaderOn...
by Nasrudith | 2026-02-22 11:55:41+00:00
I think it is quite reasonable to tell incompetents that they can't just cover their ass by claiming "you can't demand perfection".

These are the same kind of incompetents who want the pay but not the responsibility of the position. Who think that building a giant haystack of all of the data is the solution so they can illogically claim to have prevented something that because you had that needle in there somewhere! Except you never found it in time because you were too busy building the tower of Babel out of hay! It is just utterly idiotic double-think. (Cough, cough NSA!)
by eesmith | 2026-02-22 11:56:15+00:00
Calling it a false positive is entirely in line with the historical use.

Back in the 1980s or earlier it was called a "false drop".

Knuth, for example, talks about it in "The Art of Computer programming", v3 as I recall, using cookie ingredients. (See https://archive.org/details/fileorganisation0000thar/mode/2u... for Tharp using the same example.)

Bloom filters are a type of superimposed coding.
by accidentallfact | 2026-02-22 11:57:57+00:00
People always overestimate how 'phonetic' their language is, because nobody actually uses phonemes in regular speech. In Korean in particular, there doesn't even seem to be any obvious correspondence between what is written, and what is actually said.

Foreign accents don't come from any inherent inability to learn language after X years of age. They come from people pronouncing languages as they are written, and virtually no language is like that in reality.
by adrian_b | 2026-02-22 11:58:32+00:00
Borosilicate glass is much more resistant to chemicals and shocks than ordinary glass, which is why it is used in glassware for laboratories and in also in the better cooking vessels.

Except for hydrogen fluoride (a.k.a. hydrofluoric acid) and for hot and concentrated strong alkalies, biological or chemical agents will not have effects.

The main danger is either breaking the glass or its crystallization at high temperatures. A HDD is also unlikely to survive a drop on a hard floor and high temperatures would demagnetize it much more easily than affecting a glass stab.
by jeresig | 2026-02-22 11:59:48+00:00
Oh that's very cool! I have a mailing list signup on the ukiyo-e.org home page, I'll send out a message there once it's ready for testing! I've posted some screenshots on Reddit that show some of the price comparison features: https://www.reddit.com/r/ukiyoe/comments/1p6c4lb/comment/nqp... https://www.reddit.com/r/ukiyoe/comments/1pjw8br/comment/nti...
by IshKebab | 2026-02-22 12:01:49+00:00
It was never the only hard part, but it definitely was a hard part (at least in most cases; obviously there are some monopolies with relatively simple software - mostly where there are network effects like WhatsApp).

But give me the source code for something competitive with Solidworks, Jasper Gold, FL Studio, After Effects, etc. and I'm sure as hell making a business out of it!

Furthermore while good software may not guarantee business success, it is pretty much a requirement. I have seen many projects fail because the software turned out to be the hard part.
by lenkite | 2026-02-22 12:02:12+00:00
Hard disagree. It is not an improvement - it is a deterioration.

Repeat (dot command .) is far more powerful and general thanks to operator->action.

Much better composability with counts, registers, marks and operators with operator->action

Operator Pending mode has some unique advantages for swipe edits that are painful in a select first paradigm. Ex: `d/foo<CR>`. No fast equivalent in Helix.

Also, if you really want, you can select in VIM and do your job too. Use visual mode with `v`.
Show HN: Databasus v3.16.0 – new release of self-hosted PostgreSQL backup tool
by rostislav_dugin | 2026-02-22 12:02:33+00:00
Hi!

I want to share the latest important updates for my open source tool for scheduled database backups (with focus on PostgreSQL).

A quick recap:

- Supported databases: PostgreSQL, MySQL, MariaDB and MongoDB

- Many storage destinations: local storage, S3, Google Drive, Dropbox, SFTP, rclone and more

- Notifications: Slack, Discord, Telegram, email, webhook

GitHub - https://github.com/databasus/databasus

Website - https://databasus.com

In 2025 Databasus renamed from Postgresus when it became popular and support for other databases was added.

Primary audience for the project is developers, DevOps engineers and DBAs. Now project is the most GitHub starred repository for backups (surpassed even WAL-G and pgBackRest). There are ~240k pulls from Docker Hub (both of previous Postgresus and Databasus images).

New features:

1. GFS retention policy

GFS is an acronym for Grandfather-Father-Son. It allows to keep last N hourly, daily, weekly, monthly and yearly backups.

This is needed to keep backups over wide period of time within reasonable storage space.

Before only X days or months were supported.

By default now is used:

- Keep 24 hourly backups

- Keep 7 daily backups

- Keep 4 weekly backups

- Keep 12 monthly backups

- Keep 3 yearly backups

Usually this strategy is used by enterprises which needs long period of backups retention.

2. Encrypted backups are stored along with their metadata to decrypt them without Databasus itself

Before, if server with Databasus is destroyed, you were not able to decrypt backups without Databasus itself. So you had to make backups of Databasus internal DB.

Now backups are stored in S3\Google Drive\other storages with meaningful names with their encryption metadata in format:

- {database-name}-{timestamp}-{backup-id}.dump

- {database-name}-{timestamp}-{backup-id}.dump.metadata

In case of server destruction, you need only `secret.key` to decrypt backups and restore via pg_dump, mysqlbackup, mongodump or other tools. It is important for me to not vendor-lock users on my tool (even despite the fast it's OSS)

Full guide - https://databasus.com/how-to-recover-without-databasus
by embedding-shape | 2026-02-22 12:02:43+00:00
> They have ( maybe recently? ) started to create this Gateway Protocol https://docs.openclaw.ai/gateway/protocol to connect the stuff together.

That's a communication protocol between openclaw server and clients authenticated to that server though, it's not a communication protocol between different openclaw servers, is it? More like defining a HTTP+JSON protocol between a web server and a browser side client application. It's not a "protocol defining how to interact with distributed nodes", again, unless I misunderstand something.
by csmpltn | 2026-02-22 12:03:44+00:00
European governments and institutions have conveniently exempted themselves from GDPR.

And just because it's a law somewhere on earth, doesn't make it reasonable or enforceable or legal.

1. American and European laws have different standards for data processing
2. EU citizens willingly go into a contract with an American company, buying and using American services
3. EU citizens complain American law is different than European law, whilst continuing to use American products
4. EU citizens expect their laws and regulations to apply to American companies

Nobody can reasonably expect American companies to just bend over for whatever the lawmakers in Europe demand. It's an absurd scenario that only the EU can come up with.
by LAKSzero-I | 2026-02-22 12:03:52+00:00
I’m sharing an idea I call GenLoop: a Human–AI Generational Learning Loop and “Generational Playbook Engine” for using AI to train humans and pass knowledge between generations, instead of just building bigger data centers.

I’m a former Paramedic Supervisor of a County EMS system and Pediatric care provider to for my medically fragile child (pen name: LAKSzero) and wrote this as an early manifesto. I’d appreciate feedback on the concept and its practical uses.
by ben_w | 2026-02-22 12:06:09+00:00
> Although I don't see how this corn should be unaffected by crop failure if all other corn harvests failed.

I believe the argument being made here is "we need to overproduce corn in order to get food security; what can we do with the spare capacity in the good years given we're already eating too much?"

I don't know if this argument is correct, but I believe that's what's being claimed.