Please wait...
[#]
Thu Oct 22 2020 14:01:51 EDT
from
IGnatius T Foobar
Subject: Re: Text client on macOS systems displays high ASCII that are not visable to non-macoS users
I remember the conversation but I don't think I was able to reproduce the
problem. Have you found a way to force the problem to appear on a Linux system?
Or, can you provide a dump of what's hitting your terminal in canonical hex+ASCII format?
Or, can you provide a dump of what's hitting your terminal in canonical hex+ASCII format?
I think at some point in the future I'm going to rewrite the text client,
maybe even switch it over to use the REST API that is being built as part
of webcit-ng. If I did it in Python I could probably hack one together in
a weekend. Could be fun. Maybe even build it in a way where your <G>oto
loop takes you through multiple servers instead of one. That would be cool.
2020-11-09 23:18 from IGnatius T Foobar
I think at some point in the future I'm going to rewrite the text
client, maybe even switch it over to use the REST API that is being
built as part of webcit-ng. If I did it in Python I could probably
hack one together in a weekend. Could be fun. Maybe even build it in
a way where your <G>oto loop takes you through multiple servers instead
of one. That would be cool.
I don't like how that sounds. I understand it would force you to install a webcit instance in order to be able to use the text client.
I prefer it the other way around myself: for the text client to be core functionality, and the web stuff an addon.
Sat Mar 27 2021 11:07:24 AM EDT from darknetuser2020-11-09 23:18 from IGnatius T Foobar
I think at some point in the future I'm going to rewrite the text
client, maybe even switch it over to use the REST API that is being
built as part of webcit-ng. If I did it in Python I could probably
hack one together in a weekend. Could be fun. Maybe even build it in
a way where your <G>oto loop takes you through multiple servers instead
of one. That would be cool.
I don't like how that sounds. I understand it would force you to install a webcit instance in order to be able to use the text client.
I prefer it the other way around myself: for the text client to be core functionality, and the web stuff an addon.
Strongly seconded. As few dependencies as possible for text.
Could you add petscii (commodore) to the text served by citadel over telnet? I know the petscii character encoding is well defined and documented. I just don't know how to make citadel do it.
The idea of connecting a future text client through a REST API instead of
through Citadel Server's native protocol is just an idea; I have no current
plans to do it that way. Actually there are no current plans to do much of
anything with the text client at the moment because there's so much else that
needs to get done first.
It will always be my favorite, though. Did you know that Citadel will celebrate its 40th birthday this December? Pretty good for a piece of software whose original author abandoned it after a couple of months.
It will always be my favorite, though. Did you know that Citadel will celebrate its 40th birthday this December? Pretty good for a piece of software whose original author abandoned it after a couple of months.
Could you add petscii (commodore) to the text served by citadel over
telnet? I know the petscii character encoding is well defined and
documented. I just don't know how to make citadel do it.
Hmm. That's an unusual ask. I used a Commodore 64 as my primary computer in the mid 1980s, so I know quite a bit about how PETSCII is laid out. What I don't know is how one would map it on a modern display. There seem to be Unicode equivalents to most of the special characters.
What is the use case you are trying to solve for?