|
Grex > Intro > #3: Discussion about the Intro conference | |
|
| Author |
Message |
introfw
|
|
Discussion about the Intro conference
| 
Apr 16 19:46 UTC 1996 |
The rest of the items in this conference will show you the
variety of topics that we discuss here on Grex. These items
will be linked over from the many other conferences available
here.
Remember that you can type "help conferences" at the Ok: prompt
to get a listing of all the conferences, and then use the "join"
command to go to that conference. For example, "join music"
will take you to the Music conference. If you see an item here
that interests you, you should go to the conference that item
is in, to see many more items with the same general topic.
It is our hope that this Intro conference will show you the
variety and depth of the Grex conferences, and will convince
to take part in the many discussions we have here.
If you have any questions relating specifically to the Intro
conference, you should put them in this item by typing
"respond" at the "Respond or pass?" prompt below.
|
| 139 responses total. |
aruba
|
|
response 1 of 139:
|
Apr 19 17:44 UTC 1996 |
I like your selection of items, Rob.
|
srw
|
|
response 2 of 139:
|
Apr 22 00:49 UTC 1996 |
I think this conference could be an excellent way for new users to
begin experienceing conferencing. Thanks for setting this up Rob.
|
jblue
|
|
response 3 of 139:
|
Apr 27 14:56 UTC 1996 |
What't the best way to get a *COMPLETE* rundown on all there is to know
about Picospan? I want to capture it in *one* file so I can print it out
and study it, refer to it, later. Item 2 here is good but not complete.
"help intro" ditto. I could go through each help item seperately but
then my file is full of extra garbage like prompts. Isn't there one
master guide or man page or something? Picospan seem powerful but I find
it a bit confusing, non-intuitive, to really use it to the fullest. And
the help system's the same, bits and pieces in different places.
|
ajax
|
|
response 4 of 139:
|
Apr 27 18:30 UTC 1996 |
I don't know of a master guide. I think capturing bits from the help
system might be the best you can do, for a comprehensive guide. The
most important ones for basic commands, in my opinion, are
"help morecommands," "help misc," and typing "help" at a respond or
pass prompt, although like you said, the info is scattered about in
many different places.
|
umac
|
|
response 5 of 139:
|
May 1 09:29 UTC 1996 |
read
|
gbaker
|
|
response 6 of 139:
|
May 2 12:39 UTC 1996 |
Once someone told me how to download the contents of an item (the humour item
on Agora into my directory so I could send it to someone by mail (I know I
should have just used the 'read' function in Pine).
My question is : How can I find out the filename of a particular item?
Thanks for the help!
|
ajax
|
|
response 7 of 139:
|
May 2 22:41 UTC 1996 |
The "extract" command is actually easier than finding the file of an item.
(Though if you want to find the file, conferences are in the /bbs directory,
and the current agora conference is #17, so item 12 would be in
/bbs/agora17/_12). To use the extract command, type
"!extract agora 12 >filename", and that will put agora item 12 into a file
called "filename." You can also extract specific responses, like say
"!extract agora 12 50-60 >filename" would list just responses 50-60.
|
manickam
|
|
response 8 of 139:
|
May 5 04:09 UTC 1996 |
|
introfw
|
|
response 9 of 139:
|
May 5 09:48 UTC 1996 |
Welcome to Grex, manickam!
|
rcurl
|
|
response 10 of 139:
|
May 11 20:34 UTC 1996 |
Rob, you are cycling items in and out of intro at a very fat pace. I
think it would work fine if the pace were slowed. One object would be to
not have you "burn out" too fast. More practically, though, a point is to
try to have new users not stay here very long, but find their own "home"
cf. If there is a new show here every week, they might just want to stick
around. If you are going to just keep 3 items in the show, perhaps change
one every two weeks, or so? I also think that a couple more shows could be
run at the same time. With four, one changing every two weeks, you'd have
an eight week "residence time". This is just an example: I don't know what
is optimum. This could be experimented with, to find out.
|
introfw
|
|
response 11 of 139:
|
May 11 22:51 UTC 1996 |
Funny you should say that, I was just chiding myself for
letting several of the items stay here for far too long.
Opinions from anyone else?
|
selena
|
|
response 12 of 139:
|
May 12 01:13 UTC 1996 |
Rob, this is totally cool! If ONLY this had been here when I first got here..
|
rcurl
|
|
response 13 of 139:
|
May 12 05:37 UTC 1996 |
(I meant fast, not "fat".) Rob, what evidence do you have that you were
letting items stay too long? What are your specific goals in choosing the
residence time of items? My point is made by selena, who thinks intro
is "totally cool". That means she might spend more time in intro, than
in the cfs from which it comes. That is counter productive, if intro
is meant to attract (and instruct) users to use more of the cfs. You need
to make it less cool, so the conferences themselves do not suffer too
much by comparison. If *they* suffer, you won't have much new material to feed
into intro. (This is an exercise in working in an environment where everything
is connected to everything else.)
|
introfw
|
|
response 14 of 139:
|
May 12 08:16 UTC 1996 |
Re 12 - Thanks!
Re 13 - When I first envisioned this conference, I told myseld
that I shouldn't let any item stay here for more than two weeks,
no matter how interesting it was. I left two items (the
"English as an official language" and Red Wings items) here for
three weeks. I've been kicking myself since...
My main concern is that if I leave items here for a month or
two (which seems to be the time frame you're suggesting, correct
me if I'm wrong), that problems will arise:
* I'll have a bunch of items that were active when I linked them,
but died off within a few days. Do we want new users to see lots
of dead items here?
* If the items here are hugely successful, like the two items I
mentioned above, then they will have a huge number of responses,
making it that much harder for a new user to join in.
* If I get in the habit of leaving items here for months, then
people will grow comfortable with this conference, knowing that
the items here that interest him will be here forever. I don't
want that. I want Intro to be a perpetual kick in the pants.
I want users to know that if they want to follow the items that
really catch their fancy, they should get out of here and go to
the other conferences, instead of relying on this one.
Maybe it's because I'm from the MTV generation, where if the camera
stays on something for fifteen seconds, that's ten seconds too long.
But I never intended Intro to be static. I always wanted items to
cycle in and out quickly, in fact, more quickly than I have been.
That way, the items will be recent, no items dated 1993, and new
users will still be able to get involved in the discussion without
having to sift through 500 responses.
|
rcurl
|
|
response 15 of 139:
|
May 12 17:27 UTC 1996 |
We aren't seeing it very differently. However we have a big flux of
newusers, so if an item stays for time T, few experience it for that long
- in the steady state the average is T/2, and of course for some its just
once. This is a basis for (about) doubling whatever you think is a
reasonable time of explosure for one individual. I'd also like to suggest
that some items be brought over *truncated* - picked up from just the past
few months (plus the heading). I agree that even an active and interesting
item, but which started in 1993, can be too long - so, cut the first 250
(?!!) responses, and show the relatively current activity. (Of course,
tell the reader where to go to read the WHOLE thing.) I would not worry
about having *a* deadish item, because a newuser might want to pick up on
it. Why not pick a really dead item, and see what happens if you expose it
in this format? You can, of course, keep items for different lengths of
times, depending on your goals in including them. You seem to be flexible
and creative about the intro cf, so I'm just exploring the dimensions of
flexibility and creativity.
|
introfw
|
|
response 16 of 139:
|
May 13 10:23 UTC 1996 |
I can't "trim" an older item in the manner you suggest, and I
don't want to split it off into a seperate item, that would only
confuse folks. "Hey, I responded to this item in Intro, why isn't
my responses showing up in this other conference?"
|
rcurl
|
|
response 17 of 139:
|
May 13 15:20 UTC 1996 |
"You can do anything with computers....." Right?
|
introfw
|
|
response 18 of 139:
|
May 13 16:45 UTC 1996 |
Only non-programmers ever say that. >8)
|
rcurl
|
|
response 19 of 139:
|
May 13 20:04 UTC 1996 |
The items files are maintained separately in diferent cfs, even if linked.
Apparently new responses are added to both. So, can't the item file in
intro be truncated (or perhaps one should say cropped to) remove early
responses, without affecting the file in the other cf?
|
introfw
|
|
response 20 of 139:
|
May 13 20:24 UTC 1996 |
Yes, but it would require root (I believe), and I think
that would set a bad precedent.
|
rcurl
|
|
response 21 of 139:
|
May 13 21:36 UTC 1996 |
This is a new and special conference, for which I would think that new and
special procedures would be acceptable (you are already inventing these).
I think it should be acceptable for a root to perform the surgery, if a
root scalpel is necessary. It would not affect the original item file.
(Sort of a root canal, eh?)
|
yo
|
|
response 22 of 139:
|
May 17 18:07 UTC 1996 |
I have to agree with Rob here it is better to crop items from here and let
people go to the correct conf. (thats the idea here) if you cut early
responses it sometimes voids the discusions the item has developed making the
first response after seem odd to new users, adding new items and cropping the
old keeps intrest up for new users. Old grexxers arn't supposed to hang out
in intro they can find the confferences they want. New users don't know whats
out there that is what intro is for.
|
rcurl
|
|
response 23 of 139:
|
May 21 05:58 UTC 1996 |
You must not have dealt with many 400 response items....it is just as well
to come in at an interesting point, and not read the whole thing. Besides,
we all do this when conferences are restarted - you are always coming in
in the middle, even if the item starts with response 1 (which following
response 705 in a previous incarnation). But my point is to not worry
about things like this - pick up Items wherever they are interesting. A
user can always go to the real item, and read earlier responses if they
want to.
|
yo
|
|
response 24 of 139:
|
Jun 1 13:02 UTC 1996 |
you must not have been a new user a while ago
|