I say we take off and nuke the entire site from orbit.
It's the only way to be sure.
The technologically stubborn Unix sysadmin hiding in the office at the end of the corridor managing the servers which run xkcd.network. Builds computer networks, patches software and breaks both (though not necessarily in that order).
User of #Debian, #OpenBSD, and the skarnet.org stack.
Profile pic by @kalium.
| Location | /usr/sbin/multiplexd |
| Pronouns | They/them |
| Website | https://1.0.168.192.in-addr.xyz |
| Website6 | https://1000.0000.0000.0000.0000.0000.0000.0000.ip6.site |
I say we take off and nuke the entire site from orbit.
It's the only way to be sure.
Okay, so there's a annoyingly complicated API, for which there are both PCRE and Posix ERE implementations.
There's a simple API, but it's a compatibility layer on top of the Posix ERE implementation.
I want a simple API which works with PCRE's...
This has become a *little* more complicated than I was expecting.
It's at the point where the options I'm giving myself are TLS-ify everything and deal with the certificate mess or keep the tunnels and run OSPF.
Hmm, maybe I should be using some sort of thread-safe queue and doing all the I/O in one thread, instead of trying to manage it between two threads.
That's probably not a bad idea. Cue more code deletion.