home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 48167 
 deon to Deuce 
 src/tith/standards/TSP-0001.txt 
 28 Nov 25 13:47:17 
 
TZUTC: 1100
MSGID: 15669.dove-syncprog@12:1/2 2d8e806a
REPLY: 53578.syncprog@1:103/705 2d8e02ce
PID: Synchronet 3.21a-Linux master/b7d3db6c3 Sep 28 2025 GCC 10.2.1
TID: SBBSecho 3.32-Linux master/ec8f7009f Nov 15 2025 GCC 12.2.0
COLS: 80
BBSID: ALTERANT
CHRS: CP437 2
FORMAT: flowed
NOTE: FSEditor.js v1.105
  Re: src/tith/standards/TSP-0001.txt
  By: Deuce to deon on Thu Nov 27 2025 07:18 am

Howdy,

 >  > IE: If you are querying for  _tith_sysopname, why put sysop= in the
 >  > response? Couldnt the response just be the answer "Deuce"?

 > Because that's what the RFC said to do... it's supposed to be thing=other
 > thing.

Is this RFC 1464 that you speak of?

It makes sense when the attribute=value is a "subset" of the think you are
querying, but you are using it twice which seems duplicative(?) to me.

IE: if the query was alterant.bbs.dege.au, it would seem logical to have
sysop=deon, and os=linux and bbs=synchronet, etc, but if I was to query
_sysop_alterant.bbs.dege.au, I would have thought it to be a better answer to
just say "deon", since sysop is the attribute I want to get the answer to.

RFC8552 I think is written with this approach in mind. Anyway, no biggie, just
providing feedback in case it might be useful.


...лоеп

---
 ю Synchronet ю AnsiTEX bringing back videotex but with ANSI
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 13/0 102/401 103/705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 700 810 226/30
SEEN-BY: 227/114 229/110 206 317 400 426 428 470 700 705 266/512 280/464
SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280
SEEN-BY: 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426


<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca