Forking `socks` as `crypton-socks`

Announcements
1

I am on the verge of forking socks as crypton-socks (EDIT: now done). Kazu Yamamoto has kindly agreed to be a co-maintainer. As many people will know, Kazu stepped up to maintain the crypton* (and other) packages after cryptonite* became unmaintained. socks is not a cryptographic package but the crypton-* prefix is intended to signal that it is part of a family of maintained equivalents.

The sole maintainer of socks is Vincent Hanquez who, for his reasons published elsewhere, does not wish to further develop his packages or introduce new maintainers.

crypton-socks-0.6.1 will be a carbon copy of socks-0.6.1. crypton-socks-0.6.2 (soon; EDIT now released) will then bring things up to date. My medium term plan includes to eliminate a (one function) dependency on unmaintained basement (EDIT: implemented in 0.6.2).

EDIT: crypton-socks-0.6.2 is included in Stackage snapshot nightly-2025-07-12.

10 Likes
2

The ecosystem really got fucked over by Vincent’s decision, didn’t it? Not putting the blame fully on him (the issue is multifaceted), it’s just extremely unfortunate that this has caused so many ongoing issues and so much time got wasted (and still will).

4 Likes