19:46:16 <sjorge> Hi everyone, from on a plane :O the latency is insane.
19:59:07 <richlowe> sjorge: is it at least the same in both directions?
19:59:24 <richlowe> remembering the joys of australians with satellite/dialup pairs, and also EFnet when things desynched
20:09:30 <sjorge> Yeah the latency seems consistant 
20:10:07 <sjorge> 64 bytes from <snip>: icmp_seq=4 ttl=64 time=922.545 ms
20:10:58 <sjorge> SSH works, ZNC works fine,... discord, mattermost, ... do not like this at all
20:13:51 <jbk> that's not that surprising
20:19:19 <richlowe> the greatest sin of all of these is not admitting when they're (probably) out of date
20:19:30 <richlowe> every IRC client in the world had the lag indicator
20:20:09 <jbk> a fun one i encountered a few months ago was teams for some reason decided to not send messages, but only in one specific channel
20:20:45 <sjorge> My guess is anything that was around during dialup days works fine-ish
20:22:07 <richlowe> sjorge: right and I accept the internet is way better now -- unless you're on a plane, a farm, lower wacker, ...
20:22:18 <jbk> this is probably where I start shouting at clouds, but trying to shove anything and everything through http[s] probably is also less than optimal from a functionality perspective
20:24:05 <sjorge> Oh yeah modern internet bandwidth allows for so much nice stuff, although sometimes less is probably better imho.
20:24:31 <sjorge> no reason teams client should need around 4-5G of memory on a bad day and around 2 on a good one.
20:24:48 <gitomat> [illumos-gate] 16273 getaddrinfo(3XNET) does not correctly handle an unspecified socket type -- Marcel Telka <marcel⊙ts>
23:06:53 <richlowe> does anyone know of a database of character set info that can be searched?
23:07:05 <richlowe> i give a bit string, i get a character that it might represent
23:10:14 <richlowe> everything I know of is statistical, and I don't have enough weird characters for that