Language:
switch to room list switch to menu My folders
Go to page: First ... 19 20 21 22 [23]
[#] 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

[Reply] [ReplyQuoted] [Headers] [Print]

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?

[#] Mon Nov 09 2020 23:18:24 EST from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

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.

[#] Fri Mar 26 2021 17:44:15 EDT from ASCII Express

[Reply] [ReplyQuoted] [Headers] [Print]

I just wanted to say that I use a screen reader for the blind, and love the text client.

[#] Sat Mar 27 2021 11:07:24 EDT from darknetuser

[Reply] [ReplyQuoted] [Headers] [Print]

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.

[#] Sun Mar 28 2021 09:08:27 EDT from nonservator

[Reply] [ReplyQuoted] [Headers] [Print]

 

Sat Mar 27 2021 11:07:24 AM EDT from darknetuser
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.

 

Strongly seconded. As few dependencies as possible for text.



[#] Wed Mar 31 2021 18:22:25 EDT from smashbot64

[Reply] [ReplyQuoted] [Headers] [Print]

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.

 



[#] Sat Apr 03 2021 11:02:29 EDT from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

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.

[#] Sat Apr 03 2021 11:09:11 EDT from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

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?

Go to page: First ... 19 20 21 22 [23]