JdeBP

38 ms·

661.
by JdeBP 1y ago
U+12399 was not an assigned code point until Unicode 8. The other code points were in Unicode 7.
662.
by JdeBP 1y ago
Funnily enough, it was M. Stross who put me onto the fuss about the X11Libre's project's politics, and the GitHub issue over its README, just under a week ago. M. Stross had some rather strong words to say on the subject.
663.
by JdeBP 1y ago
The name that you might be reaching for unknowingly is Xenocara.
664.
by JdeBP 1y ago
That's almost correct. The order matters to an extent inasmuch as for the older paper terminals one had to delay after sending a CR in order to let the print head actually travel. So it wasn't LF+CR, but actually LF+CR+delay.
665.
by JdeBP 1y ago
It's slightly inconsistent. If sending the client's terminal type to the server is disallowed, it just hangs, and then times out. Reasonable behaviour, one might think, for a server that really needs to know that it can legitimat
666.
by JdeBP 1y ago
So yet another of many places where one just has to know that the RFC does not match the real world. An interesting test case for my state machine. But I can see the dragon in the proper colours, now.
667.
by JdeBP 1y ago
Your wife is possibly wondering why you send everything cleartext in one single frame and don't do challenge-response or any sort of state machine resynchronization between client and server. (-:
668.
by JdeBP 1y ago
Especially as it's impossible to tell whether jvanderbot's "people" datagram got dropped by some intermediate hop in the UDP version or was never sent. (-:
669.
by JdeBP 1y ago
This is what you get when you don't check for PIPELINING in the EHLO response like you are supposed to. (-:
670.
by JdeBP 1y ago
Oh that's annoying. They send LF then CR for newline on the wire, instead of CR then LF per RFC 5198.
671.
by JdeBP 1y ago
Amusingly, the original that I wanted to improve upon a quarter of a century ago still works. My improved version written in Java no longer does. * https://jdebp.uk/Softwares/text-movie-player.html
672.
by JdeBP 1y ago
It's related, certainly, as are mine, Charles Cazabon's, and Mark-Jason Dominus's. But it's not addressing what the headlined page is, which is largely a thing that is a behavioural issue on interactive real-time chat f
673.
by JdeBP 1y ago
QDOS even had non-blocking I/O at the individual read/write call level. I had to mention this when I learned of Daniel J. Bernstein advocating, almost 20 years after QDOS, non-blocking nonblock_read()/nonblock_write() additio
674.
by JdeBP 1y ago
And more evidence to add to the server-does-negotiated-SSL-but-client-is-doing-implicit-SSL pile is this: * https://marc.info/?l=opensmtpd-misc&m=141543622103232&w=2 Coincidentally, I was just talking about the mess
675.
by JdeBP 1y ago
I'll see your 7 and raise you 10. * https://github.com/OpenSMTPD/OpenSMTPD/issues/451
676.
by JdeBP 1y ago
Reading the flags one: Unscii has font coverage, if you want to try that out on the emulators whose fonts were problems. * https://news.ycombinator.com/item?id=43812026
677.
by JdeBP 1y ago
Xe means the Unicode block that is actually named "Symbols For Legacy Computing". It's not in the BMP. Some bloke named Bruce was doing TUI windows with scrollbars and sizer/menu boxes some years before TurboVision and
678.
by JdeBP 1y ago
Given that it's drawing TUI windows, the MouseText characters for doing that very thing on the Apple IIe would seem even more pertinent. * https://tty0.social/@JdeBP/114409020672330885
679.
by JdeBP 1y ago
Alas, it's not finished. You've made the mistakes that all of us have made, and haven't caught up with us, must of us having fixed those mistakes, a few years back when implementing 24-bit RGB was in vogue. This is not, as t
680.
by JdeBP 1y ago
It seems to have supported UTF-8 for at least a decade. Although it went the full-on ECMA-35 route of making that an optional switchable character set. There was an issue back in 2016 where, ironically, it was coming up in Latin-1 mode wit
681.
by JdeBP 1y ago
In hindsight, that does seem a little ridiculous; yet it was indeed the thinking. One could see where the exchanges were by simple dint of visiting a place. Soviet spies would just have had to walk around a bit. Of course, nuclear weapo
682.
by JdeBP 1y ago
I know someone who is still waiting for City Fibre, who dug up xyr road last year, to get around to actually offering a service.
683.
by JdeBP 1y ago
Back closer to the time, there were some people around who insisted that SSL specifically meant the old versions and it was all TLS now. I recall a couple of occasions where people were talking about UCSPI-SSL and someone stepped in to exp
684.
by JdeBP 1y ago
I might have an OS/2 programming manual. But I don't need it. (-: This was not an OS/2 thing. We had to make map data structures using thread IDs. Or our language runtimes did. Look to Windows NT rather than to OS/2
685.
by JdeBP 1y ago
You should have been watching lots of SciFi, too. (-: I have a Raspberry Pi in a translucent "modular case" from the PiHut. * https://thepihut.com/products/modular-raspberry-pi-4-case-cl... It is very clos
686.
by JdeBP 1y ago
Yes, it is; as I explained back in 2018. It's documented in the IA manuals, and indeed in the AMD manuals. The segment descriptors start off in unreal mode, which is changed at the first far jump that loads CS. TianoCore does a near
687.
by JdeBP 1y ago
Naming things is hard, Geoff. (-:
688.
The New Coventry Light Rail Is Here [Geoff Marshall, YouTube] [video](youtube.com)
2 points by JdeBP 1y ago|3 comments
689.
by JdeBP 1y ago
Not really. Asimov's story did not represent the process as a mathematically inevitable consequence of physics. It might not even have gone through a second cycle. Cellular life, dollars, and teletypes would all have had to come abo
690.
by JdeBP 1y ago
And the clickbait title isn't actually the conclusion, as the page cited by this one as its source even explains.

More ›