valorin.bsky.social
Friendly Hacker, Speaker, and PHP & Laravel Security Specialist.🕵️
I write securinglaravel.com and hack stuff on stage for fun. 😈
I'm found elsewhere too: https://pinkary.com/@valorin 🪄
711 posts
2,163 followers
480 following
Regular Contributor
Active Commenter
comment in response to
post
comment in response to
post
That would make for a rather eventful workshop. 🤣
comment in response to
post
I'm tempted to use it for my workshop tomorrow (it's so easy to deploy stuff!), but I'm not sure a group of newbie-hackers trying to hack into my app is really the usage you're looking for a few days after launch. 🤣
comment in response to
post
Hopefully not so intimidating... 🤞 I'm there to help them every step of the way.
comment in response to
post
Thanks! It took me a while to find, but as soon as I saw it, I knew.
(Also, his part is just incredible in season 2.)
comment in response to
post
Colour is indeed the correct spelling.
I go out of my way to use colour everywhere that doesn't require color (i.e. CSS directives), and took way too much joy in doing that when working for an US company. 😈
comment in response to
post
Did they teach you two forms of English? That'd be super weird.
comment in response to
post
Oh interesting, thanks!
That said, I don't like [] being just "brackets", as that's definitely a generic term that covers any of them in my view. And I can't spell parentheses. 🤣
comment in response to
post
Oops, forgot about the curly brackets! Your naming fits with what I'm used to.
comment in response to
post
I call those square-brackets.
And <> are angle brackets (or less-than / greater-than).
It may just be me having a terrible memory and remembering a simpler name for something where there is a more exact name.
comment in response to
post
Probably?
I call ( ) brackets, but maybe that's confusing?
comment in response to
post
😁
comment in response to
post
I'll be diving into this in my next Security Tip over at https://securinglaravel.com, sign up so you don't miss it. This is a *really* fun one. 😈
comment in response to
post
There used to be some of those in dev, but haven't heard mention of them in a while. Twitter's API being absurdly expensive probably limits the options htere.
comment in response to
post
From what I can tell, there are a few reasons:
Some folks are just "comfortable", some just don't have the headspace to for another site, while others are there because the official Laravel announcements, etc, are there.
Until Laravel leadership moves over, they'll stay there too.
comment in response to
post
I will forever blame you for this.
comment in response to
post
How is it February ALREADY???!!!
comment in response to
post
I know a lot of folks don't bother answering the phone for numbers they don't recognise any more. Add on the fact that Android (and iOS?) actually alerts for potential scam calls now. Probably getting a lot less effective.
comment in response to
post
It's interesting they've shifted to "Call this number", but it makes sense given the targets aren't good with computers.
comment in response to
post
I know!
It's definitely a creative way to do it.
comment in response to
post
We don't have a family cow... 🙃
comment in response to
post
I think that focuses specifically on plain requests. safe() is the equivalent in FormRequests, right?