Super excited for @resend's new inboxes feature 👀
I was precisely waiting for something like that for a couple of projects so I can't wait to build on it.
Out of curiosity, is there any plan to support POP3/SMTP with them, or at least ability to redirect/set aliases with another regular e-mail? (cc @lauradotjs)
Mathieu Céraline retweeted
it’s 2026. build like you’re already going to get hacked, because sooner or later you probably will
collect less. only keep the customer data you actually need. anything you never store can’t leak
encrypt everything you keep. not just passwords and card numbers: names, emails, addresses, photos, uploads, all of it. if someone gets into your database or storage, they should find nothing they can read
delete what you don’t need anymore. old accounts, expired orders, stuff from years ago that nobody uses. set it up so it gets deleted automatically, not “someday"
don’t store tokens or api keys unless you really really really really have to. if you do, encrypt them hardcore or put them in a secrets manager. and either way, keep your encryption keys separate from the data they protect
basically: the less data you keep, the less you have to worry about when you get hacked
I don't personnally use Railway but today has felt to me like the equivalent of an atomic bomb explosion. And I feel like all of this is only just starting...
An urgent notice from the Railway team
blog.railway.com/p/security-…
Mathieu Céraline retweeted
Cloudflare has deployed default web application firewall (WAF) protections for newly disclosed PHP vulnerabilities before public disclosure. The rules use request and response signals to stop exploit attempts and prevent exposed data from reaching attackers. cfl.re/488w8dc
Mathieu Céraline retweeted
One-click mitigation for php2shell vulnerability:
If you have Cloudflare in front of your PHP website, please login to the dashboard and click this button to make sure you are protected.
dash.cloudflare.com/?to=/:ac…
This reduces your risk but doesn't fix the vulnerabilities in PHP. We recommend updating PHP to a patched version.
At 14:00 UTC two critical security vulnerabilities will be patched in PHP.
These are extremely serious vulnerabilities affecting every PHP application on the web.
Laravel Cloud customers: we will begin automatically patching your applications as soon as the patch is released. No manual action is required.
Laravel Forge customers: you will need to manually update your server’s PHP version via the server’s Forge dashboard. If you are unable to update your server, it should be powered down.
Laravel Vapor customers: we will begin automatically re-deploying applications running on PHP 8 as soon as the patch is released. No patch is being released for PHP 7 -- immediately update all applications to PHP 8.
Mathieu Céraline retweeted
The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.
PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.
Hey @pascalbaljet, hope you're doing fine!
Any idea what causes this? dev-null.sh/@mathcrln/commit…
(tagged you on dev-null, but putting it here in case anyone ever faced a similar issue)
Devs, how do you learn these days in this AI era?
Specifically what does learning look like for you, what do you learn and how do you prioritize it?
dev-null.sh/@mathcrln/commit…
Hey @ClaudeDevs I have been following the latest updates to Claude (Code), the arrival of projects, SSH connector in the app, the new chat groupings, etc. But somehow I cannot seem to find them anywhere. Am I missing something, like are these features being rolled out slowly or are there conditions I do not match?
cc @lydiahallie @bcherny
Mathieu Céraline retweeted
Your side projects should be compounding very fast with AI. Every problem solved can be re-used or extracted into a generic module. Every design decision should make the next thing beautiful by default. Your agents should be constantly stealing from your past decisions.
Mathieu Céraline retweeted
The @stateoflaravel results for 2026 are now available!
This year, there had been many AI questions to differentiate hype from reality. And the results are interesting...
Hype vs Reality👇
stateoflaravel.com/results
Been using ploi for the last two years and I'm super happy with it, 3 servers, handful of clients and internal projects 👌🏾
But lately after trying out Laravel Cloud I kind of want to try out @laravelforge 🥺 Anyone has tried both?
Published my very first NPM packages this week. I will talk a bit more about my experience later but… its not as scary as I thought it would be 😅
And its already very useful! I have encapsulated logic that I use for almost all of my clients that are on @astrodotbuild, notably for SEO and OG Image Generation.
Obviously, AI contributes to making it less scary.
They are still very early, not perfect yet. And they are mostly internal, optimized for our personal usecases inside @madincohq. But I still try to make them versatile enough to be used by anyone.
It’s also a wonderful experience in building APIs, trying to make things feel fluent and easy to use, hiding complexity and making things as delightful as possible at the call sites.
It seems like in the age of AI people no longer read code 😅
Funnily enough for me it's the opposite, I am obssessed with code quality and readability. I guess I have @laravel to thank for this bias, but I keep trying to find the right abstractions to make my code, my modules, my APIs, read more fluent.
I use it to learn. Now that I don't have to pay a toll for every keystroke, I can invest that time to find the right design and abstractions, to develop my own strong opinions that I can bring from project to project. The goal is to become extremely good and fast at discriminating good code from bad code.
I also use it to... make my life easier in the future. Clear and understandable patterns make it easier for me to debug/maintain by myself in the future but it also makes it easier for Claude/Codex to rinse and repeat, no need to reinvent a new wheel in every module.
Disclaimer: to go fast, I do occasionnally allow myself a bit of technical debt; code that I know is not optimal, but that I plan to fix later once I will find the right abstractions. But I try to be diligent about always paying that debt back.
It seems like in the age of AI people no longer read code 😅
Funnily enough for me it's the opposite, I am obssessed with code quality and readability. I guess I have @laravel to thank for this bias, but I keep trying to find the right abstractions to make my code, my modules, my APIs, read more fluent.
I use it to learn. Now that I don't have to pay a toll for every keystroke, I can invest that time to find the right design and abstractions, to develop my own strong opinions that I can bring from project to project. The goal is to become extremely good and fast at discriminating good code from bad code.
I also use it to... make my life easier in the future. Clear and understandable patterns make it easier for me to debug/maintain by myself in the future but it also makes it easier for Claude/Codex to rinse and repeat, no need to reinvent a new wheel in every module.
Disclaimer: to go fast, I do occasionnally allow myself a bit of technical debt; code that I know is not optimal, but that I plan to fix later once I will find the right abstractions. But I try to be diligent about always paying that debt back.














