Greetings my friends,

I don’t often send out emails outside the usual weekly schedule

, but I wanted to reach out and let you know what’s going on at Laravel Security In Depth, or should I say: what’s going on at Securing Laravel. 😁

That’s right, I’ve changed the name!

As much as I loved Laravel Security In Depth as a name, including the unintentional double-meaning

, I’ve been wanting to move from a subdomain at Substack for a while to a full domain. A few months ago I was talking to the naming maestro Taylor Otwell, and he suggested securinglaravel.com - which sounded perfect. Since then I’ve been planning the move, and yesterday I finally did it! 🎉

Essentially this is just a naming refactor. The weekly security tips and monthly In Depth articles will remain the same, likewise so will subscriptions, and the other Substack tools. The subdomain will redirect to the new domain, so it should be pretty seamless - but let me know if you find anything broken!

So I’ve been planning the change it for a while, but why now?

As you’re probably aware, the Laravel community mainly hangs out on Twitter, so that’s where I focus the majority of my promotion and community interactions. However, the recent algorithm changes at Twitter have significantly reduced my reach, and more importantly, Twitter is now pseudo-blocking links at *.substack.com

. At this stage, the pseudo-blocking seems to be a domain match, and since I was going to switch to a custom domain anyway, it was the additional push I needed to do it!

If you’re interested in the process of switching to a custom domain, I Tweeted and Tooted

about the entire process. It was relatively painless, although a bit tedious at points…

So that’s basically it. New name, new domain, and a shiny new logo. 😎

Since you’ve made it this far, I have a favour to ask: I would love it if you could share Securing Laravel with your Laravel friends! You’re all here because you recognise learning about security is important, and it is my goal to share that with the rest of the Laravel community, so I would love you to tell your friends about Securing Laravel and get more people learning about security and writing secure apps.

Share Securing Laravel

For the free subscribers: I would really appreciate it if you considered upgrading to a paid subscription. Paid subscriptions directly fund my time each week as I research and write my weekly emails. I don’t have any sponsors or advertisers, so the more subscribers, the more time I get to spend teaching and focusing on security within the Laravel community.

To celebrate the rename, for the next 3 days you can upgrade to a paid subscription and get 25% off!

Get 25% off forever

Regardless of if you upgrade to a paid subscription or stay a free subscriber, thank you so much for being a subscriber and supporting Securing Laravel. 🥰 Your support means a lot to me, and I would not be able to do what I love without it. Thank you.

Ok, this email is long enough. Bye folks!
Stephen

P.s. As always, if you have any thoughts on the change, or suggestions for how to improve Securing Laravel, please don’t hesitate to reach out to me. Either via email, stephen@rees-carter.net, or on Twitter or Mastodon.