うなすけとあれこれ

Translated by AI (and reviewed by me) from handwritten Japanese text. (日本語が後に続きます)

May’s progress

As mentioned in the April monthly report, I’ve been developing with significant AI assistance. While I didn’t push any changes in April, I recently committed my local modifications.

Although I haven’t completed full interop testing with quic-interop-runner, I have passed interop tests with both quic-go and quiche, reaching a stage where QUIC and HTTP/3 communication is now possible. I’ve also prepared sample scripts under /examples. We can already establish connections with several known HTTP/3 endpoints, including cloudflare-quic.com. I need to set aside dedicated time to thoroughly review the entire codebase at some point. Now, regarding the Pure Ruby QUIC implementation discussed above - in practical use cases, no one would deliberately choose to use a potentially slower implementation when there are established, proven solutions available. Both in terms of interoperability and security, relying on such established implementations is superior.

With this in mind, I’ve also created a binding implementation for ngtcp2 and been advancing the development process (with AI assistance). Since I was able to acquire the exact namespace I wanted¹, I feel a significant responsibility to build on this foundation. I’ll continue enhancing the implementation’s quality to serve as a viable option for those looking to perform QUIC communication in Ruby.

• https://github.com/unasuke/quic-ruby
• https://rubygems.org/gems/quic

This initiative began when I received encouragement from kazuho at RubyKaigi 2026 (or at least that’s how I interpreted it?).

protocol-quic, yet another QUIC implementation for Ruby

By the way, Mr. Samuel Williams as known as ioquatix is also working on making QUIC and HTTP/3 available from Ruby. He focuses on enriching the asynchronous I/O ecosystem and has released several projects under https://github.com/socketry, including falcon and protocol-http2.

Inside these repositories, you’ll find https://github.com/socketry/protocol-quic, a gem that uses ngtcp2 as its backend also. After encountering build issues in my environment during RubyKaigi 2026’s post-event gathering at SmartHR, I consulted with them about these problems, and through various circumstances, I was added to the Maintainers Team for the Socketry organization.

Just a few days later, https://github.com/socketry/protocol-http3—which uses nghttp3 as its backend—was also released. Around this time, I collaborated with them at a coffee shop just before RubyKaigi 2026’s post-event gathering at Pixiv, and we successfully incorporated some patches into the project.

Neat, it works. pic.twitter.com/gdY9eoAIGh

— Samuel Williams (@ioquatix) May 25, 2026

I was able to discuss various things with Samuel regarding future Socketry-related projects, so I’ll be actively working on them to the best of my ability.