From: alter.ego@ALTERANT.remove-3ho-this

To: Digital Man
Hey DM,

Another thing that I find a little unhelpful, which I'm wondering if you can change?

I often read messages just to me when I first login, or when I'm on and I get the telegram has posted a message to me.

At login, if I'm reading those messages to me, and I choose not to see subjects
(so I get to see the whole message) - I cannot use "*" to see the thread - since its only showing me new messages (and I'm guessing "*" would only show new messages that are
threads to whatever I'm reading?)

Sometimes when I read a message addressed to me, and I need more history to remember the context (and "*" shows me nothing), I then need to stop reading "new messages", find the echo, find the message to me (or eventually read new messages until I get to
it), then "*" will give me the full history.

Anyway to have "*" show the full thread history of messages, even though I'm just scanning "messages to me"?
...deon


... Monday is a hard way to spend one-seventh of your life.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: rampage@SESTAR.remove-ove-this

To: Alter Ego
Re: Changes to "*" (seeing message threads)
By: Alter Ego to Digital Man on Sat Feb 01 2020 16:24:24

At login, if I'm reading those messages to me, and I choose not to
see subjects (so I get to see the whole message) - I cannot use "*"
to see the thread - since its only showing me new messages (and I'm guessing "*" would only show new messages that are threads to
whatever I'm reading?)

i see the same but my flow is slightly different than yours...

i'll do the same read messages to me only thing... some i may answer then... others i'll delay answering until later... when i'm through all the ones only to me, then i'll use the 'N'ew messages option and read all messages... at this
point, i'll come
back across those that i already read to me... now i can use the '*' thread feature to

1) look back if needed
2) to remember if i already replied

the really fun stuff comes later when i get to read it all again on one of my other systems/devices ;)


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-z6y-this

To: Alter Ego
Re: Changes to "*" (seeing message threads)
By: Alter Ego to Digital Man on Sat Feb 01 2020 04:24 pm

Hey DM,

Another thing that I find a little unhelpful, which I'm wondering if you can change?

I often read messages just to me when I first login, or when I'm on and I get the telegram has posted a message to me.

At login, if I'm reading those messages to me, and I choose not to see subjects (so I get to see the whole message) - I cannot use "*" to see the thread - since its only showing me new messages (and I'm guessing "*" would only show new messages that are threads to whatever I'm reading?)

Sometimes when I read a message addressed to me, and I need more history to remember the context (and "*" shows me nothing), I then need to stop reading "new messages", find the echo, find the message to me (or eventually read new messages until I get to it), then "*" will give me the full history.

Anyway to have "*" show the full thread history of messages, even though I'm just scanning "messages to me"?

Unfortunately, no. The whole "thread view" thing is pretty broken anyway, especially when a thread exceeds the length of the terminal, so it might go away or be replaced in the future.

When you do a "your message scan", only messages to you are loaded into memory.
And having a sub-mode that loads all messages into memory (e.g. to display while in thread view mode) doesn't really work - there's just too many state variables that are
dependant on the messages that were originally loaded during the scan.

Anyway, I'll keep your request in mind for future over-hauls of that code.

digital man

Synchronet "Real Fact" #73:
SyncTERM (created by Deuce) contains portions of Synchronet and SEXYZ code. Norco, CA WX: 83.4øF, 19.0% humidity, 3 mph SW wind, 0.00 inches rain/24hrs
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: alter.ego@ALTERANT.remove-2sk-this

To: Digital Man
Re: Changes to "*" (seeing message threads)
By: Digital Man to Alter Ego on Sat Feb 01 2020 01:19 pm

When you do a "your message scan", only messages to you are loaded into memory. And having a sub-mode that loads all messages into memory (e.g. to display while in thread view mode) doesn't really work - there's just too many state variables that are dependant on the messages that were originally loaded during the scan.

Bummer, I thought that would be the answer.

Not understanding the internals, that "your message scan" of messages in memory
that are mine, cannot include the threads as well (that may not be mine?) ...deon


... Ambition is the curse of the political class.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-z9s-this

To: Alter Ego
Re: Changes to "*" (seeing message threads)
By: Alter Ego to Digital Man on Sun Feb 02 2020 10:52 am

Re: Changes to "*" (seeing message threads)
By: Digital Man to Alter Ego on Sat Feb 01 2020 01:19 pm

When you do a "your message scan", only messages to you are loaded into memory. And having a sub-mode that loads all messages into memory (e.g. to display while in thread view mode) doesn't really work - there's just too many state variables that are dependant on the messages that were originally loaded during the scan.

Bummer, I thought that would be the answer.

Not understanding the internals, that "your message scan" of messages in memory that are mine, cannot include the threads as well (that may not be mine?) ...deon

Right, in this context, "your messages" means messages posted *to* you. Messages posted *to* other users are not included. The thread view probably should just be disabled in that scan mode.

digital man

This Is Spinal Tap quote #42:
What day the Lord created Spinal Tap and couldn't he have rested on that day? Norco, CA WX: 82.1øF, 18.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs --- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: alter.ego@ALTERANT.remove-l92-this

To: Digital Man
Re: Changes to "*" (seeing message threads)
By: Digital Man to Alter Ego on Sat Feb 01 2020 04:51 pm

Right, in this context, "your messages" means messages posted *to* you. Messages posted *to* other users are not included. The thread view probably should just be disabled in that scan mode.

Yeah, I got that, but can be extended to include threads of messages to you? ...deon


... The truest wild beasts live in the most populous places.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-c96-this

To: Alter Ego
Re: Changes to "*" (seeing message threads)
By: Alter Ego to Digital Man on Sun Feb 02 2020 04:27 pm

Re: Changes to "*" (seeing message threads)
By: Digital Man to Alter Ego on Sat Feb 01 2020 04:51 pm

Right, in this context, "your messages" means messages posted *to* you. Messages posted *to* other users are not included. The thread view probably should just be disabled in that scan mode.

Yeah, I got that, but can be extended to include threads of messages to you?

I'm not clear what a "thread of messages to you" would include. Any thread that
has any message that was addressed to you would be considered a "thread of messages to you"? I don't think that's what people want to read when their searching for messages
to themselves.

digital man

Synchronet/BBS Terminology Definition #32:
FTS = FidoNet Technical Standard
Norco, CA WX: 71.3øF, 32.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: alter.ego@ALTERANT.remove-ypn-this

To: Digital Man
Re: Changes to "*" (seeing message threads)
By: Digital Man to Alter Ego on Sun Feb 02 2020 12:12 pm

I'm not clear what a "thread of messages to you" would include. Any thread that has any message that was addressed to you would be considered a "thread of messages to you"? I don't think that's what people want to read when their searching for messages to themselves.

So, if I'm searching for "new messages to me" - and it happened to pick messages 50 and 70.

If 50 was a thread of 48,49 and 51,52, then the new messages to me would show me "50", but pressing "*" would reveal 48,49,51,52.

So in memory, the list of new messages is not just 50 and 70, it is also including 48,49,51,52.

The logic would be:
* Find messages to user
* Find linked messages to list of mesages to user
* This list is the list of all messages captured by the function "new messages to user" - which ultimately is a subset of all messages right?
...deon


... Do what you will with this tagline, just don't bother me about it!

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-lyh-this

To: Alter Ego
Re: Changes to "*" (seeing message threads)
By: Alter Ego to Digital Man on Mon Feb 03 2020 07:50 am

Re: Changes to "*" (seeing message threads)
By: Digital Man to Alter Ego on Sun Feb 02 2020 12:12 pm

I'm not clear what a "thread of messages to you" would include. Any thread that has any message that was addressed to you would be considered a "thread of messages to you"? I don't think that's what people want to read when their searching for messages to themselves.

So, if I'm searching for "new messages to me" - and it happened to pick messages 50 and 70.

If 50 was a thread of 48,49 and 51,52, then the new messages to me would show me "50", but pressing "*" would reveal 48,49,51,52.

Well, it doesn't work that way. When the messages are loaded from disk to memory, only the messages *to* you are loaded, not any others.

So in memory, the list of new messages is not just 50 and 70, it is also including 48,49,51,52.

The logic would be:
* Find messages to user
* Find linked messages to list of mesages to user
* This list is the list of all messages captured by the function "new messages to user" - which ultimately is a subset of all messages right?

The main difficulty there is that it would also *display* the other messages in
the thread which were not to you.

digital man

This Is Spinal Tap quote #17:
David St. Hubbins: It's such a fine line between stupid, and uh... and clever. Norco, CA WX: 71.6øF, 47.0% humidity, 8 mph E wind, 0.00 inches rain/24hrs
--- Synchronet 3.17c-Win32 NewsLink 1.111
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)