Tim ☮️ (@TimVanDijck) header
Tim ☮️ (@TimVanDijck) profile picture

Building Mailcoach @spatie_be 💻 | Loves cycling 🚴‍♂️ and racing 🏎 | Amateur pitmaster 🍖 | Dinonerd 🦕

Brecht, Belgium
Joined April 2009
Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)Photo by Tim ☮️ (@TimVanDijck)
What will you download first?
80%GTA VI
20%PHP 8.6
5 votes • 4 hours
50
Now it's getting colder outside, think about those who don't have a home.
🤖 Made with AI
1
50
We’re working hard on a new editor experience for Mailcoach, and we’re adding some fun little QoL features along the way. Like this drag-to-remove action!
65
We are slowly noticing an increase in open rates for Microsoft products, but we are still far from pre-outage levels.
We are also seeing the effects of the Outlook outage in the open rates on Mailcoach 👀
2
158
We are also seeing the effects of the Outlook outage in the open rates on Mailcoach 👀
2
2
1
1
1,301
Why compare open rates and not bounces? A lack of bounce notifications doesn’t necessarily mean everything is working. A mail server accepting your message and someone being able to access their inbox are separate things.
38
The next interesting part is recovery. Do tracked opens return to normal when Microsoft reports everything is working again, or does the effect linger? A before/during/after comparison should be interesting...
128
I never really understood peoples obsession with Japan, but now I have been there... I really miss it, and I want to go back.
3
107
The people who made this happen deserve a special place in hell.
59
One thing is not yet fully clear: are the PHP patches still being worked on, or are we waiting for some symbolic release time?
3
2
3,933
While in the old days, waiting for a set release time might have made sense, we can assume bad actors have already reverse engineered the vulnerability and are ready to exploit it. Hiding the fix until everybody is ready to update might not be the best option in the age of AI.
1
251
Tim ☮️ retweeted
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.
39
273
40
1,314
177,405
Our office playlist right now...
3
127
The Grafana MCP is such a superpower to help you manage a large production app. It makes it so easy to ask your agent operational questions.
4
258
😭
One day you typed make:migration for the last time and you didn’t even know
2
116
Tim ☮️ retweeted
Email infrastructure is HARD. A lot is because spammers abuse these infrastructures so companies have to build tools to fight them, create guardrails, buy ips, pay for expensive tools, go to conferences where they decide governance The problem is not sending 5K emails. The problem is sending emails at scale and on behalf of people. P.S. I used to send billions of emails every year. I found out more about email than I wish to my enemies
Bye bye Beehiiv 👋 I vibe-coded my own newsletter platform: 📧 Campaign management w/ editor 🖥️ Web archives (newsletter.marclou.com) 🔗 API support 🫧 List cleanup, deliverability reports It took a few prompts with Opus 5.5. I left Beehiiv because they raised prices for the 3rd time in 2 years. - My first yearly bill was $1,000. - My future bill would have been $4,000. Now I'm using AWS SES + MongoDB, and I will pay less than $300/year. Newsletter platforms charge per subscriber, when in fact the real cost is the number of emails sent. Subscribers will naturally become inactive, so you end up paying more for something that hurts your deliverability (sending to dormant subscribers = spam trap). So I've set a cleanup cron job for my newsletter alternative. It marks inactive subs as dormant, sends one last re-engaging email, and stops emailing them. Money saved. Deliverability increased. I also gain a priceless feature: Freedom. I can change the UI, add features, connect all my apps - anything is possible with just a prompt. I'm replacing Resend next. I love it, but it's very expensive ($400/mo)
26
3
3
99
22,067
Zero regrets adding this skill!
Power user tip, add this to your AGENTS.md to get better output:
1
73
Power user tip, add this to your AGENTS.md to get better output:
1
141