MurphyA/hacker-news huggingface dataset:
by zb3 | 2026-01-23 17:12:24+00:00
How does it deal with AVB? Does it have a secure element that works with Android keymint?

Does the bootloader implement fastboot? Is it unlockable? What does the partition layout look like?

I suppose the actual magic has to happen in the "abl" part and this is where it gets very interesting, but these announcements were extremely light on details..
by grugdev42 | 2026-01-23 17:12:28+00:00
Well the first point is don't ask for payment after the work is done. No one will pay because you've already solved their pain. You're in a weaker position at that point.

Tell them how much you charge before you start work and ask if they want you to start work. It can only go one of two ways.

The easiest way to convince them is to compare it to sales. If they are an electrician with an average job of $500, that website only needs to earn them two extra jobs per year to break even.

But the easiest way is to be a sociopath and not care. Ask the question and they will either say yes or no. No one is going to assassinate you for pitching a marketing website to them.

If they say yes, do you care where the money has come from? Would it matter if that was their last $1k? If they're loaded would you feel more confident? What if you do a great job and then it turns out that money came from illegal sources?

What about if they say no? Will you stay awake at night worrying that their business is losing work because people think they're weird for not having a website? What if your marketing website lands them a big client because of the "authenticity factor" of having a professional marketing website?

None of these things actually matter. But getting paid $1k feels good, especially if you've done a good job and earned it. :)
by jjk166 | 2026-01-23 17:12:33+00:00
This is why the goal of experiments needs to be falsifying hypotheses. If you can make a model that fits the raw data without absurd assumptions which contradicts your hypothesis, then the data doesn't support your hypothesis.

If you're checking whether a coin is fair and you toss out significantly more tails than heads because you didn't feel they were proper tosses, of course you're going to reject the null hypothesis that the coin is fair. Even if your criteria for what was a proper toss is objective and reasonable, you're no longer testing whether the coin is fair, you're only testing whether your criteria for counting a toss is fair assuming the coin isn't.

When you construct your experiments to reject a hypothesis - this particular model can not be right if we see this - then you can make real progress towards truth.
by ben_w | 2026-01-23 17:12:33+00:00
Keeping the lights on is sufficient for the immediate concerns.

We can worry about feature growth later, if at all. It may be age finally changing my preferences, but so much of what I've seen sold as "new" in tech in recent years has been either worse than what I already had or a reinvention of something that already existed. Like, contactless payments were already a thing before they were available in phones, and social media didn't start with FB and twitter, and Apple's API updates in the last few years feel like as much of a downgrade to me as their icons seem to be to UI blogs.
by jadbox | 2026-01-23 17:12:39+00:00
The likely hard truth: 90% of software 'itself' will be easily replaceable, especially indie software. The reason why Shopify, Jira, TurboTax, etc are hard to replace is due to most of the HARD work being OUTSIDE software- the legal work for being a payment processor, legal insurance, special client relationships that only salesmen can foster, high market TRUST requirements, legal COMPLIANCE (HIPAA), etc etc. I'm fairly convinced that AI coding is going to force most programmers to move into becoming experts in specific business hard problems.
by tracker1 | 2026-01-23 17:12:39+00:00
I think what Docker should have done, is charge for Docker Desktop from the start... even $5/mo/user as a discount rate for non-open-source usage... similar for container storage, had a commercial offering for private containers from very early on.

The former felt like a rug pull when they did it later, and the latter should have been obvious from the start. But it wasn't there in the beginning and too many alternatives from every cloud provider popped in to fill that gap and it was too late.

There were a lot of cool ideas, and I think early on, they were more focused on the cool ideas and less on how to make it a successful, long lived business that didn't rely on VC funding and an exit strategy they didn't have to succeed.
by toby- | 2026-01-23 17:12:53+00:00
My understanding is that a company's location is largely irrelevant; a company becomes subject to the GDPR when they handle EU citizens' data (or UK GDPR when it's UK citizens), and the EU/UK will still try to fine companies that aren't resident in the EU/UK - enforceability is a different question, although non-payment of fines opens the door to other remedies e.g. blocking access, seizing assets, etc.
Show HN: PR Slop Stopper
by vmazi | 2026-01-23 17:14:00+00:00
I created a github app that allows people to label suspicious LLM slop prs based on heuristic driven scoring of the submitter's github profile, activity, and activity on the repo itself.

Profiles and PRS that fail heuristics have the PR labelled appropriately.

I might also add LLM based scoring in the future, but for now this project uses only heuristic based scoring.

People who have already merged to the repo that the app is installed on should be exempted from the scan.

The project is a FastAPI service that processes requests using background tasks (https://fastapi.tiangolo.com/tutorial/background-tasks/#depe...), to allow for the github webhooks to return in a timely manner.

Might have to upgrade to a proper celery worker if this takes off.

Github app link: https://github.com/apps/pr-slop-stopper

The project uses UV for dependency management, ty for type checking and ruff for linting.

AI DISCLOSURE: I heavily used Claude Code to generate this, but I did read the code during development to ensure it aligned with my personal tastes and habits.

NOTE: I have not been able to test this myself, I tried making a fake github account and test it via forking the source repo (I have the app installed on source repo). Unfortunately, github does not allow forking repos to new accounts under a week old. I verified that the webhook urls are configured correctly with secrets properly being accepted by the server, but have not been able to guarantee functionality. If someone would like, feel free to open a low quality PR and lets see if it gets flagged! (I can almost guarantee it will break since I haven't been able to test this live yet. But a broken thing is the first step to a working thing)
by sylens | 2026-01-23 17:14:01+00:00
I think the author is correct to a point but I don't believe the examples they've chosen provide the best support for their case. Gen Z buying iPods and people buying N64 games again is not evidence of the monoculture breaking apart - it's a retreat into the past for the enlightened few because their needs are not being met by modern goods and services. You cannot buy a dedicated MP3 player today with the software polish and quality of life that an iPod had in the early 2000s (or even a Zune).

Instead, I see the growth and momentum behind Linux and self-hosting as better evidence that change is afoot.
by quickthrowman | 2026-01-23 17:14:37+00:00
You can charge a lot more than you think. IMO, $1,000 for a website is too low. I provide commercial electrical services and $1,000 would get you one of my electrician’s labor for six hours, which does not include material. For specialized electricians who do things like work on generators and do switchgear testing, $1,000 only covers around 5 hours.
by foreverflying | 2026-01-23 17:14:43+00:00
Before the marketing talk, here’s a demo.

What is Ezh?

Ezh is a frontend framework focused on extreme performance and minimal surface area, without sacrificing developer ergonomics.

In practice, it consistently outperforms React in runtime performance, while remaining surprisingly easy to use. One warning though: after using it for a while, going back to React can feel… uncomfortable.

Some concrete numbers

Core implementation: ~2,500 lines of code

Production minified bundle: 21KB

Public API surface: 11 APIs

Learning curve: effectively flat

The Splendor demo above has fairly complex UI interactions, yet the entire game page is implemented in under 1,000 lines of code.

For a more minimal example, please visit https://github.com/foreverflying/ezh-demo Readme page. It shows a tiny interactive example implemented in ~40 lines. It’s meant to be readable at a glance—no documentation required.

Design highlights

Quick self-intro first: my name is Ezh (pronounced like “edge”).

Some technical choices that define the framework:

TypeScript-only
Ezh supports only TypeScript—both for authoring and compilation. No JavaScript mode.
Every HTML element and every component is statically typed. Typos in attributes are caught immediately.

TSX-first, React-compatible syntax
TSX is a first-class citizen. Existing React TSX codebases can often be partially reused. In many cases, removing framework-specific glue code is enough to migrate.

O(1) DOM updates without Virtual DOM diffing
DOM updates are driven by an original, field-level dependency mechanism.
A single state field change triggers the minimal necessary update set—nothing else.
No virtual DOM trees, no diffing passes.

Configurable delayed disposal & reuse
DOM subtrees can be retained briefly after unmount.
If a user switches tabs away from a complex 1,000+ node subtree and returns shortly after, the rebuild cost is close to zero.

Batteries included, but small
React’s core package is ~172KB, and routing, state management, and TypeScript types are all separate concerns.
Ezh ships as a single npm package (~41.5KB unpacked), including ~18KB of type definitions.
Routing, state management, and lifecycle control are all included in the remaining ~21KB of runtime code.

Status

The ezh npm package is already usable today.
You can learn it directly from the demo source code; about an hour is enough.

The core source code will be open-sourced. That has always been the plan, though it may take a bit more time.
by reconnecting | 2026-01-23 17:14:47+00:00
Same here.

Open-source security framework (1). Applied 16 August 2025. Company registered in Switzerland (EFTA). No reply.

However, European Alternatives is a personal (sole proprietorship) website and has nothing to do with Europe, despite the name and style, which are slightly misleading as they mimic official EU website aesthetics.

1. GitHub: https://github.com/tirrenotechnologies/tirreno
by bell-cot | 2026-01-23 17:15:13+00:00
> With Starlink's peer-to-peer capabilities, hitting every single ground station and keeping the satellites from working through new ground stations may actually be quite difficult.

Yes-ish? I was thinking the command & control facilities - far scarcer than the (probably unmanned) StarLink-to-Internet Backbone connection ground stations.

> The moment you launch a nuke...

Yes-ish. The (great-)^n grandparent comment posited WWIII starting, and the nukes flying at scale. Between the widespread obliteration of ground-side infrastructure, ground-side EMP damage, and very likely EMP in space - I'd assume that Starlink would quickly go down. Plus, the ionosphere could become opaque to Starlink's radio frequencies. Finally, the ionosphere's upper layers might expand enough (due to nuclear detonations in or near space) that the orbits of the Starlink satellites started degrading very quickly.

With how easily any major space power could set off "small n" nukes in space during a major crisis, to knock out satellites - I would not rule someone doing so. The responsible parties need not claim responsibility. And sane leaders might hesitate to go full nuclear in response.
by lorenzleutgeb | 2026-01-23 17:15:14+00:00
There's `rad sync status` which will show you (for a particular repository) which other nodes have echoed back to you that they have received and verified the most recent state of your namespace of that repository. So, if you expect some other node to have received your changes, you can use this command to verify that.

When the user explicitly asks to sync, then by default the process will be considered to have completed successfully as soon as three other nodes have echoed that they have received your changes. This threshold is configurable. Further, one can define a list of nodes that they care particularly much about, in which case the process will only be considered to have completed successfully if all these nodes also signaled that they have received your changes.

For anything deeper than that, you'd have to resort to logs. And if you connect your node to the other one your are interested, you can get a pretty good picture of what's going on.

If one node "falls off" the network, then the above mechanisms will communicate that to you, or fail after a timeout.

With Git repositories, humans establish order explicitly. They push commits which are a DAG. The collaboration around that (mostly discussions on issues, patches) is also stored in and synced by Git, but here, humans do not have to establish order explicitly. Rather, these things, in Radicle lingo called "Collaborative Objects" are CRDTs, so they will merge automatically. Nodes also opportunistically tag operations on these CRDTs with the latest operation they know, to help a bit by establishing an order where possible.
by swiftcoder | 2026-01-23 17:15:45+00:00
> saying that Yegge hasn't built real software is just not true

I mean... I feel like it's somewhat telling that his wikipedia page spends half its words on his abrasive communication style, and the only thing approximating a product mentioned is a (lost) Rails-on-Javascript port, and 25 years spent developing a MUD on the side.

Certainly one doesn't get to stay a staff-level engineer at Google without writing code - but in terms of real, shipping software, Yegge's resume is a bit light for his tenure in BigTech
by thewebguyd | 2026-01-23 17:15:57+00:00
The problem (for me) isn't the hardware. The Pixel 10 Pro is arguably a great phone, and I had a 9 Pro Xl for a short time before going back to iOS and I enjoyed it while I had it.

But what I found was I was just trading Apple's quirks for even worse Android quirks, all while losing all the nice ecosystem integrations with my macbook and iPad.

App quality on Android is still hit and miss. Companies still don't put nearly as much effort into their Android apps as they do their iOS apps. Even my banking app was a laggy, buggy mess on Android compared to the iOS version. Heck, even Google's own apps are better on iOS.

Plus, until Google decides to offer E2EE for their cloud services like Apple with advanced data protection, it's a non-starter for me and I really don't feel like going full self-hosted just so I can run Android.

I want to like Android again, but there's just nothing there right now that definitively makes it a better experience for me despite Apple's flaws.
by freejazz | 2026-01-23 17:16:16+00:00
>A selfie uploaded by a schoolgirl was undressed by Grok, turning a “before school selfie” into an image of her in a bikini. As of January 15th this post was still live on X.
An image of six young girls wearing micro bikinis, generated by Grok. As of January 15th, this image was still publicly available on X.

Shocking that the images are still up on X.
by achyudh | 2026-01-23 17:16:51+00:00
I have slowly been migrating my Nix configuration to Guix as there is just so much to like about Guix such as Scheme and full-source bootstrap. I am also very happy about the move to Codeberg which hopefully results in more contributors. The new Rust packaging process is also worth reading about: https://guix.gnu.org/tr/blog/2025/a-new-rust-packaging-model...
by TheAceOfHearts | 2026-01-23 17:16:55+00:00
I'm bullish on LLMs being able to help with this kind of reverse engineering effort, if not current models then in a few more years. I've had conversations with people where they managed to get Claude to help reverse engineer old weird binaries with very little input. I wouldn't hype it up as being a magical tool that'll definitely work, but it can't hurt to try.
by gruez | 2026-01-23 17:17:05+00:00
>I think the curl -u switch just requires the password field to be filled

Yeah you're right, if you don't specify the password (eg. -u user), it prompts you for it

>there obviously isn't a legit user account test@example.com with a password of password either at microsoft or at the Japanese imap server.

But presumably the fact it's there at all suggests it's a required parameter? Maybe "password" is just a placeholder, but it's unclear based on the command line transcript alone.
by blindriver | 2026-01-23 17:17:10+00:00
All the investors before 2019 got multiples of their investment.

So series B is worth about 250M and series C is worth about 625M. Series C-2 is worth about 1.5B. Series D is worth 425M and Series D2 is worth 300M because of LP. That's a total of 3B.

That leaves 2B for everyone else. Most employees are going to get fucked big time, especially the ones after 2019. They will get a small fraction of their RSUs and all their options will be worthless, if they had options.
by pdntspa | 2026-01-23 17:17:13+00:00
I worry about people who use this approach where they never look at the code. Vibe-coding IS possible but you have to spent a lot of time in plan mode and be very clear about architecture and the abstractions you want it to use.

I've written two seperate moderately-sized codebases using agentic techniques (oftentimes being very lazy and just blanket approving changes), and I don't encounter logic or off-by-one errors very often if at all. It seems quite good at the basic task of writing working code, but it sucks at architecture and you need occasional code review rounds to keep the codebase tidy and readable. My code reviews with the AI are like 50% DRY and separating concerns
by fpoling | 2026-01-23 17:17:18+00:00
In "The Brothers Karamazov" by Fyodor Dostoevsky describes sort-of the opposite process. A body of monk who had been considered a living saint started to smell on the second day after his dearth. That made everybody to realize that he was the opposite of the saint. And then another monk mentioned that eating sweets and cakes could not lead to sainthood.
by pstuart | 2026-01-23 17:17:34+00:00
I'm hoping that advances in MoE and other improvements in LLMs will translate to allowing self-hosting to cover a good chunk of developer needs, with extending out to providers when it needs more horsepower.

In effect like traditional on-prem services that have cloud services to handle peak loads...

The tech is still relatively new and there's bound to be changes that can enable this -- just like how we went from 8088 to 386 (six years later). That was a ground breaking change and while Moore's law may be dead I expect the cost to drop significantly over time.

One can dream at least.
by radicality | 2026-01-23 17:17:50+00:00
I also don’t understand the back button at all on Safari iOS, I think one version it just stopped doing its one task correctly. It’s messing with my mental model of how I arrived at each tab. Currently:

Safari iOS: Be on a page, tap hold a link, click Open in new tab, go to new tab. The Back button should be grayed out and isn’t, and clicking it closes the tab.

Chrome iOS: Be on a page, tap hold a link, click Open in new tab, go to new tab. Back button correctly grayed out as the tab has nowhere to go back to.
by mikkupikku | 2026-01-23 17:18:04+00:00
Every time a new version of Windows drops there are legions of Windows users who say this is the final straw, they're keeping their old version until the updates stop then they'll use Linux. And every time that doesn't happen, they just keep going back to Microsoft like it's some sort of domestic violence situation. Their standards forever dropping, getting slow boiled like an apocryphal frog. I've seen this repeating over and over for the past 20 years at least.

At this point I don't even have sympathy for Windows users. They choose their lot.
by ramoz | 2026-01-23 17:18:06+00:00
I ran a similar operation over summer where I treated vibecoding like a war. I was the general. I had recon (planning), and frontmen/infantry making the changes. Bugs and poor design were the enemy. Planning docs were OPORD, we had sit reps, and after action reports - complete e2e workflow. Even had hooks for sounds and sprites. Was fun for a bit but regressed to simpler conceptual and more boring workflows.

Anyways we should settle on simpler/boring. And enhance UX around design, planning, and review.
by mediaman | 2026-01-23 17:18:13+00:00
I don't get the widespread hatred of Gas Town. If you read Steve's writeup, it's clear that this is a big fun experiment.

It pushes and crosses boundaries, it is a mixture of technology and art, it is provocative. It takes stochastic neural nets and mashes them together in bizarre ways to see if anything coherent comes out the other end.

And the reaction is a bunch of Very Serious Engineers who cross their arms and harumph at it for being Unprofessional and Not Serious and Not Ready For Production.

I often feel like our industry has lost its sense of whimsy and experimentation from the early days, when people tried weird things to see what would work and what wouldn't.

Maybe it's because we also have suits telling us we have to use neural nets everywhere for everything Or Else, and there's no sense of fun in that.

Maybe it's the natural consequence of large-scale professionalization, and stock option plans and RSUs and levels and sprints and PMs, that today's gray hoodie is just the updated gray suit of the past but with no less dryness of imagination.
by MrOrelliOReilly | 2026-01-23 17:18:36+00:00
The author's high-value flowcharts vs Steve Yegge's AI art is enough of a case-in-point for how confusing his posts and repos are. However this is a pervasive problem with AI coding tools. Unsurprisingly, the creators of these tools are also the most bullish about agentic coding, so the source code shows the consequences. Even Claude Code itself seems to experience an unusually high number of regressions or undocumented changes for such a widely used product. I had the same problem when recently trying to understand the details of spec-kit or sprites from their docs. Still, I agree that Gas Town is a very instructive example of what the future of AI coding will look like. I'm confident mature orchestration workflows will arrive in 2026.
by lostmsu | 2026-01-23 17:18:59+00:00
Not sure about Ireland, but Switzerland used to be true, but now it is also far behind since 5+ years.

See, Google Zurich vs Seattle

https://www.levels.fyi/t/software-engineer/locations/greater...

https://www.levels.fyi/t/software-engineer/locations/greater...

Hm, after carefully reviewing the entries seem more or less the same, Zurich slightly lower.
by anonymous908213 | 2026-01-23 17:19:06+00:00
The 'experiment' isn't the issue. The problem is the entire culture around it. LLM tools are being shoved into everything, LLMs are soaking up trillions in investment, engineers are being told over and over that everything has changed and this garbage is making us obsolete, software quality is decreasing where wide LLM usage is being mandated (eg. Microsoft). Gas Town does not give the vibe of a neutral experiment but rather looks be a full-on delve into AI psychosis with the way Yegge describes it.

To be clear, I think LLMs are useful technology. But the degree of increasing insanity surrounding it is putting people off for obvious reasons.