Back to the main page

Mailing List Logs for ShadowRN

Message no. 1
From: Dark Avenger <Dark_Avenger@********.DEMON.CO.UK>
Subject: Newcomers Guide - Version 1 (beta)
Date: Tue, 26 Nov 1996 00:09:11 +0000
Thankyou very much Mark, for your E-mail requesting the URL, and a post
of the present (unfinished and unapproved) version of the Newcomers
Guide to Shadowtk.

The URL, for those who want to visit it live, is

http://www.petesims.demon.co.uk/newguide.html

(there is a small 20K sound file attached to the document, so if you
don't want to here it please turn sound off in your browser) :)

I appreciate that it is a little presumptious of a relative newcomer (or
at least poster) to the list to write and submit a document like this,
but the logic of those within IF-1 that contributed to the document, was
that we were best able to see the problems of a newbie <grin>

The document in it's entirety follows. (I'm afraid it's a bit long, at
somewhere around 11 pages, but as we kept finding things, so they got
added to the document. It is as comprehensive as we can make it, but
I'm sure that some of you who are patient enough to read it, will think
of something that could be added :)

Any input/observations/ideas etc are encouraged and will be received
gratefully.

Thanks all.


____________________________________________________________________
====================================================================

Shadowtk Handbook
Newcomers Guide To Posting On The Shadowtk Mail List


I appreciate that with both parts of the FAQ and all the other
information to absorb, there is an awful lot to making a post on
Shadowtk. However, once you have understood some of what is expected of
you, it is only the formatting that you need to pay attention to. The
rest is only for occasional use in different methods of including extra
information within your e-mail message.


This Handbook is produced not as a hard and fast law book that must be
adhered to, but rather in an effort to provide some of the solutions to
questions that may arise for ways to do certain things within Shadowtk.
It is designed primarily as a reference sheet for newcomers to use when
posting to Shadowtk, and a guide to solutions discovered by the IF-1
group for a variety of problems they encountered.


Hoping this will be of use to new list members as well as old list
members. It is produced here for reference when required.

Dark Avenger



Table of Contents

1. What's It All About... ?
2. What do you Mean "Post in Character"... ?
3. Posting Instructions In Brief... Sascha's Proposals
4. Time And Date...
5. What is Encryption... ?
6. Internal Conversations Within A Team...
7. Problems and Solutions...
8. Multiple Posts...
9. The Ten Commandments of Shadowtk...


1. What's It All About... ?
Shadowtk was created to allow people to discuss all aspects of the game
Shadowrun from the point of view of a character. The plots for these
discussions are formulated on PlotD, Shadowtk's sister list. From here,
a variety of characters will either provide information or discuss the
situation that has been presented in the form of Deckers posting to the
famous Shadowland BBS.


It is advised that before any post is made to the Shadowtk list, that
the question or plot you have in mind is presented to PlotD first. This
is to prevent any anger over interference with an ongoing thread, and to
ensure that your question/plot hasn't already been extensively covered
in a previous polt line.


It is unlikely that your plot will have been covered, but it is
distinctly possible that a question you may have has.



2. What do you Mean "Post in Character"... ?
Posting in character simply means that you take on the persona of a
Decker, a cyberdeck user who runs the Matrix. A Decker is a futuristic
version of the programmers and computer users that can be met on the
Internet of today. The difference is, that a Decker interfaces with his
or her cyberdeck via a neural connector, and essentially projects
his/her consciousness into the Matrix. The Matrix is the future of the
Internet. A new world of constructs, and information datastreams. An
alternate or virtual reality. The closest example to the Matrix of the
future available in modern film would be Tron, though even this is
archaic in comparison with the Matrix of 2057.


Characters on the Shadowtk Mailing List, post as Deckers in a manner
that follows the standard laid down by FASA in their sourcebooks,
examples of this will be covered below. It requires that you select a
name for your character, preferably one that is not already in use
(Characters registered with Shadowtk can be found on Mark Imriaco's
Shadowrun Web Page at Itribe
<URL: http://www.itribe.net/shadowrun/cast-db/apps/show


You can also register your character here, by following the instructions
found in Part II of the Shadowtk FAQ: Registering Your Character. It is
advised that you check this site to make sure that your character is
unique, and if so, to register the character while you are there.


Posting "In Character", means that you, taking the part of your Decker,
write messages, ideas, solutions and information to the Shadowtk list in
response to the other posts that can be found there. However, before you
do post anything to Shadowtk. It is essential that you read both parts
of the FAQ and familiarise yourself with them. I know it sounds boring
to have to read several pages of Frequently Asked Questions, but believe
me, it will not only save you a lot of trouble, but will also help you
to familiarise yourself with the list, and allow you to enjoy yourself
more without spoiling anyone else's enjoyment of the list, or getting
into trouble by doing something that is covered in the FAQ..


It is not advised that you take the persona of a character from the
Shadowrun Source Material, as these Deckers are held in high esteem, and
any impersonation will not be accepted with any particular favour.
Please try to be original in your choice of Decker name.
An example of posting in character follows.


For the purposes of clarity, examples will be given throughout this
handbook.


>>>>>[Hoi chummers, I've just acquired a run into the NAN, anyone got
any info that might be useful to my continued survival over there?]<<<<<
-- Sneezy <13:34:35/10-23-57>


In the above example, Sneezy is asking for information on The Native
American Nations, and how best to operate within the confines of the
Indian Nations.


The formatting of the question follows a rigid and inflexible procedure
that must be followed.

It consists of:


5 right chevrons (greater than signs), " >>>>> "
a square opening bracket, and " [ "
the body of the text.

Closed by:

a closing square bracket, and " ] "
five left chevrons (less than signs). " <<<<< "


The signature of the decker consists of::

eight spaces,
two hyphens (--)
another space,
the deckers name, " Sneezy "
another space,
a left chevron (less than sign) " < "
Time (hh:mm:ss) " 13:34:35 "
a forward slash " / " and
The date (mm-dd-yy) " 10-23-57 " and finally
A closing right chevron (greater than sign) " > "


Now all of this might seem a little daunting at first, but using the
above example as a template, it is easy enough to create something that
can be used time and time again, by simply cutting and pasting into your
mailer. (Please note that the example on this page uses concealed items
to create the formatting, please delete these before using it).
The most important part of the post, and the most often to receive
errors, is the Time/Date stamp, this is the one thing that people
consistently make a mistake with. It is always best for you to use your
"real" time for the post. If however you are part of a thread where you
are in contact with people in the same team, then a standard time scale
must be agreed upon and used consistently. One person should be used as
the time keeper, and all other posts should take their prompt from that
person, altering the time and date accordingly. There are certain
exceptions to this rule, but they will be dealt with in other sections.


Still the safest way to deal with the time date stamp is to take the
real time and date from where you live, and just amend the year to be
whatever the current year is on Shadowtk. Shadowrun is based
approximately 61 years in the future, so take present year and add 61.
That should be pretty concurrent with all the rest of the posts.... but
do check first.


------------------------------------------------------------

3.Posting Instructions In Brief ... Sascha's Proposals.
A few basic instructions for Posting In Character to Shadowtk have been
assembled by Sascha Pabst, and it is these suggestions that should be
paid close attention to....


* use DOUBLE Returns to mark paragraphs
* don't use signatures
* don't quote!!!


Although quoting is a standard on nearly all other mailing lists and
newsgroups.


Conversations should be quick enough on Shadowtk, that there is no need
to quote the previous post. The person you are talking to, should
remember what it is you are answering. If you feel the need to remind
people of the previous post, please try and do so within the text of
your post rather than quoting any previous comments from somebody else.


* keep the line length to less then 80 characters, preferrably 72
* When including "downloads" of data (files, recordings, movies,
whatever), the FAQ suggests the format:


+++++ Download: filename.[dos-suffix] on a seperate line


On the other hand, I suggest a slightly different format that I have
seen on ShadowTK, that would be:


+++++ Begin Download: filename.[dos-suffix]
[Description of what is being downloaded]
+++++ EOF
+++++ Done Downloading: filename.[dos-suffix]


This way we prevent the annoying "as you can see..." statements that
just try to inform the reader what is in the data. Statements?


* Time/Date stamps are not to be left out. Attach them in any case.
According to the FAQ, they are transmitted before the line transfers
data. Well, if the FAQ says so...

* Examples for Matrix-Adresses may be found in SRII, p. 164


This is a generic private post that runs over the Shadowland BBS. The
"private" tag means: This is encrypted, only the recipients may read it
(well, react to it). Remember: This is used like Email, so you can't be
sure the recipient will receive it immediately.


***** PRIVATE: name{,name, name, ...}
>>>>>[ text to insert. Remember to keep it less then 80 columns wide.


Remember to do a DOUBLE Return at each paragraph (stupid, I know, but
hey...)
]<<<<<
-- name <hh:mm:ss/mm-dd-yy>


There are 8 (!) spaces before the "--". There is 1 space after it.
Another space between the name and the time/date stamp. The time date
stamp is enclosed in lesser/larger then signs: <10:11:03/10-15-57>
Back to Top / Home / Shadowtk FAQ I / Shadowtk FAQ II


This is a public post on the Shadowland BBS. Everyone who is skilled
enough to reach SL may read it. This is like the beloved (*not*) news
system, and the same restriction as above applies: There is no way to
tell when a given character reads this. So, don't use it for urgent
messages.


>>>>>[ text to insert. Remember to keep it less then 80 columns wide.


Remember to do a DOUBLE Return at each paragraph (stupid, I know,but
hey...) ]<<<<<
-- name <hh:mm:ss/mm-dd-yy>


See above for the time/date stamp format


This is a simple phone call. No encryption is engaged, and the call is
not re-routed. We can assume at least one of the participants is using a
cellular phone.


***** INTERNAL: ChitelCo. Cellular Distribution Net
***** From: name ([Address])
***** To: name ([Address])
>>>>>[ insert real time message here ]<<<<<
-- ChitelCo. CDN Node [Address] <HH:MM:SS/mm-dd-yy>


The [Address] in the footer would be the LTG number the call is
originating from. Within the Chicago Area, I think it should be NA/UCAS-
MW-[one digit]312, with 1 and 2 being the CZ if I understand Bug City
right. [Telcom number] would be a whole URL, err, address, like NA/UCAS-
MW-x312-xxxx (somewhere in Chicago) or NA/UCAS-SEA-xxxx-xxxx (Somewhere
in Seattle; See Seattle Sourcebook for LTG numbers)


From what I have seen LTGs (the first row of numbers) can also have only
3 digits, and I suppose the access number (the last string of numbers)
can be longer then four signs.


I'd say we use the ChitelCo. whenever at least one of the phones is
cellular.Use same header, but "UCASTel Phone Comp." For stationary ones,
with this footer:


-- UCASTel PC <HH:MM:SS/mm-dd-yy>


See above for format of T/D stamp.


The reason I use "INTERNAL" here is the FAQ that states it is "for
information that would not normally be posted to the ShadowLand board,
but would be a part of normal Matrix traffic." Which would be the case
with a phone call, I think.


NOTE: Please keep a given Access Address (last number of address). This
will keep the illusion of "consistency"


Here comes a re-routed phone call (3 times re-routed). Remember to use
some adresses outside the UCAS. Good are both Tirs, Aztlan or the Pueblo
Corporate Council.


***** INTERNAL: Long Distance Phone Call
***** From: name name ([Adress])
***** To: <Unknown User> ([Adress]) <rerooted>
***** To: <Unknown User> ([Adress]) < rerooted >
***** To: <Unknown User> ([Adress]) < rerooted >
***** To: name {<garbled access number> OR ([Adress])}
>>>>>[ Text to transfer. Some

+++++ Static Error


or of course the good old...


+++++ Data Loss: 0.8 Mp

Losses may occur due to the long distance J ]<<<<<
-- name <hh:mm:ss/mm-dd-yy>


See comments about phone calls above, see comments about Time/date
stamps even further up. To have the phone call encrypted, just enclose
the message in


+++++Begin Encryption


<message>


+++++ End Encryption


You might even add a fancy program name for the encryption, like


+++++ Begin Encryption: fractal_02.exe


(just remember to end with the same.)



One thing that's still to be tried is the radio message. I suppose the
format would be like...


***** INTERNAL: Radio Message near [location]
>>>>>[ text, see about data loss, static above. Maybe even a
+++++ Radio Jammer detected...
+++++ Countermeasures activating...
+++++ Data loss: Estimated 1.2 Mp
....drek what was that? Could be inserted. ]<<<<<
-- name <hh:mm:ss/mm-dd-yy>


There are some problems with radio Messages, though. I am not sure what
to do about the header. INTERNAL is not quite right, but it's not a
public announcement, either. And it does not route through Shadowland. I
suppose Internal is the most appropriate.


The other problem is the delayed nature of the list, normally a radio
would be used two-way. Unless people email privately and one of them
sends a summary, we have a problem here... Anyone got an idea how to
solve this?



INTERNAL HEADER
For instance...


*****INTERNAL: SIGANet
>>>>>[TO: D J H Coppinger, Director


Sir, we intercepted this radio transmission from somewhere near
Baltimore.


+++++begin transcript


or


*****INTERNAL: Private Log, Colonel Tepanohoutec AIS
>>>>>[+++++begin playback


Who is behind this? Hiding data from me, defying my orders? Who would
have the gall?


. . . .


*****INTERNAL: Lone Star Precinct 16
>>>>>[Got this from a traffic camera. Check the perpetrators, see if
they're known.


+++++begin video


The street is shown in the jerky, grainy black-and-white of an old
traffic camera. For some reason your attention is drawn to the black-
clad figure, face swathed in dark cloth, as she picks her way through
the seething crowds...


. . . .


Private memos, transcribed conversations, incidents seen by drone
cameras, communications monitored by third parties, the INTERNAL header
has a lot of potential.


Sascha Pabst

--------------------------------------------------------



4. Time and Date
One of the most consistently ignored or error riddled things on Shadowtk
is the Time Date stamp. It is very easy to make a mistake with this
format and because it is considered so important, consistent errors are
likely to be received with considerable annoyance.


All time date stamps are preceded by


eight (8) spaces
-- double hyphen
space
Character Name


The correct format for time is:


< -- left chevron (less than sign)
hh -- Hours
: -- Colon
mm -- minutes
: -- colon
ss -- seconds
e.g.: -- Sneezy <18:23:47


Forward slash seperator between time and date
/


The correct date format is:
(after the slash)


mm -- Current month (in this example October)
- ... single hyphen
dd -- Current day date
- ... single hyphen
yy -- Current year (61 years into the future)
> -- right chevron (greater than sign)
e.g.: /25-10-57>


Combined the Time/Date stamp should look like:-


-- Sneezy <18:23:47 /10-25-57>


This is the most rigid and inflexible of the rules on Shadowtk, and must
be adhered to. Occasional mistakes will be made, even by the older
listmembers, but constant infraction of this rule is sternly frowned
upon.


The other example of the Time/Date stamp is the type used by the top end
Deckers of Fasa Source Material


-- The Smiling Bandit <ha:ha:ha/he-he-he>


This is not allowed on Shadowtk, without considerable debate and
permission from the other list members. Any use of this style of
time/date alteration will be considered as the poster being too lazy to
think and make his/her T/D stamp fit in with the list. This will usually
result in private e-mail to the culprit, asking them to conform with the
rest of the list. Consequent infractions will result in removal from the
list.


-- Lazy Soso <**:**:**/**-**-**>


This is another example of the "non" stamp, and is also to be
avoided..... Basically, don't do it, unless the list members on PlotD
have first given their permission.


Finally the current FASA method of posting to Shadowland has been
changed, and now follows what FASA want us to believe is a more modern
way of posting to the Matrix, it is one of the signs from FASA that the
Matrix has been upgraded, and that systems/cyberdecks are evolving,
rather than remaining in the static form they've been so far. It follows
a much simpler procedure using single indent right chevrons (greater
than signs) and no time/date stamp. I suspect this is partly to cut down
on production times for FASA material, as it is easier to use and can be
followed much quicker.


> ..Read the Newsfaxes kid. You think we ain't got a nice little low
intensity war going on now?
> City Slicker


Although this is used by FASA, it is not recognised on Shadowtk yet, so
please don't use this method.


The disadvantages to using this format on Shadowtk, is that no linearity
between the posts is constructed, making life much more difficult for
the person compiling the Logs. There is alos the fact that the recipient
of the message has no idea when it was posted. It is highly unlikely
that the list will be changing to this style in near future. As the logs
and other factors must be considered, and some way of recognising ther
order of posts must be agreed upon before anything like this is likely
to appear. I suspect that another reason, is that following the older
style of formatting also encourages people to think before posting, and
means that there are less people who will post silly comments to the
list, thereby preventing arguments and casual silliness.


The only advantage to the new style is the lack of time date stamp,
which saves a lot of trouble for people who are working within a team
that exists in different time zones. However, with a little thought it
is relatively easy to keep your time/date current.


The time standard used on Shadowtk is GMT (Greenwich MeanTime -
Greenwich is the home of an atomic clock that sets the standard time for
the rest of the world - nice to see we Brits are still good for
something). Relative time zones to this are Seattle - 8 hours behind
GMT, Chicago, 6 hours behind GMT. Though a better reference is someone
who lives near or on the same time zone as the city you are posting
from. It is usually recommended however, that you use your current local
time and date.


5. What is Encryption...?
Encryption is a method of concealing or protecting a document from being
read by others.


There are three types of Encryption that can be used on Shadowtk.
Private, Internal, and Not To.


PRIVATE: <name>


This encryption key is used when the poster only wants this message sent
to one other character and for that character alone respond. It is
considered bad etiquette to respond to a Private post, unless


a) It is addressed to your character, or


b) You have been given permission to respond.


There is no need to add anything else to this key, as all types of
Encryption available to the Deckers is assumed to be contained within
this statement. E.G.:-


***** PRIVATE: Bull
>>>>>[ Thanx, pal, thanx a lot for your coded EMailer. Finally I don't
have to nurse Canis whenever he wants to make contact. He's about as
much sense for tech as I have for the international stock market, and I
keep my cash in a sock under my mattress at home :-) Thanx, pal, I owe
you one for this! ]<<<<<
-- Orion <15:26:17/10-19-57>


This is the most common form of Encryption, and is only necessary when
communicating directly with an individual.


INTERNAL: <name>


The next type of encryption is the INTERNAL: key This is used as the FAQ
states:- INTERNAL messages can be used to provide insight on what is
going on behind the scenes in a plot for the ShadowTk list-members.
INTERNAL messages are for behind the scenes plot development for
information that would not normally be posted to the Shadowland board,
but would be a part of normal Matrix traffic


This includes Video feed, Cybercam recordings, sound files from bugs or
listening equipment, Internal communications within opposing
organisations, even, communications within a Shadowrun team. for
example:


*****Internal Seattle FBI Surveillance dep to Directors office
>>>>>[Sir the Subject has been identified as one of the people wanted
for questioning concerning the Lassiter Investments terrorist bombings.
We have a second clip that shows him with two of the others wanted for
questioning ready to receive clip?.]<<<<<
-- Special Agent Driscol <06:57:45/10-17-57>
Surveillance dept.


or


***** INTERNAL: Invasion Force Internal Email
>>>>>[
+++++ Message-From: Bull
+++++ Subject: Bubba


Ok Bubba, you should be able to read this. Please explain how you got
this mailer, and in English this time. I'm not sure just what dialect
you were speaking in, but the mailer had a hell of a time translating
it.]<<<<<
-- IF Mailer Demon <20:39:25/10-18-57>


or


*****INTERNAL: Lone Star Precinct 16
>>>>>[Got this from a traffic camera. Check the perpetrators, see if
they're known.

+++++begin video



The last type of encryption is the "barring" message. Following the
keywords "NOT TO" the names of the characters that the writer does not
want to receive the message are listed. Once again, it is very poor
etiquette to have a character respond to a message he has been barred
from. E.g.:


***** INTERNAL: Invasion Force Internal Email
***** NOT TO: Bubba
>>>>>[

+++++ Message-From: Bull
+++++ Subject: Who the...???

Ok, I'm using the new mailer system for this, so hopefully I got all the
bugs out. Ok... Just who is Bubba and how in the hell did he get one of
my mailers?? Also, just what should we do about the situation? He said
he might be able to help?? Consider him a security breach? Or talk to
him and see what's up?]<<<<<
-- IF Mailer Demon <20:37:47/10-18-57>


Finally, there is one further type of encryption.... That which is
included within the text to conceal a subject... For example:


>>>>>>[Glad to have you along Smudge. Things are in hand at present, but
we could do with some help pretty soon. Meet us at >>encrypted<< I'm
sure Bull would be grateful for a helping hand and a friendly face, as I
figure it, he's got cut up real bad in there. Welcome Chummer]<<<<<<
-- Dark Avenger (17:40:22/10-11-57)


This is particularly useful if


a) you are not familiar enough with a city to feel confident about
posting addresses, and


b) to show that there is a certain secrecy and extra effort used to hide
the location, time or payment...


Another way to handle this is to either use the following


>>>>>[Glad to have you along. Meet us at >>place<< at
>>time<<, I look
forward to seeing you]<<<<<
-- Sneezy (17:40:22/10-11-57)


These two formats are also acceptable. When transferring payment, there
are several different ways to achieve this, all of them using the above
example of internal message encryption


>>>>>[Glad to have you along. Meet us at >>place<< at
>>time<<, I look
forward to seeing you. As agreed here is your fee >>electronic transfer
nuyen<< Hope you can bring the data with you.]<<<<<
-- Sneezy (17:40:22/10-11-57)


Basically it allows you a certain freedom of including something with
the mail, that offers safety and secrecy.


Also see Sascha's Proposals above, for further details on using
Encryption.



6. Internal Conversations Within A Team...
One problem that arose as a result of the IF-1 crew, was the problem
with non-deckers communicating with each other. As it was a dynamic plot
that was evolving as it was played, we met a couple of stumbling blocks
that resulted in a certain amount of confusion. General communications
would not travel through the Shadowland BBS, even though they did use a
part of the Matrix for communications. It was eventually agreed upon to
utilise a system designed by Steve Ratkovitch... This system was
approved by the Listmembers and keeper of Shadowtk, and is recognised as
a valid means of communication. It keeps the INTERNAL header because it
is routed through several different cyberdecks, within the same group.


Bull's Internal Mailer

***** INTERNAL: Invasion Force Internal Emailer
>>>>>[

+++++ Message-From: Canis
+++++ Subject:I'm in trouble..

They're coming to take me away, haha! ]<<<<<
-- IF Mailer Daemon <hh:mm:ss/mm-dd-yy>


This system allowed the entire IF-1 character members to communicate
with each other without having to resort to Decker summaries of events.
It meant that more players could join in and left a considerable amount
of freedom to communicate with each other.


Further references to this manner of posting is available in the Plot
Logs, Chapters Four and Five This system was used extensively for
communications within IF-1, though the header has now changed to PRIVATE
in order to reflect that this is used as a form of communication within
the five teams of IF-1 and with each other, the e-mail system is routed
through multiple cyberdecks, and through the Matrix.


7. Problems and Solutions
A number of problems that arose within the IF-1 group as a result of the
large number of co-operating players brought to a head some of the
problems with a lack of clarity in the Shadowtk FAQ. The FAQ has been
updated by Mark Imbriaco, and will be kept up to date and posted at
regular monthly intervals. Part of the reason problems arose, is because
IF-1 wanted to do something they had never before done. Deal with a
situation, as it was occurring. This caused more than a few headaches
for IF-1 and not a few reactions from the Shadowtk list members.


One problem that arose, was that of uploading data to the IF-1 group. At
one point during the adventure, Dark Avenger disappeared into the
Shadows for just over a week. He was unable to communicate with the IF-1
group and could not access the Matrix without giving himself away. It
was assumed he had died.


One way that this was done, was used by Bull in Chapter 1, where he
included video footage for Inferno, showing his breakout from Chicago
Containment Zone, and later, to illustrate some points for Dark Avenger.
The method used by Bull, is perfect where only one file of footage is
being used. However, DA wanted to upload information containing several
different files, and the format for this can be found in the Invasion
Force Plot Logs <URL>, and in the examples below.


At a point some days after his disappearance, Dark Avenger's Decker
Gates, managed to sneak past the Matrix security that was watching for
IF-1 activity and upload a file that enabled him to inform IF-1 that DA
was still alive, and give them an idea of what he was up to.


The post followed the following format...


*****PRIVATE: Invasion_Force.1
>>>>>[Thanks be to the Gods.... I'm through. Sorry to crash you like
this people, but DA's kinda pissed and wants this data uploaded to
ya'll.

+++++Activate Frame: Stinkbugtran.ars
+++++Begin trans: >> Vidcomp File: A/7645-1D4/7.hqx 041057-201-590ACX
+++++Estimated Data Loss: 2.7 Mp
+++++Begin decompression routine.
+++++Playback file: Vidcomp: A/7645-1D4/7.hqx 041057-201-590ACX


*****CYBERCAM recording: Begin file Exon1a7.vid: (23:12:11)
LLE engaged...


It's raining. Street lights reflect from puddles on the streets creating
bizarrely writhing reflections in the rippling puddles. Left the street
is empty, to the right is an old disused petrol station, pumps and Exon
sign rusting and almost unrecognisable. Some shelter is offered by the
doorway of the small pawn shop, but the wind blows much of the rain in.
A battered Land Rover rolls silently into the Exon forecourt, lights
off.


Four men bail out taking defensive positions around the forecourt,
assault rifles at the ready, body armour glistening in the rain. An
officer climbs out, glances around, nods, and walks towards the deeper
shadows near the ruined office. Something moves inside, a strange
lurching gait, but the figure cannot be made out clearly, though it does
appear bulkier than the officer. Words are exchanged, the officer by his
actions appears to become somewhat agitated.......


*****INTERNAL: Headset tight beam trans: Thor
>>>>>[Shado, you getting any of this?]<<<<< Hisses a voice
like gravel
on a beach.

A strong female voice with oriental undertones, answers.
>>>>>[No sir, nothing, weather's jackin' with the mike, gain's shot to
hell, nothing but hiss.]<<<<<

>>>>>[Ok, people, shut it down, this is pointless, drop to
trans.]<<<<<
*****EOF Exon1a7.vid


The problem that arose with this post, was the inclusion of sound
transmissions over headset radio, that had been recorded separately to
the Cybercam video. It was decided to use the INTERNAL header, and
follow standard posting procedure. Also, where it was several video and
sound clips contained within one file, it was decided to split all the
individual sections into their relevant files.. i.e:.


*****CYBERCAM recording: Begin file Exon1a7.vid: (23:12:11)


The above example, uses the header Cybercam, to indicate where the data
has come from, and the "Begin File" instruction to show the start of the
file. Each of the separate Cybercam recordings followed this same
format, and each file was given it's own name i.e: It should really use
the "drama" header


+++++CYBERCAM recording:
(five plus signs)


but it was accepted by the list members, so it can be done this way.


Exon1a7.vid: (23:12:11)


Any and all files uploaded to other posters and to team/plot members
should have a name for each and every file followed by a standard DOS
suffix, similar to the above example. It doesn't matter whether you use
a name or alphanumeric title, provided the file has one.
The Dark Avenger post was one of the first posts from IF-1 to experiment
in this manner, and was met with surprising acceptance. Where it was a
bit new, Dark Avenger expected to step on a few toes with this style of
post, but... as it transpired, it followed what everyone on the list
expected. A pleasant surprise. However, one observation was made, that
overall the post became difficult to read because of the constant use of
Shadowtk formatting, and it was suggested that rather than use the
Chevron's to indicate a characters speech within a sound file, it might
be easier and also less confusing on the eye to use standard speech
quotation marks. Again, when experimenting with something new, make sure
that someone else, either in your plot line or from PlotD sees the post
prior to you dumping it into Shadowtk. This way any formatting that is
wrong, may be picked up by the other person. In the case of the Dark
Avenger Cybercam post, another team member Sascha Pabst was used to
proof read the post prior to it being sent.


This would have the effect of altering the above example to look like
this:-


*****CYBERCAM recording: Begin file Exon1a7.vid: (23:12:11)
LLE engaged...

(The LLE engaged, indicates here that Low Light Enhabcement has been
activated to make the picture in the camera more visible, this can be
used for Thermographic and any other cyberware that is utilised to get
the results, it's not necessaty, but it helps to feed across the
impression that the environment is such that equipment is being used to
compensate, and adds to the atmosphere.)
<snip text>


*****INTERNAL: Headset tight beam trans: Thor
"Shado, you getting any of this?" Hisses a voice like gravel on a beach.

A strong female voice with oriental undertones, answers. "No sir,
nothing, weather's jackin' with the mike, gain's shot to hell, nothing
but hiss."

"Ok, people, shut it down, this is pointless, drop to trans."
*****EOF Exon1a7.vid


Serving the dual purpose of informing the recipient that there is video
and sound, following standard speech methods, and yet still allowing for
the inclusion of a sound file within the recording. As can be seen, with
the removal of the "Decker" style formatting, the section becomes much
easier to read, and yet still comes across as was intended.


There are a number of things that can occur within a post to people, and
these should be dealt with in the most logical manner first, without
attempting to rewrite the FAQ. If anything is in grave doubt, it should
be cleared up via PlotD before posting to Shadowtk.


Another thing mentioned in the FAQ, is "Dramatics". This header covers
all other types of Enclosure within a post... Dramatics are preceded by
the five Plus symbols +++++ and are used to denote the type of
enclosure.


For example:


+++++Activate Frame: Stinkbugtran.ars
+++++Begin trans: >> Vidcomp File: A/7645-1D4/7.hqx 041057-201-590ACX


This example attempts to show that the decker is utilising a program to
send the Vidcomp file, and also uses the "dramatics leader to show that
file. Other examples:


+++++ Download: bad_guy.picture


or


+++++ Video: You see at big monkey climbing a skyscraper while little
airplanes annoy him.


The "dramatics" symbol leader can be used to cover a wide variety of
posts to offer a little drama to what would otherwise be a boring post.
Again it should not be used constantly, Unless you are doing a lot of
moving of data.


9. Multiple Posts
One further thing that arose in the IF-1 group, was the fact that so
many people were interacting with the group to situations and plot
threads that were being designed by the IF founders.

This resulted in 20 people eagerly awaiting their opportunity to post to
Shadowtk concerning actions their character was taking, without having
to wait for requests or commands from the individual leaders. One way
around this problem was to form teams within the IF-1 Header.
Five teams were created

<URL>

The original concept behind this creation, was to allow people to act
individually within team actions. Using Zeus as the Core Team,
containing Bull and his family, and six of Dark Avengers squad as
firepower and guards. Zeus was the most important cell within IF-1. Thor
was led by Dark Avenger, and was the primary team for information
gathering and insurgency/counter-insurgency against the "Chess Set
Enemies" With the Magic Heavy Odin and Loki as the primary protectors
and front line troops caring for Zeus.


The Ten Commandments Of Shadowtk

The TEN COMMANDMENTS OF SHADOWTK From Second In Command, High Lord FAQ
Keeper Vincent Esposito, posted to the Shadtk list whilst a discussion
of the FAQ was in progress.
(As one of the "founding fathers" and the original "Deputy Fearless
Leader" I can tell you directly what the ORIGINAL import of the FAQ
was.)


The commandments of Shadowtk are thus:

1) Thou shalt not kill off the character of another without permission.

2) Thou shalt not push the envelope of the Shadowrun universe without
discussing it with your peers first (used to be handled in email, now
more codified in PLOTD)

3) Thou shalt remain consistent with the established history of the list
(at least as much as anyone remembers)

4) While thou mayest feel free to jump in and comment on a plot, please
confer with the others involved in the plot before posting something
that could mess up the plotline. (case: Back in the Omega Island thing,
someone decided to sink the USS Intrepid while I still had plans for it
and wanted to keep it sort of in one piece for future use. I posted a
quick fix which resulted in an angry exchange of email that went "I'm
sick of your plot"/"Don't mess with my aircraft carrier, that's Doom's
job" This is actually a corrollary to commandments 1 and 3.)

5) Thou shalt keep in mind that you are posting on a live BBS with often
dubious security.

6) Thou shalt be advised that new list members are better off lurking a
bit before posting. This is not writ in stone, but will help newbs from
stepping on peoples toes accidentally.

7) Thou shalt have fun. Hey, if you're not having fun, take a break and
do something other than sit behind your computer for a while, then come
back.

8) Thou shalt not violate established posting formats. The occasional
mistake happens, but consistent mis-posting gets in everyone's way, and
creates more work for the lord high archivist. The T/D stamp thing is a
point of debate, and will likely remain so.

9) Thou shalt not use the handle Dark Elf unless you are me. (this one
was in the original FAQ, if only to give the originators a good
chuckle.)

10) Thou shalt not under any circumstances use other characters or
character names without checking with the owner of the aforementioned
character first. If in doubt Thou shalt check the official Shadowtk
Character List at http://www.itribe.net/shadowrun/cast-db/apps/show

(commandment 10 added by Dark Avenger, following observations made
within IF and PlotD)



Author: Nemesis/Dark Avenger/Orion.
Copyright [c] 1996 [Edgerunners Inc.]. All rights reserved.
Information in this document is subject to change without notice.
Other products and companies referred to herein are trademarks or
registered trademarks of their respective companies or mark holders.
Document Created: November 7, 1996
Last revised: November 25, 1996.





--
__ \ | \
| | _` | __| | / _ \ \ \ / _ \ __ \ _` | _ \ __|
| | ( | | < ___ \ \ \ / __/ | | ( | __/ |
____/ \__,_|_| _|\_\ _/ _\ \_/ \___|_| _|\__, |\___|_|
A dark shadow in a dark world |___/

Further Reading

If you enjoyed reading about Newcomers Guide - Version 1 (beta), you may also be interested in:

Disclaimer

These messages were posted a long time ago on a mailing list far, far away. The copyright to their contents probably lies with the original authors of the individual messages, but since they were published in an electronic forum that anyone could subscribe to, and the logs were available to subscribers and most likely non-subscribers as well, it's felt that re-publishing them here is a kind of public service.