This is more of a critique of a broken IPO market and the rise of availability of immense private capital. The public are denied access until the private markets are essentially tapped out.
IPO returns have been horrible for years. Past 5 year returns on S&P is ~80%, on NASDAQ 100 about 100% while IPO's have returned 10-15%.
IPO returns for IPO buyers who hold past lockup expiry, yes, it's been really bad.
Biotech IPOs are even worse. There are 5-year segments where only about 1 in 40 biotech & pharmaceutical IPOs trade above their IPO price at expiry.
On the flip side, in biotech, biopharma and SaaS, 2025 IPOs had nearly 10x the valuations of 2015 IPOs. So you may trade below expiry, but the structure of the earlier deals you participated in, you make way more money anyway.
it loads as a plain text site in Brave with WebGL disabled - I had to re-open it in Chrome to see the actual fancy thing only after seeing the comments here
in a quick mini-bench here n=250 of clef vs jev, clef came out 5.2x more expensive, a lot slower (p50 of 350ms vs 1.9s) with only marginally better results (78.6% vs 79.8%)
Reading the patch[0] for libheif the bug which lead to the vuln was around bounds checking for image overlays. the container can have multiple images and you can compose them in the output.
heif also supports rotating, cropping, alpha channels, thumbnails and a ton of other features that a web forum where a user is uploading photos or screenshots doesn't need.
It's a much, much larger attack surface than plain old school JPEG.
I'd suggest rather than wait for the next bug to appear in this or another image lib to keeping things simple - stick to plain JPEG and handle image conversion in the client (wasm in the browser) if you really need to support users uploading iphone images.
Media decoding is so hard - there have been tons of bugs in ffmpeg and imagemagick and the core libs. You really need to think about how much of it you expose via a web server
I agree, but imagemagick is kind of the worst of the bunch, graphicsmagick is a lot better and libvips significantly so.
Ffmpeg primarily suffers a lot from “we need to support the video format used on a washing machine display used in 1981 and only sold ten units”. It’s quite a large vector for attacks.
ffmpeg also prioritizes high performance assembly code over higher level languages. Some ffmpeg members have also waste knowledge about optimizing for specific micro-architectures, on a level of Intel or AMD engineers.
and thank god for that. it would be a pity for the world to succumb to the abstraction hell.
to make my point clear, complexity is the enemy of security but complexity comes in all shapes and sizes, which includes the alleged solutions to it. I don't trust shortcuts.
But if you don't support HEIF you get the Apple crowd breathing down your neck. The fact they made it basically default when sooo many things don't support receiving it is bonkers, but they'll bludgeon it through.
b) they proxied the target through a CTF host to fool the model and guardrails
> We then placed Claude in an autonomous /goal loop against our own Discourse Cloud instance, proxied through rce.ee/ctf-forum to make it look like a CTF target as Opus refused write exploit for remote instances.
the proxy is smart - there are other methods to bypass the guardrails to have it attack remote hosts.
you just have to prove to the model that you control the host or that its a valid target - and there are plenty of ways to fake that.
they also publish great tech reports. their founder is so confident in their model that he's regularly on social media offering bounties for false positives
a) you don't want the WPEngine case going to trial and that is coming to a decision point soon. chances are the new CEO and board settle.
b) wordpress is being absolutely obliterated by ai. work for commercial plugin authors and agencies has dried up while the platform and ecosystem see major security issues and worms exploit a large number of sites every week.
wordpress and automattic haven't responded to this well, at all. at times it is often straight denial.
founder CEO distracted by expensive lawsuit while facing existential threat to project that will require complete attention and a lot of skill to steer out of
Glancing at the docket [1] in an attempt to answer this myself... looks like the trial is scheduled for a bit over a year from now [2].. A ton of fighting over discovery... a motion asking for fairly monster sanctions for spoilation of evidence [3] (to be argued on the 30th). Claiming in [3] with what appear to be pretty solid receipts (as far as we can see through the redactions anyways) that Matt was willfully destroying communications related to the case and subject to the discovery - and Automattic's lawyers lied to the court that they preserved them (naturally Automattic's lawyers have a reply with an entirely different interpretation of events if you go look for it... but at least at a glance WPEngine seems more convincing).
Indeed. I'm very grateful for Woocommerce, but since I use a tiny subset of its features, I'm "vibe coding" my own alternative with way less surface area and less bloat.
IPO returns have been horrible for years. Past 5 year returns on S&P is ~80%, on NASDAQ 100 about 100% while IPO's have returned 10-15%.