00:19 <tumbleweed> :P

06:47 <mgorny> xD

06:47 <mgorny> don't worry, i'll just backport them to Gentoo, and call ourselves safer than official releases ;-)

09:06 <cfbolz> I have certainly never seen this before?!: i86 = int_add_ovf(i70, ?)

10:31 <arigato> random off-topic notes of me being annoyed at the internet: for our app we need at least some kind of TCP-like connection between various client devices and one server we control. how hard can it be? it's a complete mess

10:33 <arigato> the client devices are used in random places; e.g. one android device seems to drop secure-websocket connections after 1s but only if it is connected via a specific phone

10:34 <arigato> using plain sockets or plain websockets tend not to work, requiring the secure version in the first place, which is a nightmare every few months when the certificates update

10:35 <arigato> because for some reason we get certificates that sometimes Unity programs on some clients are not happy with

10:39 <arigato> at this point I'm looking for a library that solves this mess by including try-various-things, retry-if-connection-drops, and I don't care about security (it's easy to add my own on top, no need for certificates in this case, because all devices are connecting to a preexisting, preconfigured server)

11:13 <LarstiQ> I assume those devices are using their system certificates?

11:13 <arigato> I think so, yes

11:18 <arigato> I suppose it's too much to ask for a library that exists for Python and C#, and that is maintained to continue working with whatever new restrictions will show up next month in the name of security

11:19 <arigato> e.g. some android devices think nowadays that it's a good idea to prevent http connections completely

11:20 <arigato> or plain sockets

11:20 <arigato> I think

11:21 <arigato> (but plain sockets have other issues with half of the proxies around)

11:31 <LarstiQ> with Python requests iirc you can add certificates to the trust store so you don't need to depend on the system being kept up to date, I would assume C# has similar (Java does at least)

11:32 <arigato> ah

11:37 <arigato> and I guess there is no such thing as an API "please open this https using this certificate", there is only APIs that modify the local user's "store" which is some file somewhere?

11:46 <LarstiQ> I do think "using this certificate" is in essence what it does, no need to mutate what the user has

11:48 <arigato> ah, ``r = requests.post(url, data=data, verify='/path/to/public_key.pem')``

11:49 <LarstiQ> https://requests.readthedocs.io/en/latest/user/advanced/#ssl-cert-verification

11:49 <LarstiQ> arigato: right

11:51 <arigato> we need working certificates anyway for the web page, but non-browsers seem more prone to complaining about them, so it may help, thanks

11:53 <arigato> (doesn't change the fact that if it works, I would prefer it to be done by a library as I said above, because next month there will be a different issue)

11:54 <arigato> (also, doesn't help in all cases, of course, like people behind some proxies)

11:58 <LarstiQ> arigato: https://magic-wormhole.readthedocs.io/en/latest/index.html seems to be pretty good in NAT/proxy breakthrough iirc

12:06 <arigato> magic-wormhole is great, but it starts with a websocket connection to a well-known server, and that's already the part that we have trouble with

12:16 <LarstiQ> I'm currently out of ideas

12:29 <arigato> thanks so far :-)

12:34 <arigato> (and ah, I think I found the equivalent to "verify=" for C# websockets)