Kasumi Hanazuki

I'm pretty disappointed that one of the Ruby committers ignored a community member begging for a discussion, saying "I don't get the point," and forced a license change against the...

So ruby-core devs want to keep this repo under the Ruby+BSD-2-Clause dual license. I agree to put my patches under it. Whether we call this a "clarifying" or "relicensing" process,...

Blocklisting using `/etc/hosts` aims to inhibit resolving a certain set of domain names system-wide. As Resolv is an alternative to system resolver, I think it is against the purpose of...

To discuss performance we'd be happy to have some numbers. What is the environment? How poor is the current performance? How is it improved with this patch? A reproducible benchmark...

It looks quite faster than "forever" :) Self-contained benchmark: ```ruby require 'benchmark/ips' require 'resolv' require 'tempfile' hosts = { small: 20, medium: 2000, large: 200000, }.transform_values do |size| f =...

> PS! `0.0.0.0` entries are only useful for browsers etc. which connect to a plethora of unwanted servers.`resolv` is part of `HTTPX` used for dev projects with full control over...

Freezing `ClassHash` on load looks problematic if the user extends the library by defining a custom Resource class and registers it in `ClassHash` after requiring resolv. How about defining a...

> Customizing a resolver should require initializing a new instance with the custom class mapping, i.e. the library should not be defining ´ClassHash` as a de-facto lazy cache. Agreed. DNS...

I have examined the logic but don't know if this works with TCP fallback. I'm thinking of a situation as follows: - The Resolv::DNS instance is configured with two nameservers...

> To make this work properly, maybe we have to reset the requester before `next`. > > ```ruby > when RCode::ServFail > if Requester::TCP === requester > requester.close > requester...