Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Giacomo Tesio
@giacomo@snac.tesio.it  ·  activity timestamp 3 days ago
@daniel@gultsch.social

#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.

In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.

So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.

I wouldn't call these as "improvements".

These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.

@lorenzo@snac.bobadin.icu
  • Copy link
  • Flag this post
  • Block
Andrew Gallagher
@andrewg@mastodon.ie replied  ·  activity timestamp 3 days ago

@daniel oh, 100% he was thinking of PGP. 😂

  • Copy link
  • Flag this comment
  • Block
Giacomo Tesio
@giacomo@snac.tesio.it replied  ·  activity timestamp 3 days ago
@daniel@gultsch.social

#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.

In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.

So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.

I wouldn't call these as "improvements".

These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.

@lorenzo@snac.bobadin.icu
  • Copy link
  • Flag this comment
  • Block
chrysn
@chrysn@chaos.social replied  ·  activity timestamp 3 days ago

@giacomo @daniel @lorenzo IETF protocol specs regularly include sections with privacy considerations just like security considerations. These point out such problems and guide implementers to get them right (eg. to only use 0RTT if user tracking is of no concern because cookies would be on anyway). If a browser implements that wrong, it's for other lacks but awareness.

  • Copy link
  • Flag this comment
  • Block
Electrostep
@electrostep@mammut.gogreenit.net replied  ·  activity timestamp 3 days ago

@giacomo @daniel @lorenzo

@bagder , you've written a book on the subject. It's the above claim of about #QUIC (and #HTTP3) true?

  • Copy link
  • Flag this comment
  • Block
Issa
@Issa@fosstodon.org replied  ·  activity timestamp 3 days ago

@daniel who is moxie? moxie marlinspike ?

also, any agenda for crypotgraphy sujbects?

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login