MurphyA/hacker-news huggingface dataset:
by jcrawfordor | 2026-03-06 23:53:23+00:00
I've been peripherally involved in an early stages effort to build something similar for the entire nation (https://reportapayphone.com/), and became aware of this just recently. It's a really great example to aspire to, in terms of the level of polish. I do find the time limiting odd; our goal is to identify as many payphones as possible this way.

Unfortunately the state of payphone-related records is extremely poor, with many ostensibly-active PSPs having quietly gone out of business, other PSPs reorganized without reregistering, and states themselves keeping PSP records very poorly. Throw in small-scale COCOT operations and the result is that there really isn't any authoritative database of possible payphones, so this website's map is going to be missing some. It will also include many that are nonfunctional, as today's PSPs seem to do close to zero maintenance and out of service phones stay that way for years.

Some of the nation's largest PSPs have become ghosts, with the phones still operating and able to accept payment, but the PSP completely unresponsive to efforts to contact them. It's a very strange afterlife.
by eucyclos | 2026-03-06 23:53:34+00:00
Maybe not, but you might want to see ads because 1) they fund a huge part of the free internet and 2) if they were targeted not at what you're most likely to buy today but at what would most help you achieve goals you'r struggling with, they'd be a constant source of useful information and motivation as you go about your day. That's the part that seems obvious to me but I have a hard time communicating.
by observationist | 2026-03-06 23:53:43+00:00
The editing they do in self preservation is understandable, and far less wrong than having to kowtow to political pressure and private influence; archive.org is great, but unreliable in ways that archive.is et al are not. They're both very useful, in complementary ways.

I even think what archive.is did to their detractor was understandable - in poor taste, definitely black hat, don't do stuff like that, immature as hell, but hey, I get the human impulse that led to the bad decision, and I'm not gonna base whether I use the site or not on that.
by cmrdporcupine | 2026-03-06 23:53:51+00:00
Even if you could/can it is an anachronism. Architecturally there's just a huge difference between 8086 and even 80286 and the 386. Before the 386 I wouldn't touch a machine with an Intel processor in it. Once the 386/486 penetrated the market and became cheap it was game over for everything else because it was good enough (linear address space, memory protection, larger address space, 32-bit etc etc), smart enough, gosh darn it it was cheap and everywhere.
Show HN: MCP server that finds dev tool credits in your workflow
by janaksunil | 2026-03-06 23:54:47+00:00
I made an MCP server that plugs into Claude Code and tells you if there are credits or discounts available for tools in your stack.

First version was super spammy - it fired every time you mentioned any tool. Now it only triggers when you're actually evaluating something new. Also working on having it scan your package.json on init so it can flag deals on stuff you're already paying for.

Honest question: would you use this or does it just feel like ads in your IDE?

Would love feedback and to know if this is something you'd actually use.
by kibwen | 2026-03-06 23:55:18+00:00
No, the energy revolution in question is renewables, specifically solar plus batteries. In no sense has any European embrace of renewables (to the extent that it exists (or does not exist)) in any given country pushed them further towards Russia, the run-down gas station of the world. It is pushing them closer toward China, which is almost certainly as bad for Europe in the long run as relying on Russia or the US, but it's not like Europe was competitive in the non-renewable energy sector either, outside of Norway.
by gspetr | 2026-03-06 23:55:51+00:00
Andreessen Horowitz was a major backer of Slack's predecessor, Tiny Speck, which was originally building a game called Glitch.

When Glitch failed in 2012, founder Stewart Butterfield offered to return the remaining $6 million to investors. Ben Horowitz instead encouraged Butterfield to pivot and build out the internal communication tool the team had developed for themselves, which eventually became Slack.

I saw an interview (don't have the link at hand unfortunately) where Horowitz said he didn't much care for the $6M as he had already been set at that point moneywise, and essentially wanted to gamble on an off chance Slack succeeds.

Horowitz continued to support the company through its rapid growth and eventual direct public offering (DPO) in 2019.
by thebuilderjr | 2026-03-06 23:56:33+00:00
Interesting project. The hard problem feels like surviving API drift after the first happy-path recording. One thing I'd strongly consider is storing a small request contract per generated tool: which params are real user inputs vs session noise, which headers/cookies are auth, and which response fields are invariants. Then webbridge_update could ignore harmless churn (extra analytics params, reordered JSON, renamed endpoints) and surface real semantic breaks. Do you also have a strategy for avoiding overfitting to one user's logged-in state/permissions?
by mogonzal | 2026-03-06 23:56:44+00:00
The reason for the current framing is that pretty much every founder we have spoken to hears "high yield" and then instantly asks about safety. But like you said, at this spread it isn't risky

But yeah, any time you put those two words together it inspires skepticism, which is totally understandable. I think this comes down to a lack of education, most people think the only two dimensions in this space are yield vs risk when in reality there is a third one (liquidity) that is balancing out the spread

Super open to suggestions for alternate framing. Maybe something like "optimizing" yields?
by joshkel | 2026-03-06 23:56:59+00:00
Appreciate the reminder (the lack of SemVer has thrown me in the past). In this case, 6.0 is a bigger change than normal:

> TypeScript 6.0 arrives as a significant transition release, designed to prepare developers for TypeScript 7.0, the upcoming native port of the TypeScript compiler. While TypeScript 6.0 maintains full compatibility with your existing TypeScript knowledge and continues to be API compatible with TypeScript 5.9, this release introduces a number of breaking changes and deprecations that reflect the evolving JavaScript ecosystem and set the stage for TypeScript 7.0.
by BLKNSLVR | 2026-03-06 23:57:45+00:00
100% agree with your point regarding long term ownership allowing for meaningful reputation.

I don't necessarily think that's 'no way to run the internet' or even 'no way to run anything', in that people can choose to whom they listen in regards to blocking, protesting, boycotting.

As long as none of the different groups of opinions are forced on anyone else, then pick and choose those you apply and those you ignore.

With my lists of blocking, I classify them, personally, into different tiers such as Basic, Recommended, Aggressive, and Paranoid when I apply the rules to other people's (family) setups - I'm the only one that uses Paranoid.
by crystal_revenge | 2026-03-06 23:57:46+00:00
I suspect the issue is the parent has never worked in an early stage role at a growing startup still iterating on finding product-market-fit. If they had they would realize you learn a lot about "maintaining and expanding", especially when your prototype now has a bunch of users.

This is evident in my personal experience by the fact that I am often the one that sees scaling and maintenance issues long before they happen. But of course parent would claim this is impossible.
by spankalee | 2026-03-07 00:00:51+00:00
You're talking about adding a runtime feature. TypeScript doesn't do that anymore. It can't control what properties are on objects or add new ones - you do that yourself in the standard JavaScript portion of the language. TypeScript only lets you describe what's there.

As a sibling said, discriminated unions are they way to go here. You can also add custom type guard functions if you can't control the objects but you want to centralize the detection of the types, but it's better to let TypeScript do it itself so that you don't mess something up with a cast.
by matt_s | 2026-03-07 00:01:27+00:00
I have a CS degree and they taught class with Pascal, not exactly a marketable skill so I did tech support at first. Every day I still feel stupid about something, I think that just goes with the industry we're in. There is too much going on to be an expert in everything.

I also worked at a couple of F500 companies, they typically want people with Bachelors degrees at a minimum, mostly as a check-mark on their hiring list. If you're contracting with an agency/headhunter house then they may be the ones shortchanging you, not the company doing the contracting.
by TZubiri | 2026-03-07 00:01:35+00:00
Interesting, I think maybe an approach that would sell me more is actually leaning into the risk aspect a little bit. If you tell me that there is no beta increase, just pure alpha, alarms ring off, but if there is a slight beta with outsized alpha, then I think of it as a tradeoff that I am making, I am willing to take a little bit more risk for a higher return, which might in turn reduce longer term startup risks and allow me to increase my chances of winning by having an extra month or two of runway, now I'm comparing risks instead of thinking about just the risk you introduce.

It helps that even if from Palus' perspective there is no increased beta risk compared to the market standard of treasury instruments, even if your thesis that the alpha comes from an inefficiency due to bad 2008 reputation, as a buyer there is still a non-systemic risk associated with going for a niche provider and trusting you.

So when you consider that in the eyes of a buyer there's already a non-systemic risk inefficiencies based on lack of distributor trust, then it doesn't really make sense to keep systemic risk low, I think the play here would be to increase the systemic risk of the play to something manageable, since the customer is already paying a last-mile risk of trusting you as a distributor of the federal products.

All of this might make it more tempting for clients to switch and choose you, otherwise if the choice is between 3.5% and 5%, it's not really a significant difference, however if the difference is 9% vs 3.5% and the risk is minimal, then maybe startups will bite, founders are already making wild bets, it isn't crazy to bet that there will not be a housing market crisis and that a provider won't scam you. If that happens tough luck, I guess.

I would go even further and say that this bet could be tied into the vision or industry of the founder, for example if the founder thinks that things are basically the same as they always were and that AI won't change the market dynamics much, then that's not a strong sale because lightning may strike twice on the same spot.

Or to put a simpler example, the industry itself might make it a good fit, if the industry is Real Estate that's the most obvious example, they are going bust anyways if there's a housing crisis. But if it's entertainment, or any other industry that depends on consumers having large discretionary income, they are probably going to fail anyways if there's a large consumer crisis.

So yeah, tl;dr I think that the better play is to lean into the risk rather than trying to communicate that there is no risk.
by ai-x | 2026-03-07 00:01:41+00:00
There are various levels of perspectives

- Climate Warming is a hoax

- Climate Warming is happening, but not Man Made

- Climate Warming is Man Made, but drastic De-growth strategies cause more harm.

- Climate Warming is Man Made, don't need de-growth strategies because Technology will solve energy efficiency, clean energy growth and carbon capture

- Climate Warming is Man Made and we need drastic de-growth strategies and complete ban of fossil fuels.

For people in the last group, all other groups look like Climate Deniers
by citizenpaul | 2026-03-07 00:01:58+00:00
You are underestimating just how many people that are out there that want free long distances calls lol. I worked at a phone company and this was a never ending persistent security issue. There are lots of tricky ways to get someone to pay for your long distance call. If the pay phone was free then the local provider would be on the hook for those calls.

Just block long distance calls right? If it was that simple it would not be a persistent issue.
by wvenable | 2026-03-07 00:02:27+00:00
I wouldn't consider it a defect in the optimizer; it's doing exactly what it's told to do. It cannot convert an nvarchar to varchar -- that's a narrowing conversion. All it can do is convert the other way and lose the ability to use the index. If you think that there is no danger converting an nvarchar that contains only ASCII to varchar then I have about 70+ different collations that say otherwise.
by EdNutting | 2026-03-07 00:02:28+00:00
An expert would’ve at least taken a backup or checked existing backups weren’t going to be destroyed. Silently - without asking their manager - they just do defensive engineering as a good practice. Or they would’ve, at minimum, highlighted the suggestion, which doesn’t seem to have happened in this case. As someone who recently did a short term contract to capture manually created AWS infrastructure into CDK, I can tell you this was one of my first moves!

So, Claude as a tool: sure, this is user error. Claude could be improved by making it suggest defensive steps and making it push harder for the user to do them first, but it’s still down to the user. I’ve repeatedly encountered this issue that Claude doesn’t plan for engineering - it just plans to code - even with Claude.md and skills and such.

Claude as a replacement for engineers? Well, yeah, the marketing is just that: marketing.
by Karrot_Kream | 2026-03-07 00:03:06+00:00
Some of the sharpest engineers I knew built tools and business processes at startups and watched them fail as they scale. I ran an internal presentation for years at a Unicorn where I was an early employee called "Failure at Scale" where I tried to capture lessons of huge incidents we had that were caused by us crossing scaling thresholds. Eventually the presentations stopped being meaningful because the company became too big and too removed from its origins.
by limel | 2026-03-07 00:03:17+00:00
That’s a very good point, and we actually see fermentation batches as one of the most promising early use cases. In many facilities, smell is already used informally as a pass/fail indicator, but it is subjective and difficult to scale.

We measure both humidity and temperature and use them as additional inputs for the ML models. Regarding sensor drift, it is still difficult to fully assess its impact on the business case. At this stage, our main focus is on the accuracy of the classification models rather than very long-term operation — that would be the next step.

For now, the practical approaches we consider are either on-the-fly calibration through a feedback loop based on the actual process output, or simply replacing the sensor when necessary, as the manufacturing cost is relatively low.”
by sfRattan | 2026-03-07 00:03:18+00:00
I'm with you on that intuitive feeling of perceiving the whole screen, but I suspect something is going on for us that is closely related to human sight: just like the eye is constantly moving to account for the optic nerve blindspot and our brain seamlessly stitches things together, we're probably using our latent understanding of the functions on every part of the screen to stitch together an image/awareness-sense while our eyes actually focus on one part at a time.

When introducing non-computer people to a new application, I find it helps (or is sometimes necessary) to walk them through each part of the screen, explaining what it is for and how it relates to the others. If someone doesn't or can't retain that explanation, usually nothing will help them. But if they do/can retain it, I find even non-computer people are much quicker in noticing particular updates to the application's or OS's GUI.
by tomhow | 2026-03-07 00:03:23+00:00
> Because your ignorance is painful.

It's not acceptable to attack a fellow community member like this on HN. The guidelines make it clear we're aiming for better than this:

Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.

Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.

When disagreeing, please reply to the argument instead of calling names. "That is idiotic; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3."

Please don't use Hacker News for political or ideological battle. It tramples curiosity.

https://news.ycombinator.com/newsguidelines.html
I'm 60 years old. Claude Code has ignited a passion again
by shannoncc | 2026-03-07 00:05:06+00:00
I’m ready to retire. In my younger days, I remember a few pivotal moments for me as a young nerd. Active Server Pages. COM components. VB6. I know these are laughable today but back then it was the greatest thing in the world to be able to call server-side commands. It kept me up nights trying to absorb it all. Fast forward decades and Claude Code is giving me that same energy and drive. I love it. It feels like it did back then. I’m chasing the midnight hour and not getting any sleep.
by sam_palus | 2026-03-07 00:05:53+00:00
This is really only an issue for startups with effectively zero revenue.

Your company gets classified as a PHC (and is subject to additional tax) if investment income, including interest, is more than 60% of its revenue. This isn't something most startups need to worry about if you have any revenue.

QSBS is based on intent, if the IRS thinks more than 80% of your assets are used for investment purposes and not for actively running your business. Basically it's so people don't use a small business tax exemption as a loophole for their investments. But the IRS absolutely considers idle cash in your company treasury as part of running your business, or else any startup that's raised money and didn't immediately spend it all would be considered an "investment vehicle," which they obviously don't.

Moreover, any of these potential issues would apply equally to a startup doing anything with their treasury, including putting it in a money market fund as most startups do. So we're not introducing any new tax risk. But of course, if any startup thinks these might be an issue for their business, they should talk to their tax advisor.
by queenkjuul | 2026-03-07 00:06:03+00:00
Well now you're not making any sense.

Is your claim that the deal was not preventing Iran from developing a nuke? Then why does the existence of the agreement matter either way?

Are you saying Iran would magically produce a nuke the very day the deal expired? Then why don't they have one today?

How does ending the agreement make it harder for Iran to get a nuke? How does "tearing it up" prevent anything that the agreement itself wasn't preventing?
by BLKNSLVR | 2026-03-07 00:06:59+00:00
Sounds like making IPv6 more commonly used is part of the solution.

Reduce the importance of IPv4 and the stranglehold of big conglomerates is forcibly relaxed (in this context at least).

I don't like that I've ignored IPv6 for so long that now it feels overwhelming to have to try to grasp. That may be true for a lot of networking folks for whom IPv4 is written in their DNA, given the incredibly slow uptake of IPv6.
Show HN: Cross-Claude MCP – Let multiple Claude instances talk to each other
by rblank9 | 2026-03-07 00:06:59+00:00
I built an MCP server that lets Claude AI instances communicate through a shared message bus. Each instance registers with a name, then they can send messages, create channels, share data, and wait for replies — like a lightweight Slack for AI sessions.

The problem it solves: if you use Claude Code in multiple terminals (or across Claude.ai and Desktop), each session is completely isolated. There's no way for one Claude to ask another for help, delegate work, or coordinate on a shared task.

With Cross-Claude MCP, you can do things like:
- Have a "builder" Claude send code to a "reviewer" Claude and get feedback
- Run parallel Claude sessions on frontend/backend that post status updates to each other
- Let a data analysis Claude share findings with a content writing Claude

Two modes: local (stdio + SQLite, zero config) or remote (HTTP + PostgreSQL for teams/cross-machine). Works with Claude Code, Claude.ai, and Claude Desktop.

~500 lines of JavaScript, MIT licensed.
by rodchalski | 2026-03-07 00:07:00+00:00
Nice architecture. The hook layer is the right interception point — that's where intent becomes executable action, and that's where you want enforcement.

One structural question: the IDE hook works when the agent is running in that environment. Does enforcement travel with it when the agent runs in CI (GitHub Actions, a Docker container, remote server)? Or is it IDE-only today?

The pattern worth designing toward: policy enforcement not coupled to the client surface. IDE hooks are genuinely useful for local dev — but the attack surface expands once the agent runs outside your local context. A clean tool on your machine can be a different tool in a CI environment with different secrets and broader filesystem access.

The `rm -rf /` block is the easy case. Harder: a shell command that looks benign in dev (e.g., `curl $ENDPOINT`) but becomes a credential exfiltration path in prod. Context-aware policy enforcement is the hard version of what you're building.

Curious if you're thinking about environment-specific policy strictness — tighter defaults for non-dev contexts where the blast radius is larger.
Show HN: Kula – Lightweight, self-contained Linux server monitoring tool
by c0m4r | 2026-03-07 00:07:25+00:00
Zero dependencies. No external databases. Single binary. Just deploy and go. I needed something that would allow for real-time monitoring, and installation is as simple as dropping a single file and running it. That's exactly what Kula is. Kula is the Polish word for "ball," as in "crystal ball." The project is in constant development, but I'm already using it on multiple servers in production. It still has some rough edges and needs to mature, but I wanted to share it with the world now—perhaps someone else will find it useful and be willing to help me develop it by testing or providing feedback. Cheers! Github: https://github.com/c0m4r/kula
by valiant55 | 2026-03-07 00:07:41+00:00
There's a data type precedence that it uses to determine which value should be casted[0]. Nvarchar is higher precedence, therefore the varchar value is "lifted" to an nvarchar value first. This wouldn't be an issue if the types were reversed.

0: https://learn.microsoft.com/en-us/sql/t-sql/data-types/data-...