Do not forget the new recents ads in Apple Maps.

I’m pretty confident that at least 95% of HN users use adblocking so clearly the users are not worth much to the ad companies. Today I have absolutely zero ads on my devices.

You probably live in a community of some nature, though.

For hiking trails, I highly recommend https://www.comaps.app/. It's simply miles ahead of Google Maps and Apple Maps for hike and biking.

Thanks, will have to check that out! Also use Strava, so maybe I should just refer to the heatmaps

Non-owning view over a single element should simply be a reference, you don’t care where this element is located.

That won't work with NULL.

It can be way more than 2 hours depending on the project.

In your example, idempotency means same request + same state = same response. State becomes part of the request, that’s why it is hard.

That's just deterministic behaviour.

For idempotency you literally just want f(state) = f(f(state)). Whether you achieve this by just doing the same thing twice (no external effects) or doing the thing exactly once (if you do have side effects) is not important.

But if you have side effects and need something to happen exactly once it seems a lot more useful to communicate this, rather than pretending you did the thing.

> But if you have side effects and need something to happen exactly once it seems a lot more useful to communicate this, rather than pretending you did the thing.

I think it depends on whether the sender needs to know whether the thing was done during the request, or just needs to know that the thing was done at all. If the API is to make a purchase then maybe all the caller really needs to know is "the purchase has been done", no matter whether it was done this time or a previous time.

And in terms of a caller implementing retry logic, it's easier for the caller to just retry and accept the success response the second time (no matter if it was done the second time, or actually done the first time but the response got lost triggering the retry).

Yes but LED lights need to be connected to some electricity source, which is inconvenient in some scenarios.

Replace your material content with lorem ipsum or garbage LLM content and upload it to Canvas to test the accessibility of your documents if required.

Wouldn’t a real live render approach work in this case? Have a live preview of your tool inside a rectangle. If the tool is light it should be optimal visually: it will respect browser rendering settings like accessibility parameters or custom addons.

Or just statically build the HTML. That's what we do for iommi docs: https://kodare.net/2025/01/14/iframes-not-screenshots.html

Don't we already have this in HTML5?

Also it would be a security issue?