Live data from Hacker News

Httpx closing down issues and discussions due to "skewed gender representation"

github.com

1–10 of 15 posts

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#7
> I've closed off access to issues and discussions.

> I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value.

That's the totality of the message.

Weirdly enough, the concept of "an environment I don't personally find welcoming is unwelcoming — and better gone" strikes me as rather unwelcoming and indicative of a diet in severe need of iron-y supplementation.

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#9
post #6

I personally treat it as a supply chain risk, as there are no longer any way to report any bugs and security problems.

How is _your_ supply chain a concern of this open source developer?

_My_ supply chain is not a big deal, lol. But this is HTTPX. A network library that has a considerable number of users.

When I say _considerable_, I'm essentially saying _nearly every_ big tech. The one I can tell for sure is OpenAI (not a fan of them though).

Remember xz attack?

Re: Httpx closing down issues and discussions due to "skewed gender representation"

#10
post #5

I personally treat it as a supply chain risk, as there are no longer any way to report any bugs and security problems.

Then why not provide one yourself?

Forking is a good option for companies, but not a good option for sole developers: one doesn't have that much energy.

Switching to other libraries like requests and aiohttp and supporting them by contributing is clearly a better option.

Post reply on HN