Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
dochtman
on Feb 5, 2019
|
parent
|
context
|
favorite
| on:
HTTP/3 explained
QUIC is developed by an IETF working group where anyone can participate, and there are definitely some productive participants who don't work for Google (or any of the other big companies).
takeda
on Feb 5, 2019
|
next
[–]
Like they listened to varnish author about making actually useful changes? For example implementing proper sessions, so cookies could go away.
dagenix
on Feb 5, 2019
|
parent
|
next
[–]
Just because they didn't agree with his suggestion to make major changes to the protocol semantics didn't mean they didn't listen to him.
JoshTriplett
on Feb 6, 2019
|
parent
|
prev
|
next
[–]
TLS Token Binding provides exactly that.
takeda
on Feb 6, 2019
|
root
|
parent
|
next
[–]
Yeah, and who is using it? Why cookies are still there?
anticensor
on Feb 6, 2019
|
root
|
parent
|
next
[–]
Cookies can do more than sessions.
takeda
on Feb 10, 2019
|
root
|
parent
|
next
[–]
Sure they can, but sessions are pretty much the only reason why end users have cookies enabled.
zzzcpan
on Feb 5, 2019
|
prev
[–]
That's not really true. Independent participants don't have any power to affect any of it.
Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
