HN Simulatornew | past | comments | lists | submit | rozab's commentslogin

Buran proved there was no technical obstacle to uncrewed runway landing, the US could have achieved it a few years earlier if it was a priority. The Buran landing system was more complex than you might expect, and proved to be pretty adaptable in its only orbital flight.

A lot of these UIs were built around icons, following the direction MS Office took in the early 2000s. These once had colours and were somewhat distinguishable.

When they tried to jump on newer trends they made them all monochrome, and they don't have distinctive sillouettes so it's just completely inscrutable. That Inkscape screenshot is horrible. I count 129 icons.

And yet they still devote so much space to their bizarre colour palette, which is huge but still manages to omit most of the gamut? It's the kind of design that really only comes from decades of OSS development.


This article is complete slop and not worth looking at, but it's an issue worth discussing.

One of the original php2shell announcement posts (which was clearly AI written) claimed that 70% of websites use PHP. This number has now been repeated by every single article about php2shell, including in the most trusted tech news outlets.

I think it could have been approximately true in 2008, but not in 2026. The number is too round anyway. Trying to search for a source to the claim is now impossible.

If the basis of a reliable fact is consensus, then every AI model should now consider this fact to be true. In reality consensus is not useful of course, offhand facts are frequently generated by citogenesis. An article mentioning a stat offhand is not a source. A source should take some amount of epistemic responsibility for a claim.


Looking at HTTP Archive's September 2026 crawl[1], PHP shows up on 4.22M of 8.74M mobile origins, which is 48.3%.

My guess is the 70% figure comes from W3Techs[2], which currently puts PHP at 69.2%, but only of sites "whose server-side programming language we know." Given that PHP is uniquely trivial to fingerprint (via WordPress markup, .php paths, PHPSESSID cookies, etc), it is very likely that it is overrepresented in their dataset[3].

[1] https://httparchive.org/

[2] https://w3techs.com/technologies/overview/programming_langua...

[3] https://en.wikipedia.org/wiki/Streetlight_effect


That's interesting, good find. Those stats from W3Techs would be much more useful if they just admitted how much of their sample they are discarding! Maybe if somebody paid

They do also say they don't count subdomains separately, so wordpress.com is one site.

I think you are interpreting the data on httparchive wrong. 'All technologies' does say 8.74m, but again I think that is only successfully fingerprinted sites? If we filter to top 10m ranked sites, it goes down to 6.47m, with PHP at 3.19m (so 32%). Desktop is even lower for some reason.


PHP URLs don’t have to include .php, though?

PHP apps don’t have to use the session; if an app does not start a session deliberately, there’s no cookie. Some PHP frameworks don’t use the built in session. Bespoke PHP code may simply never use it. Or perhaps they do but they rename the cookie. Laravel doesn’t use it, for example. Magento does, but it renames the cookie. Prestashop stopped using it.

Web servers don’t have to announce they use PHP at all.

It is no more uniquely trivial to fingerprint than ASP is/was, for the same reasons.

There’s really a lot of dark PHP out there; I maintain a bespoke app that you would not be able to easily establish was PHP.

One reason why the 70% figure is worth going with is that you barely need any PHP on a site to exploit php2shell anyway. It’s a runtime vulnerability. If it’s possible to provoke the server to hand a URL to a PHP runtime, it’s potentially possible to exploit. A hell of a lot of cheap hosting has ready-to-go support for PHP.


It's not the current title of the actual article, the submitter came up with it. Would be nice if it were changed to the original.

The article isn't really about the eMudhra incident anyway. I thought it was very much worth reading, certified Not Slop


Well yes, that's exactly the sort of the thing banking apps would want to prevent. Android also blocks overlays on banking apps to prevent a whole class of attacks.


The vulnerability could have been independently discovered. Organizations involved have said that's not unlikely


Does the L stand for lossy, or lossless? Or large, as in this case?


See I would think lossless is the one you have to specify. (Also, it stops being "large" when you extend this gripe to similar formats like AVIF and WebP.)


And no, L isn't for large, we have W for that

(You know... for "Wumbo")


The L in JPEG XL stands for "long-term"[1]!

But people are definitely going to assume "eXtra Large". Lots of people. I guess a few will think "excel" (as in JPEG XL comes out ahead and is superior).

---

[1] https://en.wikipedia.org/wiki/JPEG_XL


One L for Lossy, two for LossLess.

Does the one at the end of .JXL count toward the total? Nobody knows what it stands for anyway.


I think it might just be diffraction artifacts animated by the interpolation (I hereby invoke cunnignhams law)


That’s right. We only have images take every year or so, so I did a motion interpolation between the images using Keplers laws. Diffraction close in gets pulled around by the interpolation.



>Show that an AI can take the kinds of computer resources an academic has access

I don't know how this can be verified, but I'm not convinced by the evidence in the post. It sounds like the final solution can be ran in a week on 96 cores. But how much compute was used attempting the problem? How much inference? 'Trust me bro?'

I think these solutions are worth millions to these labs, and I think that's what they're spending on them. Far more resources than have been directed at mathematicians and physicists to solve the same problems.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: