open https://gitlab.synchro.net/main/sbbs/-/issues/449

Would be nice if the Directories/Files in each directory was listed in newline delimited JSON [1]. Each line is a record, where non-printable characters, newlines etc are escaped, which is the default for many JSON stringifiers. This would make it easier to programatically mirror content between BBSes.Suggested structure...```ts{ type: string; // "group" or "dir" or "file" - maybe just "dir" and "file" since group doesn't mean much here path: string; // full ftp path and file/dirname - /main/sbbs/sbbs316c.zip name: string; // name only part - sbbs316c.zip sdesc: string; // short description - cp437 converted to utf8 desc: string; // long description - cp437 converted to utf8 size: number; // bytes uploadBy: string; // Username uploadOn: string; // ISO-8601 encode date-time of upload "2015-01-01T12:45:00Z"}```1. http://ndjson.org/
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/449#note_2785

I'm very familiar with JSONL (see exec/load/json_lines.js).This is an interesting idea and would be pretty trivial to implement, however I don't know of any *consumer* of such meta data.If I were to implement this, I would prefer to use a schema that more closely resembles the Synchronet FileBase file-meta-object: https://synchro.net/docs/jsobjs.html#FileBase_class_methods
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/449#note_2786

That structure would be fine w/ me... was only thinking of including details for directories as well as files... but even if only for "dirs" listing just files, would be beneficial.
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)