TCP is the way that you send information, HTTP is what it means.

The difference, in your case, is the port. You can’t CAN have TCP and UDP on the same port, but you can’t have the same protocol on the same port.

edit: I didn’t knew you could have different transfer protocols on the same port, ty!

Punk rock for kids who can’t skate, by destructo disk

and The power of positive drinking, by ashtrays

Tbh you can play 0h h1 on your phone. A simple level takes 30 some seconds

Do you have feet and a camera?

HOUSE OF LEEEEEEAAAVEEESSSS

It’s more goose than duck, but I like it. It’s also pretty fat :)

“Unless it’s renders the product completely unusable unprofitable, why spend money and fix it?”

tbh I bought far cry 4, but because it was at a heavy discount and Ij ended up paying less than (the USD equivalent of) 4 dollars

I know him so well in my ass.

LMAO

Jokes on you! I love my spicy potatos!

And the orb pondering! Although, that wasn’t as big as this

That’s a great post, sad it didn’t get known

this and the three days without shitting post

(In portuguese, because that’s what I write most often) Mulheres são paulo em uma vez por um grande número

Women are São Paulo at once for a large number. I hope that’s not misogynistic

I’d say 128 is understandable, but something like 256 or higher should be the limit. 64, however, is already bellow my default in bitwarden

Damm, I legit didn’t knew there bcrypt had a length limit! Thank you for another reason not to use bcrypt

Also rate of the requests. A normal user isn’t sending a 1 MiB password every second

Why are you hasing in the browser?

Also, what hashing algorithm would break with large input?

The problem is that you (hopefully) hash the passwords, so they all end up with the same length.

Oh, I already hated windows, that was just the last straw