Text 16301, 82 rader
Skriven 2014-08-27 15:14:22 av mark lewis (1:3634/12.0)
  Kommentar till text 16283 av MICHAEL LOO (1:123/140)
Ärende: s-s-h 854
=================
 On Tue, 26 Aug 2014, MICHAEL LOO wrote to MARK LEWIS:

 MiL> It's not as though anyone said, oh, let's mispost a few messages 
 MiL> today, keep the moderator on his toes!

 MaL> exactly! ;)

 MiL> So I didn't say anything when the Russki dumped his mistake posts 
 MiL> here. Figured it would get straightened out in due course.

i wasn't being mean when i wrote my original... i wanted to get that stated in
case it appears that i was making something of the situation... my apologies if
anyone has thought that from my statements...

 MaL> as far as the gating stuff goes, some systems gate some things to 
 MaL> fidonet on a one-way basis and others are bi-directional... some 
 MaL> of the bi-directional ones are free-flowing and some require 
 MaL> manual intervention to send the posts to the other side of the 
 MaL> gate

 MiL> I'd see manual forwarding as the best solution in such a case.

it depends on the area being gated, really... manual forwarding can become a
burden in the same way that newsgroups' pre-moderation method requires that the
moderators read and approve every post before it appears in the group... areas
that require membership would have to be manually crossed over but others where
anyone can post could go either way depending on the quantity and type of
traffic...

 MiL> Bear in mind that I am against any kind of forwarding of this 
 MiL> echo, in or out.

yup... but some things do still get shared in other venues by some means... i
know that if i want to print a recipe, i have to forward it via email to one of
my other accounts where i can read it on a machine with access to the
printers... that or read it in my news server on a machine with printer
access...

 MiL> Do conferences have to be consecutively numbered? I.e., could you
 MiL> give Cooking, say, 61, and have it stay 61 if you decided to
 MiL> shutter conference 60 (for example)?

 MaL> its a QWK format thing... the message areas are recognized by QWK 
 MaL> by number and if the number changes then the messages go into the 
 MaL> wrong area

 MiL> So if you get rid of conference 60, couldn't you replace its name
 MiL> with [empty conference] as a placeholder? Sort of like
 MiL> if apartment 60 in a high-rise goes vacant, you just leave
 MiL> it vacant until you can get it occupied again, rather than
 MiL> move the tenants of 61 into 60 ... is that an okay analogy?
 MiL> I'm not sure.

the analogy works but it depends on the software and the operator... in my
software, i can just blank out the name but other operators may actually delete
the entire record... in my case, i specifically force the area numbers because
i have trouble tracking that an area that a user sees as area 55 might actually
be area 87 if the user doesn't have access to some areas and the software
presents them to the user with consequtive numbering...

 MaL> i reverted some years back to using the echotag as the area 
 MaL> name/title... mostly because some of them were quite long and got 
 MaL> chopped off... also because a lot of them were something like The 
 MaL> official support and discussion echo for BLAHBLAH

 MiL> They shouldn't make names like that. Succinctness in such fields 
 MiL> is always a virtue.

agreed but the field is basically the 'title' or 'short description' with a
paragraph description being available... it is another thing where it depends
on the software and the operator behind it...

 MiL> EGGPLANT CAVIAR
 MiL> Compiled by George G. Vitt, Jr.

interesting! i was envisioning some sort of method of making tiny balls of
eggplant for the caviar portion but i see that it is really more of a paste
thing... we might have to give it a try one day ;)

)\/(ark

 * Origin:  (1:3634/12)