As I said, just because you don't like it doesn't make it broken.
As you are the only one whose ever complained, I would suggest the
problem is elsewhere -- and very much not mine.
OTOH, I originally had Synchronet set up so that all the message
areas were grouped by network -- which is how you like it -- and
users (plural) did complain because they couldn't find the "echoes
When a user isn't either pissed at the network admins, or banned by
then, which networks you want/need to avoid isn't an issue.
OTOH, I originally had Synchronet set up so that all the message areas were grouped by network -- which is how you like it -- and users
(plural) did complain because they couldn't find the "echoes about (subject)" that they were used to participating in on the predecessor
BBS.
predecessor BBS.
can message areas not be grouped in more than one way? i don't
recall. perhaps in a(n unpleasant) way where two areas listed in two
groups use the same files?
can message areas not be grouped in more than one way? i don't recall. perhaps in a(n unpleasant) way where two areas listed in two groups use the same files?
can message areas not be grouped in more than one way? i don't recall. perha > in a(n unpleasant) way where two areas listed in two groups use the same filThat would certainly be unpleasant. ;)
can message areas not be grouped in more than one way? i don't recall. perhaps in a(n unpleasant) way where two areas listed in two groups use t > > same files?
They actually can be, by having a sub-board with the same internal code in m > than one message group. This means you can't use the "internal code prefix"
feature, but it is doable. Some oddity with message scan config / pointers might occur also, I don't recall.
| Sysop: | KrAAB |
|---|---|
| Location: | Donna, TX |
| Users: | 6 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 42:29:52 |
| Calls: | 56,907 |
| Files: | 3,065 |
| D/L today: |
3 files (1,879K bytes) |
| Messages: | 53,402 |