You mean does the 80s-based protocol that doesn’t even support encryption support voice?
It doesn’t support having messages received while you were offline
IRC supports one and one thing only: N-wise chats to connected clients. That and delusional nerds who like to think they’re better than everyone else. Huge support for that too.
People who actually have sane standards for their instant messaging use the Matrix decentralized chat protocol when they need non-proprietary coms, or revolt
You can find it in action on regex101 with the regex indeed matching the query string in the maliciouswebsite and not matching even just something with the port and no user/password
It is valid (just weird & not recommended) to give a user:pw combo to a website that doesn’t ask for one in the headers. Browsers stripping it off is a different thing
The sheer number of things you have to take into account to properly parse a URL should convince you to not use regexes for it
The fact that it’s less code, more correct, faster and more readable to use new URL() should also be enough to convince you to not use regexes
Lmao ah yes, one of those
If you’re not convinced with this you never will
You can just wrap your var with “new URL()” and have something faster, correct and easier to read, but I’m guessing you’ll change your ways silently in a few years when you’ve forgotten about this interaction and managed to convince yourself it was your own idea!
Until then i guess you can add /c/whatev at the end of my two examples and find something else to criticize and decide not to support
Oh man I was hoping you’d ask because URLs are way worse than people imagine and that’s still not even a tenth of what emails can do
HtTpS://user:pw@lemdro.id:443 is a valid url to lemdro.id and should match but will not
Http://maliciouswebsite.to/?q=http://lemdro.id will match but should not
To give you an idea of how bad this is I suggest anyone tell me if their lemmy app parsed those properly because Thunder treats the 1st one as an email and Jerboa thinks both are URLs
You also have the instances that have a valid address with www in front of them for old school internet habits, there’s urls that can have quotes in them, urls with chinese characters or russian characters that are both valid in their encoding but have a canonical form in ASCII
It’s a mess, and the correct way to do this is still faster than your regex in the end which is crazy
Hard sell. Calling people you know nothing about “bad developers” because they don’t like your tool on the other hand, that was cringe as hell and just made you look like you somehow tied your self-worth to php. “If my tool gets criticized; that means I’m being criticized!”
If you don’t give in to that, you start to see “Oh, that bug wouldn’t have happened if I’d been using [x]” and you become a better developer
When a woodworker cuts iself with a bandsaw, people who do what you do scream “He’s a bad woodworker!”
And while they’re screaming, we invented guardrails
It ““worked”” in France
It still kills most of the userbase when they do it
Normal people don’t know what a fucking dns is
You end up with 10 more new sites and a drop in quality and an endless game of cat & mouse