-
Notifications
You must be signed in to change notification settings - Fork 0
/
privacy.html
83 lines (67 loc) · 3.03 KB
/
privacy.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
<html>
<head>
<title>The MUCK Manual: Admin: Privacy Issues</title>
</head>
<body bgcolor="#FFFFFF">
<center>
<a href="shareresp.html">prev</a>|
<a href="toc.html">toc</a>|
<a href="au.html">next</a>
</center>
<table>
<tr>
<td width="20%"> </tc>
<td>
<!-- BODY CONTENT HERE -->
<p><b>5.2.4 Privacy Issues</b></p>
<p>Privacy on <code>MUCKs</code> is a charged issue, and making good decisions
about how to handle privacy issues requires making mature judgments in the face
of seemingly contradictory considerations. </p>
<p>On the one hand, there is no guarentee of privacy in an online
environment. On the other hand, there is no excuse for administrators
who abuse their position to pry into the online lives of players on
their worlds.</p>
<p>On the one hand, the subjective experience of <code>VR</code> as a
`safe' environment often leads people to let down their emotional guard...
to reveal intimate or painful details of their lives to others online.
Administrators should take every precaution against violating the
implied trusts that lead these players to make such revelations. On the
other hand, people have organized illegal activities online, and the
administrators of worlds where this has taken place have been embroiled
in legal issues as a result. Administrators owe it to themselves and to
other players on the <code>MUCK</code> to take reasonable precautions against
such cases.</p>
<p>Doing a good job with privacy issues is primarily a matter of following
an important list of DON'Ts:</p>
<ul>
<p><li>DON'T read log files unless you have a specific, valid reason for
doing to. Filter the output so you only read what you need to read.</p>
<p><li>DON'T set yourself <code>Dark</code> and move about the <code>
MUCK</code> to populated areas, eavesdropping on conversations.</p>
<p><li>DON'T use <code>Darked</code> puppets to eavesdrop on rooms that
you would otherwise not be able to hear.</p>
<p><li>DON'T <code>@teleport</code> into private rooms without warning.</p>
<p><li>DON'T <code>@teleport</code> online players without warning them.</p>
<p><li>DON'T <code>examine</code> players' properties unless you have
a specific, valid reason for doing so.</p>
</ul>
<p>Religiously abiding by these "don'ts" in conjunction with keeping a log
of commands issued by players is a reasonable compromise. Be aware that
if you do log commands, and players on your world are investigated for
illegal online activities (which includes using online worlds to organize
illegal <code>RL</code> activities), your command logs may be subpoenaed. It
is not absolutely necessary for your <code>AUP</code> to state that you log
commands, but you will be on firmer ground if you do so: players will not be
able to claim that they did not know that commands were logged, and would have
acted differently if they had known.</p>
<center>
<a href="shareresp.html">prev</a>|
<a href="toc.html">toc</a>|
<a href="#top">top</a>|
<a href="au.html">next</a>
</center>
</td>
<td width="20%"> </tc>
</table>
</body>
</html>