I've just tried to get it to run on Windows XP SP3. (I have a VM for an old Canon all-in-one printer.) I grabbed a legacy Tcl 8.6.6 installer from https://github.com/dbohdan/tcl86-nsis-installer (mine) and a 2017 build of curl with certificates from https://winampplugins.co.uk/curl/. The harness was developed against curl 8 and didn't work with 7.53.1. MiMo-V2.6-Flash, running in the same harness on modern Linux with Wine for `curl.exe`, found that the necessary change was minimal and only touched `--write-out`:
Use the proxy from old agent, it doesn't care. It'll bridge http to https and even read modern webapps and convert them to markdown (via lightpanda). It has free web search (via keenable) as well with no API key. 1000 requests/day per ip
The updates from http://legacyupdate.net makes Windows XP TLS 1.2-functional. And IronTCL worked for a Gopher/Gemini client I've got from elsewhere (https://luxferre.top). It's called BFG, you can peek its source and find that everything works in the spot. No issues to connect to any Gemini server where TLS it's mandatory.
I have some bundled BFG+IronTCL where it packs IronTCL, TCLlib and Tklib.
The authors should take the parent comment as a sign their manifesto's title is bad. Some will read the title and make a snap judgement that the manifesto must be totally against AI.
IceWM is a good DE for xrdp servers (https://en.wikipedia.org/wiki/Xrdp). This makes it my main window manager on a workstation I access through Remote Desktop. On my old ThinkPad, I had to migrate off IceWM because Xorg on Debian 13 no longer provided video acceleration. I have switched to Wayland and KDE.
With IceWM, you need to take care of the SSH agent that KDE or Cinnamon would start for you. You can do it with something like this in your `.xinitrc`:
As I said, the computer is a workstation. The xrdp server is a server in the same sense as sshd. I access the workstation remotely from my laptop, iPad, Android phone, etc. I picked Remote Desktop over, say, X2Go because it had the best iPad client some years ago (Microsoft's own).
> It was found that many publications that use Unicode Braille characters use U+2800 with a marking glyph. A
marking space is not without precedent, consider U+1680 OGHAM SPACE MARK. However, in some cases,
U+2800 is clearly used as a symbol, to indicate the presence of a space when describing a Braille sequence
corresponding to a symbol or punctuation, similar to the use of ␣ (U+2423 OPEN BOX) to indicate the
presence of a space. Especially in cases where it is used in a trailing position, as in the [UNE13] example, it is
clear that it would be inappropriate for this symbol to disappear.
> Considering this usage as a marking symbol, together with concerns about changing the relatively stable—and
often hardcoded—White_Space property (a property of only 25 code points, last changed in Unicode 6.3, when
U+180E MONGOLIAN VOWEL SEPARATOR ceased to be a space), the PAG preferred a more targeted
change.
but still unreasonable. In the presence of issues for each of the two options, you pick the correct one unless you have rather strong reasons, which they don't:
> U+2800 is clearly used as a symbol, to indicate the presence of a space when describing a Braille sequence corresponding to a symbol or punctuation, similar to the use of ␣
Why is that? Have you perhaps forgotten to add "␣" equivalent for Braille? So maybe do that instead so people can us a mark to mark something?
> Especially in cases where it is used in a trailing position, as in the [UNE13] example, it is
clear that it would be inappropriate for this symbol to disappear
Nothing disappears in the cited example, the line is very short , how is it possible to reject a fix when you can't even find an example of that fix breaking someone?
> last changed in
and this approach is why we can't have nice things and generations of computer users continue to suffer due to some dumb oversight decades ago. And it's not like we get a payoff of great stability, not, that standard is uber complicated and changes all the time
Thanks. No, I haven't played Sword Quest. The comments on the blog point out how it resembles Dragon Quest and Ultima IV for the NES, while Mark Hughes' page for the original Python 2.1 Umbra (https://mdhughes.tech/software/umbra/) says it's influenced by dungeon crawlers and console RPGs. I think that's the clearest visual connection. If Sword Quest uses drawing primitives to create its enemy graphics in vector, that's another.
Good reminder to play Aerofoil. I starred the repository a while ago and forgot about it. By chance, I never played that much Glider PRO, which I know is the more popular game with more houses.
I liked the Flash version of Glider PRO made by Mark Arenz in 2006, which the developer put on GitHub a few years ago (without source): https://github.com/markarenz/rid-flash-archive. Worth a try to see how close it got as a 2000s Flash game. Wikipedia used to say this:
> In 2006, Mark Arenz teamed up with Calhoun to construct a version of Glider PRO built in Adobe Flash.[citation needed]
I took the same path with my for-fun/learning GUI coding agent in Tcl/Tk: https://wiki.tcl-lang.org/page/Featherweight. It shells out to curl for the networking.
I've just tried to get it to run on Windows XP SP3. (I have a VM for an old Canon all-in-one printer.) I grabbed a legacy Tcl 8.6.6 installer from https://github.com/dbohdan/tcl86-nsis-installer (mine) and a 2017 build of curl with certificates from https://winampplugins.co.uk/curl/. The harness was developed against curl 8 and didn't work with 7.53.1. MiMo-V2.6-Flash, running in the same harness on modern Linux with Wine for `curl.exe`, found that the necessary change was minimal and only touched `--write-out`:
Here are two screenshots of the result. Featherweight is running in Tcl 8.6.6 on Windows XP.https://paste.dbohdan.com/1ng3b5y-kb4yd/greenshot-1.png https://paste.dbohdan.com/1ng3b5y-kb4yd/greenshot-2.png
reply