HN user

waiwai933

693 karma

Email: waiwai95[at]gmail[dot]com

Posts3
Comments133
View on HN

Newer fleets will have GPS units on board that report back to Control, but it's not universal and I don't believe there are industry-wide standards or APIs. Signalbox is definitely extrapolating from TD/TRUST/Darwin, not GPS reports.

Killed by Apple 2 months ago

Why is Apple Watch series 0 even listed? I can _sort of_ see the argument for discontinued form factors generally even though I'd disagree with it being useful to show, but series 0 wasn't a different form factor even.

I think it may help to clarify that there are two Regulations which seem to have been muddled in the comments:

* Regulation 2023/1670 provides, inter alia, that smartphone manufacturers must make replacement batteries available to consumers, except where the 80%/1000 cycle criteria is met, in which case replacement batteries can be made only available to professional repairers. There is also a requirement for it being able to replace the battery but this does permit use of non-trivial tools under certain circumstances.

* Regulation 2023/1542 provides that portable batteries (not limited to smartphones) must be readily end-user replaceable if they meet certain criteria unless the strict waterproofing/medical industry criteria are met.

Maybe some of these questions are obviously answered in a Cloudflare control panel or help document. I’m not in the market right now so I won’t do that research.

I don't love piling on, but it still shocks me that people write without first reading.

I did a free 30 day Kagi trial a month ago, and while I'm not sure I'm convinced the search results are better, they're definitely not worse. I've only fallen back to Google thrice, and in every case, Google didn't find anything useful either.

That said, the most astonishing thing was that I apparently do 100 searches a day, so 3k a month... I'm a bit sad that Kagi doesn't offer opt-in search history because I want to know what it is I'm searching for! (it's across three devices so looking at browser history is just above the threshold of how much effort I want to put in)

I'm surprised - simply because I never get Pinterest results on Google. Now admittedly most of my searches aren't the kind where Pinterest is likely to have relevant results, but even then, surely I'd at least see them _sometimes_. But I literally can't remember the last time I saw a Pinterest search result.

Unless, as you suggest, they take over Google Images but not text search results? I could believe that I use Image search sufficiently rarely that I wouldn't have seen a Pinterest result.

S3 is great for being able to stick files somewhere and not have to think about any of the surrounding infrastructure on an ongoing basis [1]. You don't have to worry about keeping a RAID server, swapping out disks when one fails, etc.

For static hosting, it's fine, but as you say, it's not necessarily the cheapest, though you can bring the cost down by sticking a CDN (Cloudflare/CloudFront) in front of it. There are other use cases where it really shines though.

[1]: I say ongoing basis because you will need to figure out your security controls, etc. at the beginning so it's not totally no-thought.

I’ve seen other examples where customers guess at new APIs they hope that S3 will launch, and have scripts that run in the background probing them for years! When we launch new features that introduce new REST verbs, we typically have a dashboard to report the call frequency of requests to it, and it’s often the case that the team is surprised that the dashboard starts posting traffic as soon as it’s up, even before the feature launches, and they discover that it’s exactly these customer probes, guessing at a new feature.

This surprises me; has anyone done something similar and benefitted from it? It's the sort of thing where I feel like you'd maybe get a result 1% of the time if that, and then only years later when everyone has moved on from the problem they were facing at the time...

My understanding is that the crush risk at Euston is entirely an operational issue of Network Rail's making (NR being the station facility owner), by deliberately not announcing platforms until the last moment, causing passengers to run to the platform en masse. If platforms were announced earlier, the crush risk would be seriously mitigated.

The obvious next question is whether platforms _can_ be announced earlier - to which the answer is, as I understand it, yes. The platforms are known about much further in advance and the reason for the delay appears to be a combination of intransigence by Euston management and a lack of sufficient ticket gateline staff by the train operators.

We're really looking forward to Windows support - I don't think any Actions runners vendors supports Windows at the moment and we were looking at building our own runners as a result, but if this launches soon, we'd be very keen to try it out!

Even if Apple were to defeat the geofencing trick, it's trivial to hide behavior:

1. Make an API call to your server with the build number of the app.

2. Have that API response control whether the "secret" features are available.

3. Only enable each build's secret features once it's passed review.

4. Profit?

No dynamic/interpreted code required.

And there are sufficient variations on this that I would guess it's reducible to the halting problem and thus undecidable.

I'm not sure that's necessarily practical though - if I'm dropping a link in Slack to a colleague

You want to look at [a123456](some.git.url/a12345678...) to see where we've done this before

I can't promise that the repo won't have changed by the time they look at it (but because the full hash is linked, it's not a problem in practice).