JCpac

joined 2 years ago
[–] JCpac@lemmy.today 3 points 2 weeks ago

With enough quantum tunneling, anything is possible!

[–] JCpac@lemmy.today 3 points 2 weeks ago

"Blows up blender with mind"

[–] JCpac@lemmy.today 8 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I personally finished "Inside" in one sitting without planning to.

Phrasing...

[–] JCpac@lemmy.today 23 points 3 weeks ago

I want to argue with this, but it makes too much sense

[–] JCpac@lemmy.today 3 points 1 month ago

I am hilarious and you will quote everything I say

[–] JCpac@lemmy.today 6 points 1 month ago

I see eye of newt, but where, prithee, is your...

sQuIrT oF lEmOn? 🍋‍🟩🤏

[–] JCpac@lemmy.today 111 points 2 months ago (5 children)

No, it's Javascript, keep up

[–] JCpac@lemmy.today 15 points 2 years ago

CSS is decorating a christmas tree off to the side. Some of the decorations are hovering in the air. We don't correct CSS, as it seems to be having fun regardless.

[–] JCpac@lemmy.today 1 points 2 years ago (1 children)

Is it because of the "Host" HTTP header? I always thought it was optional, since the IP address and port were handled by the network and transport layers respectively. Turns out it's required to resolve between different virtual hosts in the same server. Today I Remembered (TIR?) that virtual hosts are a thing...

Is there anything else that might indicate the domain name in the handshake connection?

[–] JCpac@lemmy.today 9 points 2 years ago (11 children)

I don't get it... How does this protect anything? If we want our packets to reach a web server, we need to write the server's IP address on them. If a snooper has the IP, can't they just lookup the domain name from a DNS server? Or is that not a service DNS provides?

If the IP address is encrypted, how will the routers know where to send the packets? Only solution I can think of would be onion routing... Am I wrong??

[–] JCpac@lemmy.today 12 points 2 years ago

If you're having fun after 1600 hours, then you're not playing it wrong

view more: next ›