
Lead Full-stack engineer @WeWorkJP. Organizer @LaravelliveJP & @phptokyo 👉 Laravel Live Japan: https://xitter.cf/t.co/vWQ5zWfJMx 👉 Discord: https://xitter.cf/t.co/z9uEaYrDtr
Tokyo, Japan
Joined January 2022
- Tweets3.1K
- Following632
- Followers687
- Likes81.8K
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
"The php2shell scare pulled PHP onto front pages worldwide, from Japan's prime minister to the NSA, and showed how much of the internet quietly runs on it." @mattstauffer
phpnews.net/php2shell-php-re…
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
php vulnerabilities: time to clarify what really happened
here's my conversation with @derickr, a member of php internals. we go through the full timeline and the facts
watch here: youtu.be/5X5csEbmHqs?si=uAk7…
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
See also the information advisory on PHP website by the PHP security team: php.net/archive/2026.php#202…
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
The PHP security team is advising everyone to set this config until the next patch:
session.upload_progress.enabled=0
I’ll be cutting a release shortly where serversideup/php will do this for you by default ⚡️
php.net/archive/2026.php#202…
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
PHP security team: keep session.upload_progress.enabled=0 until the next bugfix release. It blocks a rare RCE path, CVE-2026-115560.
PHP Warns of Another Session Upload Progress RCE Path
phpnews.net/php-session-uplo…
Gotta keep an eye on this for when Linux support drops, but I will soon play with it on my MacBook:
phibrowser.com/
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
So here is what I am going to do:
1. Begrudgingly give Dia a fair chance
2. Advance in creating my own browser
3. Stick to Chrome/Zen until I am satisfied with my own browser
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
The /dev/null mobile app (completely open source btw) is coming along
Sent my first picture through it earlier. DMs work too
This is worse than what I was expecting them to do with it after being taken over by Atlassian...
We've decided to sunset Arc on December 22, 2026.
That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community.
Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward.
We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how:
· Your passwords, bookmarks, extensions and history come over to Dia seamlessly.
· Spaces, Folders, and Tab Groups are in Dia and import over with your data intact.
· Dia now surpasses Arc benchmarks in stability, speed, and security.
· The browser features you use in Arc are free in Dia, and the AI is optional.
Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.
David Ciulla 🇯🇵🇨🇭| Laravel Live Japan retweeted
#DailyResource
News by Stephen Rees-Carter
Laravel Security Notice: Critical PHP Security Release
Read now at
bestoflaravel.com/go/5491
#php #laravel #webdev #javascript #tech #resources #developers
Patched PHP runtimes are live on Vapor.
Our guidance has changed, and we now recommend redeploying your apps.
◆ Native runtime on PHP 8.2+: redeploy
◆ Docker runtime: run a new deployment, not a redeploy
PHP 8.0 and 8.1 won't get a patch. Upgrade to 8.2+ now.
Native runtimes are updated on Laravel Vapor.
We are still working on an auto redeploy for Vapor and recommend redeploying yourself to get you on the patched secure PHP version quickly.
All images are available including 8.3, 8.4 and 8.5. If you are not on a native runtime, you will need a new deployment, not a redeploy.


















