06:05:19 <jfauhn> Hello I am just checking to see how things are going. I am monero curious and wanted to see how I can help.
12:41:05 <m-relay> <w​kaleign:matrix.org> Get in touch with this platform for greatness you’ll definitely thank me later
ℹ️❤️
👇🏻👇🏻👇🏻
12:41:06 <m-relay> (removed)
12:42:02 <m-relay> <w​kaleign:matrix.org> Get in touch with this platform for greatness you’ll definitely thank me later
ℹ️❤️
👇🏻👇🏻👇🏻
12:42:04 <m-relay> (removed)
14:36:29 <m-relay> <v​tnerd:monero.social> jpk68: no errors for socks are reserved
14:37:22 <m-relay> <v​tnerd:monero.social> You extend boost error code by creating a category with a unique static memory address. Every `int` is then available
14:41:04 <m-relay> <v​tnerd:monero.social> Arguably 0 is always implicitly reserved for no error otherwise the typical conversion to bool doesnt work correctly
14:41:23 <m-relay> <v​tnerd:monero.social> Otherwise every other value is valid
14:45:48 <m-relay> <v​tnerd:monero.social> In socks, some error integers are defined by the spec. These Integers map to a value in the special socks category. Then the implementation has other possible errors and those use different integer values in the same category.
14:47:54 <m-relay> <v​tnerd:monero.social> A few of the common errors returned by a socks server have an explicit name but I also didn't list all 256 valid error values
14:48:15 <m-relay> <v​tnerd:monero.social> Most of them are unused iirc
15:31:36 <m-relay> <j​pk68:matrix.org> Thanks, that was genuinely super helpful :))