Stringout now supports Canon Cinema RAW files. The kind folks at Canon actually made their SDK available to me, meaning Stringout uses first-party raw data extraction and color science.
EOS C70 .𝚌𝚛𝚖 Cinema Raw Light footage? Yeah just drop it in Stringout.
C500 Mark II 5.9K? Yes, all 15 stops of dynamic range are automatically tone mapped in ProRes proxies and laid out in an assembly edit that opens in Premiere, Resolve, and FCP.
When I was in school the checkout closet was almost all Canon, including a C500 (mark i) that could capture the then-new .𝚛𝚖𝚏 format over SDI with one file per frame. So I made sure that works in Stringout, too.
I'm out here collecting pro codecs like infinity stones. Please please please send me a file that Stringout doesn't support yet because I'd love to fix that for you!
3
5
252
I’m looking for Electric Cloud alternatives, if anyone has any suggestions for a service that was _just_ written on it
Replying to @ElectricSQL
We’re sunsetting Electric Cloud but everything we’ve previously open sourced stays open source.
117
Theo Pak retweeted
This is the IMAX console we have here. Very old, but very reliable. You can see Odyssey is over 250k frames which includes the Dune 3 prologue. This works out to over 11 miles of film at around 630lbs.
People for years told me why I never talked about competitors of Redis. The Zig / Bum drama is a good warning. Do your job, without thinking everything is some form of competition or comparison. So: do your stuff, leave people that act lawfully alone.
when one single programming language becomes someone’s identity they become impossible to reason with. everything becomes self-defense of the internal identity. would be nice to instead have their gifts in the public commons absent that issue. many such cases, unfortunately.
I expect people who work on programming languages to have exceptional taste.
Looking at the blog post from the Zig team, it unfortunately appears they have poor taste. It’s likely to severely impact their future adoption.
147
Theo Pak retweeted
Replying to @mitchellh
Yes, Zig made Bun possible. Bun went from me coding in a smelly room in Oakland for a year solo to a team & among the most widely used tools in the JavaScript ecosystem, and a lot of that is thanks to Zig.
Should’ve held off merging the PR until the blog post was done.
Stringout is not impacted by CVE-2026-44578.
Next.js just got its worst vulnerability ever, CVSS 8.6.
→ affects versions 13.4.13+, 14.x, 15.x, and 16.0.0–16.2.4
→ attackers can access your internal services, cloud credentials, API keys, and admin panels
→ no authentication needed
→ one crafted request is all it takes
→ roughly 79,000 instances are exploitable right now
→ vercel-hosted apps are safe, self-hosted are not
upgrade to 15.5.16 or 16.2.5 immediately.
Readers added context they thought people might want to know
The security fixes for these Next.js vulnerabilities were released in versions 15.5.18 and 16.2.6 on May 7, not the versions recommended here. x.com/nextjs/status/…
1
2
492
Stringout.com is safe from the widespread package supply chain issue! I instituted a 2 week minimum release age long before this
Easier way to protect yourself (if you are not infected yet) is to set a minimum release age in your package manager.
For @npmjs:
`npm config set min-release-age=2d`
For @pnpmjs:
`pnpm config set minimumReleaseAge 2880`
For @bunjavascript:
```
# In bunfig.toml
[install]
minimumReleaseAge = 172800
```
For Yarn:
`yarn config set npmMinimalAgeGate "48h"`
110























