home.social

#http3 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #http3, aggregated by home.social.

  1. Many changes! Shipping STABLE @nlnetlabs Unbound QUIC builds aside our non QUIC variant&our cutting-edge canary builds soon! The supported architectures have been ramped up too: ppc64le, s390x, riscv64 joined the party. No own unbound.conf anymore, now we're just patching the needed settings at buildtime.

    Test driving our builds verifies everything is nice. 💚

    github.com/madnuttah/unbound-d

  2. Many changes! Shipping STABLE @nlnetlabs Unbound QUIC builds aside our non QUIC variant&our cutting-edge canary builds soon! The supported architectures have been ramped up too: ppc64le, s390x, riscv64 joined the party. No own unbound.conf anymore, now we're just patching the needed #recursor settings at buildtime.

    Test driving our builds verifies everything is nice. 💚

    github.com/madnuttah/unbound-d

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy #Security #ci #cd

  3. Many changes! Shipping STABLE @nlnetlabs Unbound QUIC builds aside our non QUIC variant&our cutting-edge canary builds soon! The supported architectures have been ramped up too: ppc64le, s390x, riscv64 joined the party. No own unbound.conf anymore, now we're just patching the needed #recursor settings at buildtime.

    Test driving our builds verifies everything is nice. 💚

    github.com/madnuttah/unbound-d

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy #Security #ci #cd

  4. Many changes! Shipping STABLE @nlnetlabs Unbound QUIC builds aside our non QUIC variant&our cutting-edge canary builds soon! The supported architectures have been ramped up too: ppc64le, s390x, riscv64 joined the party. No own unbound.conf anymore, now we're just patching the needed #recursor settings at buildtime.

    Test driving our builds verifies everything is nice. 💚

    github.com/madnuttah/unbound-d

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy #Security #ci #cd

  5. Many changes! Shipping STABLE @nlnetlabs Unbound QUIC builds aside our non QUIC variant&our cutting-edge canary builds soon! The supported architectures have been ramped up too: ppc64le, s390x, riscv64 joined the party. No own unbound.conf anymore, now we're just patching the needed #recursor settings at buildtime.

    Test driving our builds verifies everything is nice. 💚

    github.com/madnuttah/unbound-d

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy #Security #ci #cd

  6. New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (github.com/madnuttah/openssl-b)

    Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

    cc @nlnetlabs 💚

    github.com/madnuttah/unbound-d

    hub.docker.com/r/madnuttah/unb

  7. New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (github.com/madnuttah/openssl-b)

    Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

    cc @nlnetlabs 💚

    github.com/madnuttah/unbound-d

    hub.docker.com/r/madnuttah/unb

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

  8. New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (github.com/madnuttah/openssl-b)

    Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

    cc @nlnetlabs 💚

    github.com/madnuttah/unbound-d

    hub.docker.com/r/madnuttah/unb

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

  9. New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (github.com/madnuttah/openssl-b)

    Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

    cc @nlnetlabs 💚

    github.com/madnuttah/unbound-d

    hub.docker.com/r/madnuttah/unb

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

  10. New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (github.com/madnuttah/openssl-b)

    Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!

    cc @nlnetlabs 💚

    github.com/madnuttah/unbound-d

    hub.docker.com/r/madnuttah/unb

    #DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy

  11. Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

    Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

    Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

    Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

    myhome.zone

  12. Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

    Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

    Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

    Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

    myhome.zone

  13. Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

    Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

    Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

    Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

    myhome.zone

  14. Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.

    Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.

    Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.

    Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.

    myhome.zone

  15. Lapor engkong @kongtol dan koh @semurjengkol ...

    #GoToSocial :gotosocial: sama #misskey :misskey: gua lewatin #caddy biar bisa access log nya seragam di #loki. Tadinya sih mau sekalian biar bisa #http3 dari cf ke origin, tapi ternyata #cloudflared cuma support http3 dari browser ke edge doang, bukan dari edge ke origin. Tapi lumayan lah bisa http2 dari edge ke origin.

    Caching juga dah gua atur di #cloudflare biar access media di #s3 full-caching.

  16. Lapor engkong @kongtol dan koh @semurjengkol ...

    #GoToSocial :gotosocial: sama #misskey :misskey: gua lewatin #caddy biar bisa access log nya seragam di #loki. Tadinya sih mau sekalian biar bisa #http3 dari cf ke origin, tapi ternyata #cloudflared cuma support http3 dari browser ke edge doang, bukan dari edge ke origin. Tapi lumayan lah bisa http2 dari edge ke origin.

    Caching juga dah gua atur di #cloudflare biar access media di #s3 full-caching.

  17. Lapor engkong @kongtol dan koh @semurjengkol ...

    #GoToSocial :gotosocial: sama #misskey :misskey: gua lewatin #caddy biar bisa access log nya seragam di #loki. Tadinya sih mau sekalian biar bisa #http3 dari cf ke origin, tapi ternyata #cloudflared cuma support http3 dari browser ke edge doang, bukan dari edge ke origin. Tapi lumayan lah bisa http2 dari edge ke origin.

    Caching juga dah gua atur di #cloudflare biar access media di #s3 full-caching.

  18. Lapor engkong @kongtol dan koh @semurjengkol ...

    #GoToSocial :gotosocial: sama #misskey :misskey: gua lewatin #caddy biar bisa access log nya seragam di #loki. Tadinya sih mau sekalian biar bisa #http3 dari cf ke origin, tapi ternyata #cloudflared cuma support http3 dari browser ke edge doang, bukan dari edge ke origin. Tapi lumayan lah bisa http2 dari edge ke origin.

    Caching juga dah gua atur di #cloudflare biar access media di #s3 full-caching.

  19. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  20. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  21. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  22. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  23. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  24. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  25. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  26. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  27. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  28. 🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
    kmcd.dev/posts/connectrpc-wher
    #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi

  29. Revision 709: HTTP/3 und WebTransport, mit Max Inden | Working Draft

    workingdraft.de/709/

    Das war ein echt schöner Überblick über QUIC, HTTP/3, DoH und ECH. Auch immer mit einem "warum" mit schwingend.

    Danke @mxinden 🙏

    #http3 #ECH #quic #internet

  30. Revision 709: HTTP/3 und WebTransport, mit Max Inden | Working Draft

    workingdraft.de/709/

    Das war ein echt schöner Überblick über QUIC, HTTP/3, DoH und ECH. Auch immer mit einem "warum" mit schwingend.

    Danke @mxinden 🙏

    #http3 #ECH #quic #internet

  31. Revision 709: HTTP/3 und WebTransport, mit Max Inden | Working Draft

    workingdraft.de/709/

    Das war ein echt schöner Überblick über QUIC, HTTP/3, DoH und ECH. Auch immer mit einem "warum" mit schwingend.

    Danke @mxinden 🙏

    #http3 #ECH #quic #internet

  32. Revision 709: HTTP/3 und WebTransport, mit Max Inden | Working Draft

    workingdraft.de/709/

    Das war ein echt schöner Überblick über QUIC, HTTP/3, DoH und ECH. Auch immer mit einem "warum" mit schwingend.

    Danke @mxinden 🙏

    #http3 #ECH #quic #internet

  33. Ein Paketverlust und plötzlich steht alles? HTTP/2 über TCP leidet an Head-of-Line-Blocking. Wanderson Xesquevixos erklärt, wie #HTTP/3/QUIC das löst & wie es in #Java26 aktiviert wird.

    So simpel ist der Einstieg! Jetzt lesen: javapro.io/de/java-26-uebernim

    #Java #HTTP3 #Performance

  34. Ein Paketverlust und plötzlich steht alles? HTTP/2 über TCP leidet an Head-of-Line-Blocking. Wanderson Xesquevixos erklärt, wie #HTTP/3/QUIC das löst & wie es in #Java26 aktiviert wird.

    So simpel ist der Einstieg! Jetzt lesen: javapro.io/de/java-26-uebernim

    #Java #HTTP3 #Performance

  35. qs aka quick-send - Tired of wrestling with overly complex file transfer tools? Solution, the hidden gem of A-to-B file transfers.

    While alternatives like croc and magic-wormhole often suffer from frustrating UX—requiring extensive manuals, relay configurations, slowness, custom scripts, and firewall tweaks—qs focuses on simplicity and actually works.

    Why qs stands out:

    • Zero installation: Ships as a single binary without unnecessary bloat.
    • Frictionless UX: No 50-page man pages or complex setup instructions; just run and transfer.
    • Reliability: Cuts out the hours of frustration and failed attempts common with over-engineered solutions.

    If you need a tool that simply does exactly what it is supposed to do, check out the project and its excellent feature comparison checklist here: https://github.com/maxomatic458/quic-send

    #filetransfer #datatransfer #magicwormhole #croc #quic #http3

  36. qs aka quick-send - Tired of wrestling with overly complex file transfer tools? Solution, the hidden gem of A-to-B file transfers.

    While alternatives like croc and magic-wormhole often suffer from frustrating UX—requiring extensive manuals, relay configurations, slowness, custom scripts, and firewall tweaks—qs focuses on simplicity and actually works.

    Why qs stands out:

    • Zero installation: Ships as a single binary without unnecessary bloat.
    • Frictionless UX: No 50-page man pages or complex setup instructions; just run and transfer.
    • Reliability: Cuts out the hours of frustration and failed attempts common with over-engineered solutions.

    If you need a tool that simply does exactly what it is supposed to do, check out the project and its excellent feature comparison checklist here: https://github.com/maxomatic458/quic-send

    #filetransfer #datatransfer #magicwormhole #croc #quic #http3

  37. qs aka quick-send - Tired of wrestling with overly complex file transfer tools? Solution, the hidden gem of A-to-B file transfers.

    While alternatives like croc and magic-wormhole often suffer from frustrating UX—requiring extensive manuals, relay configurations, slowness, custom scripts, and firewall tweaks—qs focuses on simplicity and actually works.

    Why qs stands out:

    • Zero installation: Ships as a single binary without unnecessary bloat.
    • Frictionless UX: No 50-page man pages or complex setup instructions; just run and transfer.
    • Reliability: Cuts out the hours of frustration and failed attempts common with over-engineered solutions.

    If you need a tool that simply does exactly what it is supposed to do, check out the project and its excellent feature comparison checklist here: https://github.com/maxomatic458/quic-send

    #filetransfer #datatransfer #magicwormhole #croc #quic #http3

  38. qs aka quick-send - Tired of wrestling with overly complex file transfer tools? Solution, the hidden gem of A-to-B file transfers.

    While alternatives like croc and magic-wormhole often suffer from frustrating UX—requiring extensive manuals, relay configurations, slowness, custom scripts, and firewall tweaks—qs focuses on simplicity and actually works.

    Why qs stands out:

    • Zero installation: Ships as a single binary without unnecessary bloat.
    • Frictionless UX: No 50-page man pages or complex setup instructions; just run and transfer.
    • Reliability: Cuts out the hours of frustration and failed attempts common with over-engineered solutions.

    If you need a tool that simply does exactly what it is supposed to do, check out the project and its excellent feature comparison checklist here: https://github.com/maxomatic458/quic-send

    #filetransfer #datatransfer #magicwormhole #croc #quic #http3