owsei

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!

games, specifically far cry 2, 3 & 4 and overwatch. And punk shows, getting beaten up in a mosh while very drunk is truly refreshing/entertaining

I imagined a red dodgeball on a small brown table. The person was just a thick stick figure and when the ball fell it bounced.

The color and shape I didn't actively choose, they cam be different, but I guess my brain has defaults.

The ball falling and bouncing, however, I had to actively think about, the same way I have to think about texture. I don't have to think about where the ball would stop, or how much it would bounce tho.

How else would you open a program?

It's a great threat

also it's food

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.

A day before I got in a guy set fire to the trash in the chapel. So I befriended him immediately!

Thank you very much!