Live data from Hacker News

Viewing profile — simmervigor

simmervigor

HN member
Joined
Mon, Mar 21, 2022, 10:50 AM UTC
HN karma
123
Public activity
20 items

About simmervigor

No profile information was provided.

Recent public activity

  1. story
  2. story
  3. story
  4. comment
    Comment #44992945

    > If anyone from Cloudflare happens to be reading this, you should know that you have some kind of misconfiguration Thanks for the detailed information. I'm a someone from Cloudfla…

  5. comment
    Comment #43430474

    We certainly like it at Cloudflare. Look out for more blogs from the team related to the topics.

  6. comment
    Comment #43421560

    Very nice work. From a qlog and MASQUE enthusiast

  7. story
  8. story
  9. comment
    Comment #31718496

    tools.ietf.org hosted a range of tools or links to resources. That is what i mean by service, which has been in the process of migration to other subdomains of ietf.org

  10. comment
    Comment #31718487

    From the page: > The IETF Datatracker is the day-to-day front-end to the IETF database for people who work on IETF standards. It contains data about the documents, working groups, …

  11. comment
    Comment #31715378

    Odd this appeared on the front page. The service is deprecated and the tools will soon have been entirely migrated under https://datatracker.ietf.org

  12. comment
    Comment #31649556

    Yes it was, there was a pretty lengthy discussion dating back to 2017 on the issue tracker https://github.com/quicwg/base-drafts/issues/253 TL;DR just like HTTP/2, we wanted to avo…

  13. comment
    Comment #31648947

    103 Early Hints is RFC 8297. It defines a status code. Because status codes are an HTTP semantic, they are common across all HTTP/1.1, HTTP/2, and HTTP/3. There's nothing special t…

  14. comment
    Comment #31648921

    For what it's worth, the HTTP/2 specification contains almost identical phrasing as HTTP/3 [1]. That's not unexpected, the considerations are similar: using a single connection wit…

  15. comment
    Comment #31648786

    Co-chair of the QUIC WG here. Early in the process, we decided it was important that HTTP/3 provide parity with HTTP/2. That helps application developers to migrate back and forth …

  16. comment
    Comment #31635981

    You could build this as an application mapping over QUIC. Within a single QUIC connection use reliable streams for the metadata delivery, and unreliable datagrams [1] for the paylo…

  17. comment
    Comment #31635578

    > If I were the Internet Dictator, I'd be a big fan of standardizing the semantics of http separate from the physical transport and then defining best practices for using alternati…

  18. comment
    Comment #31631220

    Some related discussion in this Twitter thread: https://twitter.com/alagoutte/status/1532013841718120449?t=W...

  19. comment
    Comment #30760137

    Proxy components are officially called Intermediaries in thr HTTP semantic specification; see https://httpwg.org/http-core/draft-ietf-httpbis-semantics-la... . Intermediaries can h…

  20. comment
    Comment #30760083

    The vanilla CONNECT method is an instruction to open a TCP connection to the target server. What is sent over that is entirely up to client and target the server it doesn't need to…