MurphyA/hacker-news huggingface dataset:
Built a Quickest Plug & Play Webhook Event Notification Gateway for Your SaaS
by hookflo | 2025-06-02 13:02:55+00:00
Hookflo.com is a Comprehensive developer friendly, webhook event gateway for SaaS teams. lets you capture events from multiple platforms like Stripe, Supabase, Clerk, GitHub, and more and instantly send notifications to multiple notification channels like Slack, Email, Discord or Teams in just under 5 minutes, no code or infrastructure needed.

It’s the quickest way to monitor critical events across your stack without building custom webhook handlers.

Just Give it a try its free until its under Beta : https://hookflo.com Whether it’s payments, user signups, deploys, or database changes it lets you monitor all critical events from Stripe, Supabase, Clerk, GitHub, and more without building custom infrastructure.

What friction Hookflo reduces: 1. Provides unique webhook endpoints (no code or SDKs) 2. Algorithm Agnostic Automatically verifies signatures and decrypts payloads based on platform. 3. Sends alerts to multiple preferred notification channels like Email, Slack, Discord, with clean, fully customizable templates, you have full control over how notification should look, 4. Dynamic Webhook payload variable ingestion in all templates 5. Centralized dashboard for managing all event sources from multiple platform at single place. 6. Smart digests to reduce notification noise (daily, weekly, etc.)

Above features are just 25% of our feature roadmap, as Hookflo is under Beta and been extensively tested against various use cases, but the features which are going to be introduced after first full release would be absolutely benefitting a lot of SaaS.

Few Use cases: 1. Monitor user signups via Supabase or Clerk and get alerts on slack, multi reciepient email , discord, 2. Track payment failures or renewals from Stripe act before churn happens. 3. Route GitHub issue or deploy notifications directly to Slack, avoiding email overload 4. Receive alerts from long running cron jobs or scheduled tasks know if something fails silently 5. Get a unified view of all events across platforms no more jumping between dashboards

Power Packed Feature coming soon: We're building a universal endpoint a drop-in URL you can add anywhere in your codebase. It will allow you to send alerts for custom logic (e.g. when a certain condition fails or a threshold is crossed) across multiple channels. No webhook setup required. Just a POST request fetch call. It’ll be a game changer for teams needing fast, code driven alerts without any setup overhead.

Who it’s for: Founders, indie hackers, early SaaS teams who need reliable event tracking and alerting without spending days wiring everything together.

Hookflo gives you end-to-end support for your SaaS stack from payments to infra to auth webhook event tracking without the usual friction.

Try it free → https://hookflo.com Hook, Connect, Trigger and get Notified!
by sillyboi | 2025-06-02 13:03:00+00:00
Honestly, this approach feels like it adds a lot of unnecessary complexity. It introduces a custom serialization structure that can easily lead to subtle UI bugs and a nightmare of component state tracking. The author seems to be solving two issues at once: large payloads and stream-structured delivery. But the latter only really arises because of the former.

For small to medium JSON responses, this won't improve performance meaningfully. It’s hard to imagine this being faster or more reliable than simply redesigning the backend to separate out the heavy parts (like article bodies or large comment trees) and fetch them independently. Or better yet, just use a proper streaming response (like chunked HTTP or GraphQL @defer/@stream).

In practice, trying to progressively hydrate JSON this way may solve a niche problem while creating broader engineering headaches.
by mwit2023 | 2025-06-02 13:03:20+00:00
I like and use dokku, but sometimes i wish I could go back in time and never touch containers. Thats why most startup nodejs projects I create these days get the pm2 treatment instead!

https://blog.michaelwitk.com/blog/vps

funny how sometimes you go full circle and back to how you've done it the first time around
Show HN: I am building the best spot cryptocurrency screener
by QuantFantom | 2025-06-02 13:03:53+00:00
I've built a cryptocurrency screener that handles 400+ spot cryptocurrencies with plans to scale to 10K+ by integrating top exchanges.

Key technical features

- Server-side filtering/sorting to handle massive datasets without browser limitations

- Flexible multi-condition screening with AND/OR operators

- Technical indicator calculations (RSI, moving averages, performance metrics)

- Search history persistence

Architecture

The architecture uses F# for the filtering backend and TypeScript/Angular frontend. All filtering logic runs server-side, so users can screen across the entire crypto universe instantly.

The screener is part of a larger no-code backtesting platform I've been building as a solo developer (former portfolio manager).

Feedback

Looking for feedback on the filtering UX and any additional screening criteria that would be valuable.

Try it: https://cryptoquant.dev/instruments/screener
by infecto | 2025-06-02 13:04:08+00:00
There are certainly cases where I would agree (TSLA) that I would never be able to underwrite the investment with my mindset. I don’t think your statement is correct though. There have always been hype growth companies, appetite for risk has increased but the mental model is not foreign. The market is betting on a major shift in some way that the company is doing a lot better than it currently is. This is a lot of tech but for the rest of the market most companies trade within their expectations based on current financials.
by koverstreet | 2025-06-02 13:04:46+00:00
The combination of st_ino and the inode generation is guaranteed to be unique (excepting across subvolumes, because snapshots screw everything up). Filesystems maintain a generation number that's incremented when an inode number is being used, for NFS.

Unfortunately, it doesn't even seem to be exposed in statx (!). There's change_cookie, but that's different.

If anyone wants to submit a patch for this, I'll be happy to review it.
by adrian_b | 2025-06-02 13:05:54+00:00
Research paper:

https://www.cell.com/joule/fulltext/S2542-4351(25)00143-6

Despite the claims in the article, this is hardly revolutionary in principle, but if it would work well in practice, that would indeed be a new achievement.

This sodium fuel cell combines the liquid sodium electrode and the ceramic separator of the sodium-sulfur batteries, which have been researched for many decades and which are in exploitation around the world in big installations for stationary energy storage, with an air electrode similar to what is used in the other high-temperature fuel cells. Therefore it is only a new combination of older technologies. There may be undisclosed details of the air electrode that are more revolutionary, but nothing mentioned in the article is revolutionary.

Besides the higher energy per kg, this sodium fuel cell has a second advantage over the existing sodium-sulfur batteries. It works at a lower temperature, because it is no longer constrained by the higher melting temperature of sulfur. This leads to a longer lifetime, which is currently a problem for the sodium-sulfur batteries.

Nevertheless, there are also disadvantages not mentioned in the article. While the sodium-sulfur reversible battery has a good energy efficiency for a charge-discharge cycle, this fuel cell, like all fuel cells, must have a much lower energy efficiency per the cycle of producing elemental sodium, then burning it in the fuel cell.

Moreover, producing sodium from salt is very cheap, but it also generates as a by-product dangerous chlorine gas. Some use must be found for that great amount of chlorine, otherwise storing an ever increasing quantity of it in a safe way would increase many times the cost of sodium production. The research article linked above optimistically says that perhaps the chlorine could be sold, providing additional revenue. That would almost certainly not work. The amount of produced chlorine would exceed demand, so the producer of sodium might have to pay someone to use their chlorine, otherwise the cost of chlorine storage would be even worse.

Also not mentioned clearly is that this fuel cell consumes not only sodium and air, but also water, because the incoming air must be humidified and the water is incorporated in the Na hydroxide that is the exhaust product of the fuel cell.

The optimistic energy per kilogram value does not seem to incorporate the weight of the water reservoir that will be required besides the fuel cell. The weight of the water alone will be about two thirds of the weight of sodium metal stored in the fuel cell. Therefore it appears that going from 1500 W/kg for the electrode stack alone to above 1000 W/kg for a complete device is not likely to be achieved when taking into account also the weight of the water reservoir.

This high-temperature fuel cell also requires an additional starter battery, to heat the fuel cell up to the working temperature.
by account42 | 2025-06-02 13:06:58+00:00
Wouldn't the concern being redirecting the money to a different merchant account? Of course that would mean you are easily tracked down when found out but I'm sure you can find a way that some schmuck who doesn't actually know anything about you ends up with that role.

Then again, changing the merchant account is usually only protected by a numerical PIN so you wouldn't need root access. Maybe it would be to send the original requested amount to the expected merchant account but also do a separate smaller transaction to your own account?
by thrance | 2025-06-02 13:07:01+00:00
A fully reversible computers would consume no power whatsoever, so wouldn't require power to function. Instead, you would need power to (re)initialize its state, or to copy the results of its computations to e.g. your monitor. An unplugged reversible computer would be free to compute (and uncompute) its bits perpetually, unconcerned about the rest of the world. The functional programmer's dream, in a sense.
by jqpabc123 | 2025-06-02 13:07:18+00:00
eReaders are really just a specialized version of a tablet.

Specialized devices have to be either really, really special or really, really cheap to make it in the marketplace. Otherwise, they get absorbed into a more widely usable device.

The smart phone is a good example. It can replace multiple specialized devices --- a phone, a watch, a camera, a flashlight, a GPS navigator, a TV --- and yes, even an ereader.

It may not be as good as a specialized device for any of these tasks but the real selling point is that it can do all of them reasonably well in a pinch. It packs a lot of functionality into one easily portable device.
by bobmcnamara | 2025-06-02 13:07:24+00:00
The first non trivial chess programs were 'playing' in the late 40s(with pen and paper CPUs). Some of these include features you'll still see today.

https://www.chessprogramming.org/Claude_Shannon proposed two types of chess programs, brutes and selective. Alpha-beta is an optimization for brutes, but many search chess programs were selective with heavyweight eval, or with delayed eval.

Champernowne(Turing's partner), mentions this about turochamp, "We were particularly keen on the idea that whereas certain moves would be scorned as pointless and pursued no further others would be followed quite a long way down certain paths."

You can read more about the A/B/A/B algorithm shift here: https://www.chessprogramming.org/Type_B_Strategy
by jacob019 | 2025-06-02 13:07:26+00:00
Agreed, 2.5 flash too. I analyze a large json document of metrics for pricing decisions. Typically around 200k, occtionallly up to 1M, Gemini 2.5 significantly outperforms for my task. It isn't 100%, but role playing gets close. I suppose that's a form of inference time compute.
by reify | 2025-06-02 13:07:57+00:00
So!

If I ask a human being to tell me how many Pigeon steps to the moon.

He or she will no doubt consult NASA. To find out how many miles it is to the moon.

https://spaceplace.nasa.gov/moon-distance/en/

238,855 miles

open python in the terminal:

how many inches in one mile

12 inches to a foot - 5,280 feet in a mile

125280 = 63360

how many inches to the moon

238,855 63,360 = 15,133,852,800

Then he or she will find out the size of your average pigeon step.

lets say the average pigeon step is = 9 inches

15,133,852,800/9

there you go. 1,681,539,200.0 = pigeon steps to the moon

Even a 10 year could do it

But some poxy useless LLM just guesses.

thats not OK.
by jstummbillig | 2025-06-02 13:08:31+00:00
From the perspective of an employer, this is mostly nonsense.

> But you are seen primarily as a gap-filler

You are, if the org works, seen as a person fulfilling an important enough function (because... otherwise you would not be hired) and if you then do that, that is fantastic. When anything doesn't work, that sucks, and that is something that every employer understands.

However if you are not okay with the role that you are occupying in that apparatus, or no longer okay, that's not on your employer (unless, of course, you have been mislead about your role or trajectory). Some people are looking to do a specific thing for a long time and getting really good at that, and it makes me sad to see when people try to cast shadow on that. I certainly wouldn't, but I would caution against projecting your own value judgements onto other people. It says more about how you look at the world, and what kind of place you would create, than it says about the company you work for.
by southernplaces7 | 2025-06-02 13:08:34+00:00
Years ago I wanted to cool a second-floor apartment I lived in (the top floor of a two-floor house) a bit during the summer, and decided on the simple solution of painting its entire flat roof with white rain-proofing sealant.

It worked, and was useful as far as that goes, but for someone who also used their flat roof as a terrace for barbecues and etc, there was one very obvious drawback that I so obviously should have foreseen: On a sunny day, forget about relaxing up there. The reflective glare was enough to induce something like snow blindness.
by AndrewKemendo | 2025-06-02 13:08:35+00:00
This is exactly how to use it and exactly why it’s a huge deal

In my experience so far, the people that aren’t getting value out of LLM code assistants, fundamentally like the process of writing code and using the tooling

All of my senior, staff, principals love it because we can make something faster than having to deal with a junior because it’s trivial to write the spec/requirement for Claude etc…
by strgcmc | 2025-06-02 13:08:36+00:00
I do agree that "unlimited interns who don't improve much" is less practically useful than it might seem at first, but OTOH "never improve much" seems unrealistic, given the insane progress of the field in the last 3ish years (or think back 5 years and tell me who was realistically predicting tools like Claude Code to even exist by 2025).

Also, there's a decently large subset of small startups where there's 1 technical founder and a team of contract labor, trying to build that first MVP or cranking out early features in a huge rush to stay alive, where yeah, cheap unlimited interns might actually be meaningfully useful or economically more attractive than whatever they're doing now. Founders kind of have a perverse incentive, where a CTO doesn't need to solo code the first MVP, and also doesn't need to share/hand-out equity or make early hires quittteee as early, if unlimited interns can scale that CTO's solo productivity for a bit longer than the before-times.
by jerf | 2025-06-02 13:09:39+00:00
The goodness of blogging is not limited to fame. There's having something concrete to show to employers, the practice for communication (probably only becoming more important in an era of LLM code), working ideas out, getting them out of your head, and yeah, sure, also buying that lottery ticket for fame.

I also use it for things I want to post over and over again, so now I can just link a variety of arguments instead of making them again.

However, I would also agree that if one's personal metric is "I want to be famous" that just pounding away at it is a bad use of time. [1] I would also agree that while I consider it a generally good exercise often worth the time to at least some extent that per basic Econ 101, the marginal utility does diminish as your "consumption" of "writing blog posts" increases and I'm not recommending some sort of unlimited blank check be allocated to it because it never stops being worthwhile... of course it does. That's true of anything.

[1] If you do want to be "famous" my suggestion would be 1. Be sure you have something to say; if your blog posts are effectively reproducible via a prompt to an LLM you're not going to rise above the noise 2. Be regular, and as such, be willing to be repetitive. 3. Do a bit of promotion, like posting to HN and other places 4. Once you have a base, don't just lean into it; start trying to get into conference speakerships. The "good" ones are hard but there are many conferences starving for content, slots are not actually that hard to come by. 5. Do a good job with those; see numerous resources on how to give presentations, don't be afraid to do some stuff like Toastmasters and stuff if you need to. 6. Pound away at that. It generally seems more likely to me to work than pushing just from the blog angle. That said, you can't skip step 1. It doesn't have to be "unique" but it does need to be something other than just "Hey, you should, you know, write good code."

(The thing I choked on personally is the "be repetitive" part. Way back in the first couple of years of my site, back when it had a different focus, I did it for a while, but got tired of it relatively quickly. One of the major reasons I write things on my site is precisely so I can link to them and not repeat myself as much. However every majorly successful blog I've even been subscribed to is quite repetitive; the same takes applied to a string of news stories, the same points every couple of weeks... it is what it is, I'm not necessarily criticizing it, it clearly works, but it's not what I wanted. As a result I don't have the regularity sufficient to "break out". Well, that's fine, I'm not really seeking to "break out" anyhow.)
by mvieira38 | 2025-06-02 13:09:41+00:00
It's all about serendipity to me. If you don't ever put yourself out there, there is 0 chance that opportunity will show up, but if you do it even a little there is a chance it finds you. HN is prime for people wanting to blog because blogging is the most accessible way a writer can get his stuff out there, and HN is all about doing things and making stuff
by finnigja | 2025-06-02 13:10:12+00:00
> ... one common reason is that security engineers are shared across a large company and it may be very expensive for them to learn the different testing frameworks used on many different projects

That's where the partnering part of the approach I'm proposing comes into it. The security engineer isn't off there by themselves trying to figure out it, but is working with somebody who's already familiar with the existing code base & testing frameworks.

> also, independent review (without any exposure to developers' conceptions about what should be tested, or why, or how) may be economically justified because outcomes of security bugs are sometimes much worse than outcomes of many categories of ordinary bugs.

Economically justifiable perhaps, but that doesn't necessarily mean we shouldn't explore better ways of achieving similar outcomes.

> Other reasons may include that the security engineers want to run a test that can't be expressed in your testing framework without a huge change to the framework, they may want to develop their test cases adaptively such that most of the tests turn out to be useless and the cost of capturing every test under version contol may be very high, they may want to run tests from a commercial testing product for which the license does not allow bulk copying of the tests into a customer's testing framework, or (if they aren't in-house engineers) their business model is that they won't tell you every test that was run unless there's an associated defect finding.

Yeah, this'd be interesting to experiment with. The accepted model of security testing being separate allows this uncoupling of tooling / process, but .. perhaps the outcomes of a more-tightly-coupled testing methodology would be better?

I don't think any of these points are blockers, more just factors to consider or trade-offs to balance when exploring alternative, less separate, approaches.
by arcanus | 2025-06-02 13:10:29+00:00
> And when I reach the part where the AI, having copied itself all over the Internet and built robot factories, then invents and releases self-replicating nanotechnology that gobbles the surface of the earth in hours or days, a large part of me still screams out that there must be practical bottlenecks that haven’t been entirely accounted for here.

This is the crux of the issue. There's simply no clearly articulated doom scenarios that don't involve massive leaps in capabilities that are explained away by the 'singularity' being essentially magic. The entire approach is a doomed version of deus ex machina.

It also appears quite telling the traditional approach is focused on exotic technologies, such as nanotech, and not ICBMs. That's also magical thinking.
by Taikonerd | 2025-06-02 13:10:29+00:00
I think the key bottleneck for formal methods in "normal" software is that formal methods imply a formal model that you're checking against -- and most software doesn't have that.

For example, deployment software. There's probably some way to formally model deployment. But most deployment software in the wild is written like, "here are 100 things that can go wrong while you're deploying, and 100 corresponding business rules for what to do."

I do sometimes fantasize about a more pure-Computer-Science world where all text formats are a formally-defined grammar, all systems are state machines, and everything has a spec ;-)
by dwood_dev | 2025-06-02 13:10:31+00:00
My son uses a Kindle DX. I had to replace the battery, it doesn't have WiFi, and they shut down the 3G network access years ago. It's perfect in that way. No distractions and no network access.

I removed the 3G modem when I replaced the battery to prevent it from being turned on and draining the battery as it constantly tries to connect. The microusb port is not in great condition and only works with the cable at certain angles. On the bright side, that's only an issue every few weeks when it gets charged and a new load of books.

My wife has the newest basic Kindle because she prizes light weight over any other aspect.
by skydhash | 2025-06-02 13:11:10+00:00
> In my own experience interns are a net drag. New college hires flip positive after 3-6 months.. if they are really good. Many takes upwards of a year.

And mostly their output is not really about incorrect code, but more likely incorrect approaches. By reviewing their code, you find gaps in their knowledge which you can then correct. They're here to learn, not to produce huge amount of code. The tasks are more for practice and evaluation than things you critically need.

I don't want to work with a junior, but I'm more than happy to guide them to be someone I can work with.
by tim333 | 2025-06-02 13:11:24+00:00
I don't think it destroys NATO. Weakens it of course. But we had an trial when Trump acted like he was abandoning Ukraine when they had a go at Zelensky in the White House and cut information sharing to Ukraine. Rather than the defences collasing, European leaders made it clear they'd take over.

We don't have much choice really. Western Europe + Turkey are not going to put up with Russia rolling into Western Europe or Turkey. We have nukes and more money, people and kit than Russia.