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

Looks like "?logonlist -l" reports 'same day' calls in ascending order, while the next day (or previous days) are in a descending order. Would like for it all to be in one order, or even configurable with an option "?logonlist -l -a" for ascending, or "?logonlist -l -d" for descending? See below for screenshot.

https://pharcyde.org/logonlist.png
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Nick Boel wrote to GitLab issue in main/sbbs <=-

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

Looks like "?logonlist -l" reports 'same day' calls in ascending
order, while the next day (or previous days) are in a descending
order. Would like for it all to be in one order, or even
configurable with an option "?logonlist -l -a" for ascending, or "?logonlist -l -d" for descending? See below for screenshot.

https://pharcyde.org/logonlist.png

This looks correct/normal to me. The first sort is by date, and then
it's sorted by the time of connection on that date, top to bottom.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Gamgee,

On Sun, Jun 09 2024 13:17:00 -0500, you wrote:

https://pharcyde.org/logonlist.png

This looks correct/normal to me. The first sort is by date, and then
it's sorted by the time of connection on that date, top to bottom.

As we discussed on IRC, If the date were to go in the same order as the time of connections on the same day, the newest calls would be at the bottom of the list. Currently, they are not sorted in order, *by call*. The "total connections" column on the left side of the screenshot will show you that they are not in order.

Would just like to see it possibly configurable for ascending, decending, or leave it how it is, is all.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- slrn/pre1.0.4-9 (Linux)
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Re: "logonlist.js -l" reports last callers out of order
By: Nicholas Boel to Gamgee on Sun Jun 09 2024 09:15 am

Would just like to see it possibly
configurable for ascending, decendin

Plus one on this. The last login list
is a little weird with date going
newest to oldest but logins on that
date going oldest to newest. Or is it
vice versa? Whichever, I would
definitely prefer to see the list of
callers in simple order so you can just
quickly glance at it rather than trying
to match up numbers and such.

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/761#note_5368

I'm not seeing this. In all cases, for me, logonlist.js is returning the logons in the same order they are listed in the `data/logon.*jsonl` file (the same order in which they are added to the file, during logon).

Maybe you're looking at the `data/logon.lst` file instead?
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: "logonlist.js -l" reports last callers out of order
By: Nicholas Boel to Gamgee on Sun Jun 09 2024 09:15 am

Hello Gamgee,

On Sun, Jun 09 2024 13:17:00 -0500, you wrote:

https://pharcyde.org/logonlist.png

This looks correct/normal to me. The first sort is by date, and then it's sorted by the time of connection on that date, top to bottom.

As we discussed on IRC, If the date were to go in the same order as the time of connections on the same day, the newest calls would be at the bottom of the list. Currently, they are not sorted in order, *by call*. The "total connections" column on the left side of the screenshot will show you that they are not in order.

Would just like to see it possibly configurable for ascending, decending, or leave it how it is, is all.

As it is now, logonlist.js and the underlying libraries (json_lines.js, logonlist_lib.js) don't "sort" the entries at all - they are always displayed "how it is", in the order the entries are in the file, which is the same order in which they are added to the file during logon (by default, in logon.js).
--
digital man (rob)

Synchronet "Real Fact" #46:
Synchronet External X/Y/ZMODEM protocol driver (SEXYZ) was introduced in 2005 Norco, CA WX: 76.1øF, 58.0% humidity, 14 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: "logonlist.js -l" reports last
By: phigan to Nicholas Boel on Sun Jun 09 2024 01:00 pm

Re: "logonlist.js -l" reports last callers out of order
By: Nicholas Boel to Gamgee on Sun Jun 09 2024 09:15 am

Would just like to see it possibly configurable for ascending, decendin

Plus one on this. The last login list is a little weird with date going newest to oldest but logins on that date going oldest to newest. Or is it vice versa? Whichever, I would definitely prefer to see the list of callers in simple order so you can just quickly glance at it rather than trying to match up numbers and such.

I'm not sure what you're describing. The data/logon*.json file contains logon information in the order of the recorded logons (newest at the end) and this is the same order in which the entries are displayed by logonlist.js.
--
digital man (rob)

Steven Wright quote #8:
If you want the rainbow, you got to put up with the rain.
Norco, CA WX: 76.0øF, 59.0% humidity, 6 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/761#note_5369

I'm definitely not using data/logon.lst whatsoever (however, that seems to display the last 7 callers in order). I'm using this to display the last callers:

// Last few callers
console.aborted=false;
console.clear(LIGHTGRAY);
if(options.show_logon_list === true)
bbs.exec("?logonlist -l");
if(bbs.node_status != NODE_QUIET && ((system.settings&SYS_SYSSTAT) || !user.is_sysop))
bbs.mods.logonlist_lib.add();

.. that is all.

Maybe this is because you're only looking at the last 4-5 callers? I've been listing 10, and it doesn't look like data/logon.jsonl is even showing that many, so maybe that's why.

That said, currently I have 5 calls from today, and they are listed in the order as they are in data/logon.jsonl, 34279-34283. Then, the 6th most recent caller is listed as 34275 from yesterday, and then the 7th caller is 34265, from 6/4/24 (which looks like it's listed in logon.0.jsonl, and the 8th caller is 34266, also from 6/4/24 (which looks like it's listed in logon.1.jsonl.

So that's probably where the problem lies, when it backtracks into older files.

So I guess I would say try loading a longer list of last callers and you'll see what I mean.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/761#note_5370

Okay, yeah, I see now: when pulling from previous days to form the last few callers list, they're not in order.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/761
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Digital,

On Sun, Jun 09 2024 22:56:26 -0500, you wrote:

Would just like to see it possibly configurable for ascending, decending, or
leave it how it is, is all.

As it is now, logonlist.js and the underlying libraries (json_lines.js, logonlist_lib.js) don't "sort" the entries at all - they are always displayed "how it is", in the order the entries are in the file, which
is the same order in which they are added to the file during logon (by default, in logon.js).

In that case, is there a setting somewhere to log 10 entries in logon.jsonl so they show up in order? It seems it's only logging 5, and then going back to older files, ie: logon.0.jsonl, logon.1.jsonl, etc. which is what seems to be putting them out of order (since it seems as though every list is ascending).

Regards,
Nick

... Take my advice, I don't use it anyway.
--- slrn/pre1.0.4-9 (Linux)
# Origin: _thePharcyde distribution system (Wisconsin) (723:1/1)
ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Digital,

On Sun, Jun 09 2024 22:58:02 -0500, you wrote:

I'm not sure what you're describing. The data/logon*.json file contains logon information in the order of the recorded logons (newest at the
end) and this is the same order in which the entries are displayed by logonlist.js.

Looks like when it runs out of entries in the main .jsonl file, it goes to the older ones, which are also in ascending order. This makes an actual flowed list out of order.

The default only displays 5 entries, so you're not seeing what I am. I display 10 last callers. I guess an easy fix would be if you could log the last 10 (or more) callers in logon.jsonl, before it rotates to another file.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- slrn/pre1.0.4-9 (Linux)
# Origin: _thePharcyde distribution system (Wisconsin) (723:1/1)
ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: "logonlist.js -l" reports last
By: Digital Man to phigan on Sun Jun 09 2024 03:58 pm

logon information in the order of th
recorded logons (newest at the end)

Newest at the end per day, right? But
then the next day goes above those?
Or am I just seeing it wrong?

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: "logonlist.js -l" reports last
By: phigan to Digital Man on Mon Jun 10 2024 07:01 pm

Re: "logonlist.js -l" reports last
By: Digital Man to phigan on Sun Jun 09 2024 03:58 pm

logon information in the order of th recorded logons (newest at the end)

Newest at the end per day, right? But then the next day goes above those?
Or am I just seeing it wrong?

That was bug with the '-l' option only, as it pulled from more than one day to fulfill the request - that's now fixed.
--
digital man (rob)

Breaking Bad quote #25:
Now if I could only learn how to lick myself. - Hank Schrader
Norco, CA WX: 61.5øF, 85.0% humidity, 3 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: "logonlist.js -l" reports last
By: Digital Man to phigan on Mon Jun 10 2024 10:40 pm

That was bug with the '-l' option only, as it pulled from more than one day fulfill the request - that's now fixed.

I'll finally upgrade one of these days :)

---
þ Synchronet þ TIRED of waiting 2 hours for a taco? GO TO TACOPRONTO.bbs.io
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)