Hi there

Some further suggestions, one or two I think others have made as well?

1) For menu commands - file group change (FG) and message group change (MG) having the ability to display groups in a two column layout vs one column.
This may be better suited to a .INI file vs the display prompt approach at present? I'm not sure.

2) Index area reader - a switch in ANSIMIDX.INI that hides echomail groups
with no new messages

e.g

; Display only message bases with new messages

new_only = true

I would also add this is as switch for the MI menu command so sysops can
offer users this option. A user may wish to toggle it on/off themselves?

3) Looking for a quick way to 'catch up / mark all as read' across all subscribed message bases and groups. At the moment setting last read pointers and applying a certain date to all bases can achieve this but I'm wondering about a switch or some other way of doing it? If you could use the TAB key in the area index reader to select certain base / all bases then use CTRL-U to apply to all selected bases... that would be one way.

Just a few random thoughts :)

Best, Paul

--- Mystic BBS v1.12 A37 2017/12/30 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Good ideas

On 01:34 31/12 , Avon wrote:

Hi there

Some further suggestions, one or two I think others have made as well?

1) For menu commands - file group change (FG) and message group change (MG) >having the ability to display groups in a two column layout vs one column. >This may be better suited to a .INI file vs the display prompt approach at >present? I'm not sure.

2) Index area reader - a switch in ANSIMIDX.INI that hides echomail groups >with no new messages

e.g

; Display only message bases with new messages

new_only = true

I would also add this is as switch for the MI menu command so sysops can >offer users this option. A user may wish to toggle it on/off themselves?

3) Looking for a quick way to 'catch up / mark all as read' across all >subscribed message bases and groups. At the moment setting last read pointers >and applying a certain date to all bases can achieve this but I'm wondering >about a switch or some other way of doing it? If you could use the TAB key in >the area index reader to select certain base / all bases then use CTRL-U to >apply to all selected bases... that would be one way.

Just a few random thoughts :)

Best, Paul

--- Mystic BBS v1.12 A37 2017/12/30 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/30 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

3) Looking for a quick way to 'catch up / mark all as read' across all subscribed message bases and groups. At the moment setting last read pointers and applying a certain date to all bases can achieve this but I'm wondering about a switch or some other way of doing it? If you could use the TAB key in the area index reader to select certain base / all bases then use CTRL-U to apply to all selected bases... that would be
one way.

You may or may not remember back to when the file base index was added, but the intention is to replace the message base index with the same style the file base index uses, where you can tag bases and sub/unsub/perform actions against them.

What you're describing is exactly how the file base index works now so that would become part of the message reader.

--- Mystic BBS v1.12 A37 2017/12/30 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/30/17, g00r00 pondered and said...

What you're describing is exactly how the file base index works now so that would become part of the message reader.

I'm having that aha moment... yes this does ring bells with me. Sounds good thanks.

--- Mystic BBS v1.12 A37 2017/12/30 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)