lol768

Joined 11 years ago

Karma
5,155
Submissions
1,080
Member since
Mar 7
[ my public key: https://keybase.io/lol768; my proof: https://keybase.io/lol768/sigs/usirCkduUZATP9tnCZ31ABcanzQ24kzt_MxDbZx2DIE ]

GitHub: https://github.com/lol768

View on Hacker News

Recent submissions

Comment · 8 days ago
My favourite part from the first video is how much effort it took to drag up from the bottom of the screen to get back to the home-screen. This reflects my experience with how iOS handles touch gestures in general.. also super easy to accidentally activate "Reachability" mode!
Comment · 10 days ago
Fully agree. Moved to FrankenPHP's static build (which was ready very quickly) to get away from it. Don't intend to ever use the "official" images again.
Comment · 10 days ago
> The PHP security team closely monitored and inspected appearing PoCs after the leak but did not identify any functional exploits at the time of release/public disclosure

Okay, but how close did they get? Were they close enough that a determined actor could've (perhaps using an LLM) managed to get to a functioning exploit?

Comment · 10 days ago
The PHP Foundation should manage it, the Docker ""Official" Images" approach clearly just doesn't work properly for responding to vulnerability patches.
Comment · 11 days ago
> as of my comment, this is not endorsed by PHP

Are you speaking officially here?

There are various mitigations suggested online, including completely blocking multipart requests at LB level. Is the combination of both effective?

Comment · 11 days ago
> edit: Mitigation for impacted versions is to set `session.upload_progress.enabled = Off` in php.ini

I think this is only partial mitigation: https://x.com/Dinosn/status/2112717168349712734

I have additionally followed the advice to just ban multipart uploads before the request even touches PHP (luckily my app doesn't use them at all). I do now know if this conclusively resolves it.

Comment · 11 days ago
Comment · 25 days ago
> This stopped once LSP was designed

No, it didn't stop. In my experience, LSPs are still incredibly poor and comparatively primitive vs the actual analysis that JetBrains have implemented. It's night-and-day different in terms of the supported refactorings, actual understanding of the types and the codebase etc.

Also, LSP is just poorly designed and inefficient. JSON-RPC was an awful choice, the specification text is not well-written and the whole thing feels like a Microsoft pet project for VS Code than an open specification that everyone agrees works well.

Comment · 1 month ago
Resolved, but can still affect customers for up to 4 hours...

So many problems here, and no signs of an updated SDK that behaves properly on malformed input.

Comment · 1 month ago
> Every other brand's EV is the machine gun.

Nissan have decent BEVs, though - the new LEAF is great to drive.

I know the United States is significantly behind the curve on EV adoption, but I really don't understand who would want this, it's the worst of both worlds.

Comment · 1 month ago
Comment · 2 months ago
> Accrescent is the end goal for a secure and private app store but it's still in alpha

Note that nobody (new) can submit to it today; the developer console HTTP 503s and is only available to an allow-list of developers.

Comment · 2 months ago
Yes, and the UK's industry body - Rail Delivery Group - has thoroughly screwed up distribution of the timetable data for this trial... so no online retailers (with the exception of BR Fares) will be selling tickets for the operation. Hardly a fair trial.
Comment · 2 months ago
Issues seems to be completely broken, just getting unicorns.

Interestingly the API still works for creating an issue (but webhooks weren't fired).

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton