MurphyA/hacker-news huggingface dataset:
by inglor_cz | 2026-02-11 12:08:50+00:00
Or somewhere remote. Czechia is a small country with a well-developed grid and nothing here is really "remote" compared to, say, Alaska.

But people still do have chalets/huts in the mountains, and the authorities won't spend money on burying 10 km of cables in complicated terrain just for a small hut colony or a solitary hut. Which means that the cables go through the air, which means that a fallen tree can sever them, and you won't be particularly prioritized. That said, people who actually live there or spend longer holidays there during winter months, tend to have enough firewood collected to survive such situations comfortably.

It is a different story in cities/villages with compact house patterns. I don't think I ever saw a snow-related blackout in such a place. There, your worst risk is actually flooding. We've had some serious floods in the last decades, and even buried cables will get damaged and short-circuited in such an event. For example, the cable needs to cross a stream, so it is attached to a bridge, high water comes and tears down the entire bridge with the cable as well.
by hasheddan | 2026-02-11 12:09:04+00:00
Good question! We wrote a few blog[0] posts[1] about the motivation for signy and how it is used in practice. The primary use case is complex devices with multiple MCUs and multi-protocol connectivity (e.g. Wi-Fi, Cellular, Bluetooth, etc.). In this context, each MCU may have different security capabilities, and manufacturing / provisioning may be simplified by storing a single set of credentials (e.g. a private key) in a single secure storage location, then using that key to generate a temporary signed URL that can be handed to the less secure domain for a scoped operation, such as downloading an asset. There are also more niche use cases, such as allowing an end user to access a private resource by generating a signed URL and sending it to a phone via NFC.

[0]: https://blog.golioth.io/signed-urls-for-embedded-devices/
[1]: https://blog.golioth.io/signed-urls-on-esp32/
by actionfromafar | 2026-02-11 12:10:48+00:00
None of it.

It the motor is smaller, it pulls less current.

If it pull less current, you can use batteries which aren't specced for high amps.

If use use less amps, you can use thinner cabling and split the batteries up i various compartments. That means heat is more distributed. Less active cooling, if any, is needed, of both batteries and motors.

All of the above can translate to less weight, which mean better range.
by keiferski | 2026-02-11 12:11:54+00:00
I work for a SaaS.

Basically I think it depends on your customers. If they’re just regular people, developers, etc. looking for a productivity tool, you should worry.

But if your clients are actual businesses looking for reliable, secure software, I wouldn’t worry too much. A real business isn’t going to trust hacked together, vibe coded solution. At that level it’s better to just pay $100-1,000 a month than deal with unpredictable problems.
by lifis | 2026-02-11 12:12:06+00:00
Seems the classic legacy overengineered thing that costs 100x production costs because it's a niche system, is 10x more complex than needed for to unnecessary perfectionism and uses 10-100x more people than needed due to employment inerta.

A more reasonable thing is to just use high quality cameras, connect to the venue fiber Internet connection, use normal networked transport like H.265 with MPEG-TS over RTP (sports fans certainly don't care about recompression quality loss...), do time sync by having A/V sync and good clocks on each device and aligning based on audio loud enough to be recorded by all devices, then mix, reencode and distribute on normal GPU-equipped datacenter servers using GPU acceleration
by srean | 2026-02-11 12:13:47+00:00
To reconstruct the image one has to cut off those frequencies in the corrupted image where the signal to noise is poor. In many original images, the signal in high frequencies are sacrificable, so get rid of those and then invert.

https://en.wikipedia.org/wiki/Wiener_deconvolution

If one blindly inverts the linear blur transform then yes, the reconstruction would usually be a complete unrecognisable mess because the inverse operator is going to dramatically boost the noise as well.
by derangedHorse | 2026-02-11 12:13:58+00:00
> 1. The restaurant isn't lacing your food with cocaine

Cocaine creates a much larger chemical change in the brain and can kill you in high doses so it’s not really comparable.

> 2. The author is incentivizing reading, which is generally a good thing

Says who? Why is reading inherently a good thing?

And all of those things are regulated because they have what most consider to be objectively bad effects on the body (with metrics based on cellular harm).
by kashunstva | 2026-02-11 12:14:02+00:00
> Becoming a parent is basically a destruction of the self.

I am a parent and have definitely felt very stressed on account of children. But as for feeling like my "self" was destroyed, I can't really say I ever experienced that; and I'm not even sure about the idea of a fixed immutable self anyway. I'm not advocating for having children, or against having children; but I don't think I was crushed as a human being because of my choice.

My last child is graduating from high school this year. She's a violinist and I'm a pianist. I've always accompanied her since she was 3; and we do a lot of musical collaborations. I definitely feel like my sense of self is expanded by all of this. But maybe I just got lucky.
by Esn024 | 2026-02-11 12:14:50+00:00
I think, unlike what the author writes, communities CAN be moved if they are sufficiently small and loyal to the leaders who do the move, and the leaders don't screw it up. Moreover, the move is sometimes an improvement.

I've witnessed it myself. For example, Commander Keen fans moving from various InsideTheWeb forums to a centralized phpBB following the ITW shutdown announcement in the late 1990s. I can't think of anybody that got lost, and it was actually an improvement because the new discussion infrastructure was better than it had been before. The community didn't scatter to the winds, far from it; it consolidated and grew.

Of course, such a situation is probably rarer with the enshittification these days, but it would be worth it to figure out when it works, too.

And history is replete with stories of groups who became most successful AFTER a migration, or at least were not so negatively affected by one.
by tim333 | 2026-02-11 12:15:06+00:00
I'm not sure with the trucks. My guess is requiring cameras that provide a view of the problem areas might be the thing, possibly with some AI that detects cyclists and the like. I think a lot have warning signs on now for cyclists. Personally I never stop anywhere near them and treat the red lights as kind of give ways.

I'm not sure the highway code rules are that appropriate for places like central London. I tend to treat the whole place like a pedestrianised area - not worrying too much about road signs but giving way to pedestrians.
by dathinab | 2026-02-11 12:17:18+00:00
speculations are it's either related to ICE or drug cartel investigations

The former has a long history of not cooperating with local authorities (also in ways I personally think are sometimes quite malicious but that is off topic). Und normal circumstances ICE would never have the power to lead to a shut down of air space, but with the current administration who knows.

And drug cartel investigations won't cooperate with the city council as an investigation big enough to shut down airspace wouldn't want to risk it leaking by speaking with a city council about it.

But this is a pretty big deal and lets hope this is just about preventing some high ranking drug cartel members from fleeing and not some retaliatory horror story implicitly triggered by the repeated public rejections and denouncements of Trump in recent week. Like if we look at full (and violent) dictatorships(1) you would expect an internet outage to follow and then a lot of people to die.

(1): To be clear no the US is not a full blown violent dictatorship. Even through things are bad, they are not "that" bad. Through IMHO there seem to be people in the government which want to make it exactly that bad.
by muragekibicho | 2026-02-11 12:17:26+00:00
1. I like my laptops with USB ports and removable RAM and disk. I love computers and opening up a mac is a bad experience.

2. It costs an arm and a leg to replace parts on a Mac when you travel outside the United States. Replacing the keyboard on my first macbook cost the same as the actual price. I learnt my lesson. I don't need that Apple garbage in my life.
by FranklinJabar | 2026-02-11 12:17:39+00:00
> Wouldn't that qualify you as a YIMBY?

YIMBY is the pro-private-development lobby, as best I can tell. PHIMBY is the term I've seen.

> If you want to build public housing, only the NIMBYs would really oppose the idea.

I suspect most who go by YIMBY would also oppose this.
by chairmansteve | 2026-02-11 12:17:51+00:00
Ok... How about this? All (human) models of the universe are "Ptolemaic" to some degree. That is, they work but don't necessarily describe the true underlying structure ().

So it is a mistake to assume that any model is actually true.

Therefore complex numbers are just another modeling language, useful in certain contexts. All mathematics is just a modeling language.

() If you doubt this, ask yourself the question: Will the science of particle physics have changed in 100 years?
Show HN: Lorem.video – placeholder videos generated from URLs
by guntis_dev | 2026-02-11 12:18:38+00:00
At work I have to deal with videos in different resolutions. We're also switching from H.264 to AV1, so I needed a quick way to test our video pipeline with different formats and sizes.

I created lorem.video - a service that generates placeholder videos directly from the URL. For example: https://lorem.video/1280x720_h264_20s_30fps

You control everything via the URL path: resolution, duration, codec (h264/h265/av1/vp9), bitrate, and fps. Videos are cached after first generation, so subsequent requests are instant.

Built it in Go using FFmpeg for encoding. Generation runs in a nice'd process so it doesn't interfere with serving cached videos. Running on a cheap VPS.

MIT licensed, source on GitHub: https://github.com/guntisdev/lorem-video
by mcjiggerlog | 2026-02-11 12:19:10+00:00
I have published an extension [1] that has 100k+ users and I've probably received hundreds of emails over the years asking me to sell out in one way or another. It's honestly relentless. For that reason I also only trust uBlock Origin, Bitwarden and my own extensions.

I'd also note that all this spam is via the public email address you're forced to add to your extension listing by Google. I don't think I've ever had a single legitimate email sent to it. So yeh, thanks Google.

[1] https://chromewebstore.google.com/detail/old-reddit-redirect...
by xmcqdpt2 | 2026-02-11 12:19:13+00:00
Because it's the middle size between the two reasonable car sizes that are being made today: gigantic and fucking enormous.

If you aren't buying at least the gigantic car, then you don't care about your kids safety and that's bad. How are you going to protect them from my gigantic SUV?

What? Walking?? No of course that's illegal! You want to navigate the street without a massive steel bubble? Are you nuts!
by Sharanxxxx | 2026-02-11 12:19:58+00:00
Hi HN,

I’m sharing a project I’ve been working on with a client called CartOS. As someone who has spent a lot of time in the e-commerce space, I was interested in their approach to 'un-siloing' the merchant stack.

The platform is built for businesses that want Shopify-level ease of use but need deeper control over the theme engine and backend extensibility. It uses Liquid templating for front-end flexibility, but the 'Bolt' system is what caught my eye—it allows for adding complex logic (SEO engines, shipping protection, reviews) as modular units rather than messy third-party app injections.

A few technical highlights:

-> Unified Logic: It bridges digital storefronts with a native POS (NFC, KDS integration) on a single database, avoiding the typical sync lag between retail and web.

-> Liquid Support: Full control over the storefront design for those comfortable with Shopify’s templating language.

-> Built-in Automation: It includes 'Cascade,' a native marketing engine, so you aren't piping data out to third-party email tools just to send a recovery flow.

It was developed by a team with 30 years of enterprise experience (Salloq), and the focus was on making the 'infrastructure' invisible so merchants can just scale.

I’d love to hear this community's thoughts on the 'Bolt' architecture vs. a traditional App Store model. Does the 'all-in-one' approach appeal to you, or do you prefer the modularity of separate services?

Check it out: https://cart-os.com/

I'll try to answer what I can about the architecture!
by seansh | 2026-02-11 12:20:26+00:00
I think you mean Scrimba. Yes, it's similar in the sense that in both tools, when you're playing back a recording, you're not looking at the code as a video. But instead the code is there as text. You can pause the recording, look at the files in the project, scroll up and down the editor etc.

The difference is that CodeMic records and replays inside your editor, not on the web. Currently, only VSCode is supported, but the output is independent of VSCode, making it easy to bring it to other editors and even the web.

Another difference is that CodeMic is not focused on web development or any particular stack. It's more general.
by b3lvedere | 2026-02-11 12:20:48+00:00
Kind of a weird feeling that in order to get the better Windows 11 experience one requires programs from four operating system versions earlier.

Windows 11 also takes a huge amount of time to get working as i intend. I have to remove a lot of 'features' and heavily optimize some processes. It's stable and it works, but i'm getting more and more annoyed by it that upcoming updates sometimes destroy all my effort.

Kinda wish i could run everything my family wants on Debian. I know i could do that right now, but the wife and kids will never get used to that if they have to use Microsoft products in their working and school life.
by llm_nerd | 2026-02-11 12:21:33+00:00
"I wasn't told how to interpret it"

Then you detail how you had to look up how to interpret this. Amazing stuff. Like, do you realize you just destroyed your own nonsense? Doing the "Duh, obviously" bit and then saying "this picture was so weird I had to be told what it meant" is quite the self-own.

"where you apparently jumped the conclusion that it was two men that were obviously about to have sex "

Save this boorish troll Reddit righteous-brigading garbage from HN. How isn't your garbage post far in the negatives?

Yes, you're so enlightened and better than thou. Howler.

It's an extremely odd picture to be on one's homescreen. Some people have their dog, some their wife, and then Bob here, he has two strange shirtless men in an extremely odd pose. Not even any normal album cover text to make it clear it's an album cover. Just a picture of two shirtless men.

"naval aviators"

Again, Reddit look-at-the-crowd bullshit.
by RupertSalt | 2026-02-11 12:22:03+00:00
I worked for an ISP in the mid-90s and had been on the Internet since 1989 or so. I recall the progression for me was something like this:

We used telnet in college no problem. It was a fairly well-accepted method of remote access. The heterogeneous network had many different modes, but a major dialup point was the Annex box, which supported telnet into the Unix or VMS machines.

Between Unix machines, we would often prefer "rlogin" instead. There were several horrific iterations of other remote-access protocols such as "remsh". rlogin was notorious for its "/etc/hosts.equiv" authorization method which trusted DNS and should've been perceived as Swiss Cheese from the outset. rlogin was, IIRC, directly related to rsh and rcp and used the same frameworks. rlogin was no more secure than telnet, but probably less secure because of its conveniences.

We also used port 23/tcp for remote management, for example Cisco routers. They weren't running telnetd, but it was the port where you connected remotely and logged in with or without credentials.

rlogin persisted alongside telnet, until encryption came into fashion and ssh was distributed. Once ssh was available and working well, everyone knew that telnetd and rlogind were on borrowed time. The services were shut down and disabled in inetd. The ports were sometimes blocked. Security advisories went out.

I suppose it took a long, long time for ssh to finally dominate, and for people to abandon telnetd mostly, but it was fairly thorough. We all recognized the superiority of sshd's authentication and encrypted channels.

There were mitigations for people to extend their legacy use of telnetd and rlogind. For example, tcp wrappers and fail2ban could be implemented. Firewall filters could select only authorized networks. VPNs could tunnel through an Intranet that still used them. So, the services lived on wherever they didn't need to be exposed on the public Internet. But I think most Unix admins got the picture by the end of the dot-com bubble.
by freetime2 | 2026-02-11 12:22:30+00:00
The R2 isn't even really a mid-size SUV. It is closer to a RAV4, which is considered a "compact SUV" or "crossover" [1]. Mid-size SUVs like the Honda Pilot tend to be even larger.

[1] https://www.carmax.com/articles/suv-size-comparison-guide
Divexa: The High-Tech Architecture of a 'Pig Butchering' Scam
by aoijfoqfw | 2026-02-11 12:22:53+00:00
Following a series of forensic audits and victim trajectory tracking, ReviewShield Anti-Extortion Lab has identified Divexa as a sophisticated fraudulent entity. While it positions itself as a "next-generation Web3 exchange," its operational logic is a textbook implementation of high-tier financial extortion masked by technical jargon.

1. MSB Registration: The Compliance Facade
Divexa aggressively weaponizes its FinCEN Money Services Business (MSB) registration to manufacture institutional trust. From a technical compliance standpoint, MSB is a mere administrative record-keeping filing and does not confer the regulatory oversight, asset audits, or consumer protections associated with a full banking or brokerage license. By intentionally conflating "federal registration" with "state-level money transmitter licensing (MTL)," Divexa creates a legitimacy gap to shield its unregulated activities from retail scrutiny.

2. The 'Pig Butchering' (Sha Zhu Pan) Lifecycle
Our forensics indicate that Divexa’s user acquisition funnel is deeply integrated with global social engineering networks. The platform utilizes a three-stage "slaughter" model:

The Prime: Targets are lured via "investment mentors" or fabricated "romantic interests" on encrypted social apps.

The Fattening: The platform’s centralized backend manipulates trading data to show astronomical, fabricated gains, triggering the "sunk cost" fallacy to encourage larger deposits.

The Slaughter: Withdrawal requests are met with algorithmic blocks or account freezing once a target's capital hits a critical threshold.

3. Systemic Extortion & ‘Secondary Slaughter’
When victims attempt to retrieve their capital, Divexa triggers a standardized extortion protocol. The platform demands "security deposits," "personal income taxes," or "liquidity verification fees"—often 20% to 30% of the account balance. Our evidence confirms that paying these fees never results in fund release; instead, it leads to further extortion demands or a permanent account blackout. This is not a business dispute; it is organized cyber-extortion.

4. Technical Infrastructure & Operational Risks
Divexa’s infrastructure fails to meet the "bank-grade security" standards it advertises:

Certificate Validation: Official domains lack Extended Validation (EV) SSL certificates, a baseline for legitimate financial institutions.

Physical Nullity: The claimed New Jersey office at Hudson Street has been verified as a virtual mail-drop with no physical operations.

Engine Vulnerabilities: Stress tests show the "trading engine" is a closed-loop simulation with zero verifiable on-chain liquidity or external order routing.

ReviewShield Verdict:
Divexa is a high-risk fraudulent architecture designed for capital theft. ReviewShield Lab advises the technical community to blackhole all associated domains and revoke any Web3 wallet permissions linked to this platform immediately. We advocate for a zero-tolerance policy against entities that weaponize "technical innovation" to facilitate financial crime.
by dakheera47 | 2026-02-11 12:22:54+00:00
Hi HN,

I built JobOps to solve a problem I kept running into: job links expire, descriptions get edited, and by the time an interview invitation arrives weeks later, I have no idea what I actually applied for or which resume version I sent.

What it does:

Snapshots job descriptions at application time (so dead links don't kill your context)
Generates tailored resumes and stores the exact version you sent with each application
Supports local LLMs (Ollama, LM Studio) alongside cloud providers for resume tailoring
Command bar (Cmd+K) and keyboard shortcuts for bulk operations
Webhook integration for automation (n8n, Zapier, etc.)
Dashboard for tracking application velocity and success rates
Technical details:

TypeScript monorepo. React 18 + Vite 6 frontend, Node/Express backend, SQLite + Drizzle ORM. Self-hosted via Docker Compose with persistent ./data volume.

The LLM integration is provider-agnostic—swap between OpenAI, Gemini, OpenRouter, or local models without code changes. Built an adapter pattern that made adding Ollama support trivial.

Job extraction uses a pluggable system: JobSpy (Python wrapper), Gradcracker, UKVisaJobs, manual imports, Glassdoor. Everything normalizes to a unified schema with deduplication.

Why local-first:

Your job hunt data is sensitive. This runs entirely on your machine. No SaaS, no tracking, no data leaving your infrastructure unless you explicitly configure webhooks.

Current state:

Been shipping daily for 3 weeks. 200+ stars, 570+ Docker pulls, 5 contributors I've never met, users answering each other's questions in issues. It's gone from "tool for myself" to something people are actually using.

Demo (read-only): https://jobops.dakheera47.com
Repo: https://github.com/DaKheera47/job-ops

Open to feedback, questions, and PRs.
by josephg | 2026-02-11 12:23:17+00:00
Urgh. This problem with git is so unforced. Essentially, people want commits to mean 2 different things at the same time:

1. Store the uncurated history of how the project was developed. 1 commit is created whenever a dev types 'git commit'.

2. Be a linear list of PRs / changes / whatever to a project. Each PR is created by squishing many commits together. It is associated with a conversation around code review, a ticket / issue and often some feature or bug.

Commits can't be both of these things at the same time, so we end up with unnecessary tooling like this.

The answer seems pretty obvious. Git just needs 2 separate mechanisms for these 2 different ideas. The obvious approach would be to leave commits as being atomic units of code change, and invent a new concept in git which represents a feature / feature branch. It would essentially just be a metadata object naming a set of commits, and it would have links to an issue tracker, CI results and code reviews.
by hocuspocus | 2026-02-11 12:23:53+00:00
EPI is the interface and it's built upon SEPA and TARGET standards.

Wero is the implementation. I think it makes sense to provide a turnkey solution to all participating banks, so that we don't have 100+ versions of the same app.

Countries that don't want to trust EPI (or simply outside the Eurozone) are able to take the same path as Bizum in Spain, and make their domestic solution interoperate with EPI instead of replacing it.