ultrafez

I've seen the term "request coalescing" used to refer to a technique to minimise the impact of cache stampedes. Protects your backend systems from huge spikes in traffic caused by a cache entry expiring.

There are many types of request that cannot be made with client-side JS alone, but for those that can, the ability to send those requests client-side would be handy.

This is very cool - I haven't seen anything like it before. I've spent about half an hour noseying at places I've lived or considered living, fascinating. The view of changing house prices is something that I haven't seen presented in this way either.

Thanks for building it and thanks for sharing.

What model are you using now that fixes the issues you experienced on your 735xt?

We're conflating the Ninja Creami with Ninja's smoothie makers and blenders - they are separate product lines

Is the project named spinup or rallyup? The HN post title differs from the GitHub repo

People might not buy a game if they don't think they'll get a fair play experience.

The poke feature is back! It was re-introduced this year some time.

It also seems reminiscent of KSQL - consuming multiple input topics, and producing output to a topic defined using a query written in a SQL-like language that defines how the inputs are combined and filtered.

Meta point - this page has one of the nicer "snap" scrolling mechanisms I've seen on Mac with a touchpad - scrolling still feels natural, but when I let go it snaps to a single slide. Scrolling with momentum seems to work naturally too. Can't comment on keyboard or mouse scroll wheel navigation though.

Strange. It shouldn't alert you unless the AirTags aren't connected to their own phones - do they leave their phones behind when going for a walk?

This objectively makes the world a worse place. I challenge you to come up with any ethical angle that supports your work on this product.

Your first point is almost a meme at this point - so many products can be written off as pointless with the statement:

> As a [type of tech person], [product] is completely unnecessary as you can easily build a similar system yourself by simply combining [tool A] with [tool B] and [tool C]. It's so simple!

I'm not disagreeing with your point, but it misses the point that often the benefit of using a particular product is that you don't have to build it yourself, not to mention the other benefits you could get from using the exact same system as somebody else (e.g. sharing Postman collections).

Some of the cost might come from buying a computer suitable for video editing, which I can imagine could be a couple of thousand dollars.