Security called me at 6:12 AM today. "Patch every PHP server immediately." I asked what happened. "Two critical vulnerabilities. Remote code execution. No authentication required." Cool. How many PHP servers do we have? According to inventory: 12 According to reality: Nobody knows. We found one running WordPress. Three running old internal tools. One under someone's desk. Two inside vendor appliances. A forgotten employee directory from 2016. And a server named: PHP-OLD-DO-NOT-TOUCH Naturally, that one runs payroll exports. Then we found a PHP 5.6 box. I asked who owned it. The documentation said: BRIAN. Brian left in 2019. We called Brian. He said: "Oh wow, that's still running?" Excellent. By 8 AM, leadership joined the incident call. CEO: "Can hackers actually get in?" Security: "Potentially yes." CEO: "Without a password?" Security: "Yes." CEO: "Then why do WE need passwords?" Not the lesson. Finance asked if we could wait until the weekend to patch because downtime affects revenue. Security explained that the alternative was letting strangers execute code on our servers. Finance asked for a cost comparison. At 9:17, someone suggested temporarily taking the vulnerable websites offline. Marketing refused. "Our campaign is live." So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover. We finally patched everything we could find. Then our scanner discovered another PHP server. Hostname: TEMP-PHP-2014 Uptime: 4,512 days. Nobody knows what it does. Nobody owns it. Nobody can shut it down. But every time we block network access, the warehouse stops printing shipping labels. Security has classified it as critical infrastructure. It is running PHP 5.4. The vulnerability has existed longer than half our employees. The emergency patch took four hours. Finding out what PHP actually runs took eleven. The internet isn't held together with code. It's held together with servers everyone is afraid to turn off.

Locize now checks every AI and machine translation against its source before storing it: syntax, placeholders, tags, and in MessageFormat and Fluent the plural forms of the target language. Also new: MessageFormat 2 as a project format. locize.com/blog/ai-translati…

Our first Fluent prompt rule got 57% of Russian, Polish, Ukrainian and Czech test plurals right. The fixed rule got 100%. Prompts help, but the safety net is checking every AI translation against its source before it is stored. What we built and measured: locize.com/blog/ai-translati…

Your AI just translated "Save" as "saving money". 🐷 Translation is solved. Trust isn't. 90 seconds on what breaks when nothing checks a translation, and what to do about it. locize.com/end-of-translatio…

@locize connects continuous localization with modern development workflows, combining real-time translation delivery, MT and LLM providers, linguistic context, and AI-powered quality estimation. Kudos to Adriano Raiano, for helping us keep the profile up to date! Explore: zurl.co/5BCFB #Localization #TMS #TalkToNimdzi

Translation errors are rarely bad language. ~2.3% of translated segments have a mechanical defect: dropped placeholders, broken tags, changed numbers, damaged whitespace. 87% of projects translate at least one term inconsistently. locize.com/blog/translation-…

<< At @GSMtasks we help manage deliveries and services... We translate and host all our translation files in Locize, so it has become our TMS hub. It keeps everything organized across languages. By now we couldn't imagine doing localization without it. >> locize.com/customers#gsmtask…

"AI killed the TMS" is half right: the mechanical layer got cheap. The review, consistency and provenance layer didn't. An honest take incl. a build-or-buy framework: locize.com/end-of-translatio…

Looking for a continuous localization platform? Built by the creators of i18next, @locize combines real-time localization, AI quality estimation, and developer-friendly workflows to help teams ship multilingual content faster. Thanks to Adriano Raiano for collaborating with us on the profile. Explore it in Nimdzi's TMS Feature Explorer: zurl.co/lKrh4 #Localization #TMS #LanguageTechnology

<<Locize fits seamlessly into our development workflow, saves our team valuable time, and helps us deliver a consistent experience to customers across different languages. It's simple, reliable and does exactly what we need it to do...>> locize.com/customers#halo

After 16+ years on @github, I’m finally a star. ⭐️

Hey folks 👋 Quick reintroduction for anyone who's new here: For the better part of the last decade I've been building the plumbing that a huge chunk of the internet quietly runs on. Mostly, I'm a "Nebraska" developer but I live in Forlì, Italy. I'm the Co-Founder & CTO of @platformatic, where we're rethinking how teams run Node.js in production. Less glue code, fewer 2 am pages, more shipping. On the open-source side, I create and maintain things you've probably got in your node_modules right now: Fastify (the web framework), Pino (the fast logger), and a long tail of libraries that were downloaded 42 billion times in 2025. I also sit on the Node.js Technical Steering Committee, mostly nerding out over streams, diagnostics, and HTTP. People sometimes assume the OSS work is a side quest to the "real" job, but honestly, it's all one thing to me: figuring out how to make the web faster, more reliable, and more fun to build on. Some of it's under a company roof, a lot of it's out in the open. The part that's kept me going for years, though, isn't the download counter. It's the community: the maintainers, the first-time contributors, the folks I get to mentor and learn from at conferences and in issue threads. That's the good stuff. Off the clock: one wife, one daughter, one poodle. A perfectly balanced household, which is more than I can say for my dependency tree. In the summer, you'll find me sailing to blow off steam. ⛵ Good to see you all. Let's build something. 🚀

Slop security vulnerabilities are the worst. They just burn maintainers' goodwill and time.

We scanned the top 100,000 websites to see who actually runs on i18next. At least 1,534 do. @X, @gitlab, @Deezer, @Strava, DeepL, @Microsoft Power BI, @UEFA, and many more. Full data + a searchable list of every one we found: locize.com/blog/who-uses-i18…

i18next AND inlang. Not either/or. npx i18next-cli init --inlang Sherlock, Fink & Paraglide now work on your existing i18next JSON. Nothing migrates. 7 interop bugs found, 7 fixed within hours, together with @samuelstroschei 🤝 locize.com/blog/inlang-inter…

10 years of Locize 🎂 Around this time in 2016, locize.com launched as a small backend for i18next. It still does that today. Just quite a bit more. Same workflow. Same Swiss-made platform. Same co-founders. Ten more years to go. 🔗 locize.com/blog/10-years-of-…

Moving a Remix app to React Router v7? remix-i18next (by @sergiodxa) targets RR v7 framework mode. New walkthrough covers the middleware-based locale detection, SSR-bundled translations, client-side CDN lazy-load, saveMissing, and the in-context editor. locize.com/blog/react-router…

12 minutes. The entire Locize product, end-to-end. We don't do sales calls — so this is exactly what we'd show you on one. 📺 piped.video/lCuHSZvSiVg📄 locize.com/blog/what-is-loci…

i18next in Production: Managing Translations at Scale This post covers the practical problems that appear when managing translations at scale, and the i18next ecosystem patterns that solve them. locize.com/blog/i18next-in-p…

next-intl vs next-i18next: Choosing the Right i18n Library for Next.js This post compares them on the things that matter for a real project: how translations are loaded, how they integrate with your stack, and what workflows they enable. locize.com/blog/next-intl-vs…