You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plan for the near future is to have support for SOCKS5, so the ideal is to use socks instead of socks4 on the library names and public modules, and have specific internal modules for each version of the protocol. Currently, mirage_socks4 and lwt_socks4_unix are not following this convention and socks itself ended up being too verbose to use.
The text was updated successfully, but these errors were encountered:
The plan for the near future is to have support for SOCKS5, so the ideal is to use socks instead of socks4 on the library names and public modules, and have specific internal modules for each version of the protocol. Currently,
mirage_socks4
andlwt_socks4_unix
are not following this convention andsocks
itself ended up being too verbose to use.The text was updated successfully, but these errors were encountered: