Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Behind every great computer sits a skinny little geek.


computers / alt.bbs.synchronet / Re: More Questions

SubjectAuthor
o Re: More Questionsthe doctor

1
Re: More Questions

<624D9F4E.46690.sync@vert.synchro.net>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=15923&group=alt.bbs.synchronet#15923

 copy link   Newsgroups: alt.bbs.synchronet
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx98.iad.POSTED!not-for-mail
From: the.doc...@QBBS.remove-1u1-this (the doctor)
Subject: Re: More Questions
Message-ID: <624D9F4E.46690.sync@vert.synchro.net>
X-Comment-To: TRACKER1
Newsgroups: alt.bbs.synchronet
X-FTN-PID: Synchronet 3.19c-Linux master/b5cce30f9 Mar 28 2022 GCC 8.3.0
X-FTN-MSGID: 46690.sync@1:103/705 26b38bb0
X-FTN-CHRS: ASCII 1
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-Gateway: vert.synchro.net [Synchronet 3.19c-Win32 NewsLink 1.113]
Lines: 39
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Wed, 06 Apr 2022 14:10:25 UTC
Date: Wed, 6 Apr 2022 14:59:00 +0000
X-Received-Bytes: 2345
X-Original-Bytes: 2294
 by: the doctor - Wed, 6 Apr 2022 14:59 UTC

To: TRACKER1
>--- TRACKER1 wrote ---
> On 2/24/22 08:44, the doctor wrote:
> I can't speak for how Synchronet is handling this...
>
> I have been looking into this as well, planning on cataloging the
> information into a couple services as well. My plan was to look for
> "json-begin" and "json-end" in the message and plucking what's in
> between.
>
> Per the JSON spec, it *should* be UTF8 encoded, and any white-space
> characters outside quoted strings should be ignored. Since you can
> escape any character outside the 7-bit ASCII range (as well as quotes)
> per JS encoding (\x## \u#### \###), I suggest doing so for any
> interchange messages that include higher characters (and control chars),
> and (re)encoding any non-utf8 character sets to their Unicode
> corresponding values.
>
> As to message bodies, I think that terminal based message conventions is
> the combination of CRLF (\r\n), since \r will move the cursor to the
> beginning of the line and \n will move the cursor down one line. (IIRC)
>
> That's just my own opinionated take on this one, and what I've been
> doing so far.

Thanks for the information. I will trying doing what you suggest for
unicode characters. I've more or less got it working now, it was really
a problem caused by the more dusty bits of code (that i wrote like 15 or
more years ago) and me not remember what I did or why. (:

---
"No matter where you go, there you are..."

---
* TARDIS BBS - Home of QUARKware * telnet bbs.cortex-media.info
--- Synchronet 3.19c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

1
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor