User:Xenon dichloride/Terminal: Difference between revisions

(9 intermediate revisions by the same user not shown)

Line 2:

The following represents the initial state:

~/

~/ # owner: e

boot/ # owner: su

instances

files

Line 10:

commands

winning

~~judgement~~

commands/ # owner: su

mk

cp

Line 21:

Line 20:

kill

sudo

players/ # owner: su

== ~/boot/instances ==

The system must reboot to enact any changes to ~~files within~~ ~/boot/. Each week 3 new instances are created, with the contents of ~/boot/ directory at the end of the previous instance comprising the ~~new~~ rules:

The system must reboot to enact any changes to contents of ~/boot/. Each week 3 new instances are created, with the contents of the files in ~/boot/ directory at the end of the previous instance comprising the rules for the instance:

Instance I: Sunday, Monday

Line 32:

Line 31:

Instance III: Friday, Saturday

The rules must be continuously obeyed by all players.

The rules ~~defined by the files within ~/boot/~~ must be obeyed by all players.

== ~/boot/files ==

A file is a document containing data such as text, formatting, tables or images. ~~It is represented as a section~~ Anything that can be added to an [[Main Page|Infinite Nomic Wiki]] page is valid content for a file. Every file has an owner, which is 'su' unless otherwise specified.

A file is a document containing data such as text, formatting, tables or images. Anything that can be added to an [[Main Page|Infinite Nomic Wiki]] page is valid content for a file. Every file has an owner, which is 'su' unless otherwise specified.

== ~/boot/users ==

A user can own files and execute commands. Every player is a user. Additionally, 'su' ~~can be used to reference~~ the superuser, with absolute control of the system. 'e' ~~can reference~~ every user.

A user can own files and execute commands. Every player is a user. Additionally, 'su' references the superuser, with absolute control of the system. 'e' references every user.

== ~/boot/players ==

Line 51:

Line 49:

is_su = false

privileges = 2

If that file already exists (the player has the same id), is_player = true. If multiple players would have files of the same name, subsequent player files have an integer appended to their name to represent their place when joining.

If that file already exists (the player has the same id), is_player = true. If a player's name contains "/" characters, they are replaced by "|". If multiple players would have files of the same name, subsequent player files have an integer appended to their name to represent their place when joining.

When a player ceases being a player, is_player = false. If a player or ex-player leaves the server, they are no longer a player and their file is removed.

Line 66:

Line 64:

|mk

|make

|mk {location ~~or if blank: ~/~~} {name~~} {owner or if blank: you~~} {contents as attached .txt file or code block}

|mk {location} {name (no "/")} {contents as attached .txt file or code block} {owner or if blank: you}

|Creates a file at the specified location.

|-

|mkdir

|make_directory

|mkdir {location ~~or if blank: ~/~~} {name} {owner or if blank: you}

|mkdir {location} {name (no "/")} {owner or if blank: you}

|Creates a directory at the specified location.

|-

Line 91:

Line 89:

|rn

|rename

|rn {location} {new name}

|rn {location} {new name (no "/")}

|Changes the name of a file or directory.

|-

Line 106:

Line 104:

|kill

|

|kill {~~link~~ to ~~message~~ or message id or if blank: all active}

|kill {reply or links to messages or message ids or if blank: all active}

|Terminates an active ~~process~~ ran by you.

|Terminates active processes ran by you.

|-

|sudo

Line 120:

Line 118:

== ~/boot/winning ==

The first player to become a 'superuser' (is_su = true) wins the cycle.

~~== ~/boot/judgement ==~~

There shall be a sole Judge, responsible for resolving rules disputes. An incumbent Judge can be removed with the assent of two players, but they should not be removed except for abuse of office. A person can cease being the Judge by publicly stating so.

A request for justice shall take the form of a question or statement. The proper response to a question is an answer to that question, and the proper response to a statement is the truth value of that statement.

Upon formal submission of a request for justice by a person other than themself in #request-for-justice, the Judge shall, as quickly as possible, issue a response to the request. This response shall be binding only to the extent that it reasonably directly pertains to the request, and only to the extent that it does not blatantly and obviously contradict rules text while still considering the expressed or clearly implied legislative intent.

Within 4 days of a judge issuing a ruling, a public vote of confidence on that ruling can be initiated in #request-for-justice. Votes may be cast in such a vote for a period of 2 days after initiation. Votes are to be cast by 👍 or 👎 reactions on a clearly designated poll message; if a person's vote is unclear, it is to affirm the judgement. A ruling is overturned if strictly more players vote in favor of overturning than affirming.

A ruling may be overturned by the Judge who made it within one week of being made. When a ruling is overturned in this manner, the Judge shall then issue a new ruling on the initial request, which shall be binding in the same manner as the original ruling.

~~An overturned ruling shall have no bearing on the interpretation of the rules or of the gamestate.~~

Any reputable player may become a candidate for the Judge by sending a message in the channel #judge-elections. If there are any Judge candidacies put forward during a week, the player whose message is both popular and has the most 👍 reactions from players becomes the Judge once that week ends. A Judge Candidacy message is popular if it has more 👍 than 👎 reactions from players on its initiating message. Ties are broken in favor of the player with the earliest text message during that week.

@@ Line 2: / Line 2: @@
 The following represents the initial state:
-  ~/
+  ~/                   # owner: e
-      boot/          # owner: su
+      boot/            # owner: su
           instances
           files
@@ Line 10: / Line 10: @@
           commands
           winning
-         judgement
+      commands/        # owner: su
-      commands/      # owner: su
           mk
           cp
@@ Line 21: / Line 20: @@
           kill
           sudo
-      players/       # owner: su
+      players/         # owner: su
 == ~/boot/instances ==
-The system must reboot to enact any changes to files within ~/boot/. Each week 3 new instances are created, with the contents of ~/boot/ directory at the end of the previous instance comprising the new rules:
+The system must reboot to enact any changes to contents of ~/boot/. Each week 3 new instances are created, with the contents of the files in ~/boot/ directory at the end of the previous instance comprising the rules for the instance:
 Instance I: Sunday, Monday
@@ Line 32: / Line 31: @@
 Instance III: Friday, Saturday
+The rules must be continuously obeyed by all players.
-The rules defined by the files within ~/boot/ must be obeyed by all players.
 == ~/boot/files ==
-A file is a document containing data such as text, formatting, tables or images. It is represented as a section Anything that can be added to an [[Main Page|Infinite Nomic Wiki]] page is valid content for a file. Every file has an owner, which is 'su' unless otherwise specified.
+A file is a document containing data such as text, formatting, tables or images. Anything that can be added to an [[Main Page|Infinite Nomic Wiki]] page is valid content for a file. Every file has an owner, which is 'su' unless otherwise specified.
 == ~/boot/users ==
-A user can own files and execute commands. Every player is a user. Additionally, 'su' can be used to reference the superuser, with absolute control of the system. 'e' can reference every user.
+A user can own files and execute commands. Every player is a user. Additionally, 'su' references the superuser, with absolute control of the system. 'e' references every user.
 == ~/boot/players ==
@@ Line 51: / Line 49: @@
   is_su = false
   privileges = 2
-If that file already exists (the player has the same id), is_player = true. If multiple players would have files of the same name, subsequent player files have an integer appended to their name to represent their place when joining.
+If that file already exists (the player has the same id), is_player = true. If a player's name contains "/" characters, they are replaced by "|". If multiple players would have files of the same name, subsequent player files have an integer appended to their name to represent their place when joining.
 When a player ceases being a player, is_player = false. If a player or ex-player leaves the server, they are no longer a player and their file is removed.
@@ Line 66: / Line 64: @@
 |mk
 |make
-|mk {location or if blank: ~/} {name} {owner or if blank: you} {contents as attached .txt file or code block}
+|mk {location} {name (no "/")} {contents as attached .txt file or code block} {owner or if blank: you}
 |Creates a file at the specified location.
 |-
 |mkdir
 |make_directory
-|mkdir {location or if blank: ~/} {name} {owner or if blank: you}
+|mkdir {location} {name (no "/")} {owner or if blank: you}
 |Creates a directory at the specified location.
 |-
@@ Line 91: / Line 89: @@
 |rn
 |rename
-|rn {location} {new name}
+|rn {location} {new name (no "/")}
 |Changes the name of a file or directory.
 |-
@@ Line 106: / Line 104: @@
 |kill
 |
-|kill {link to message or message id or if blank: all active}
+|kill {reply or links to messages or message ids or if blank: all active}
-|Terminates an active process ran by you.
+|Terminates active processes ran by you.
 |-
 |sudo
@@ Line 120: / Line 118: @@
 == ~/boot/winning ==
 The first player to become a 'superuser' (is_su = true) wins the cycle.
-== ~/boot/judgement ==
-There shall be a sole Judge, responsible for resolving rules disputes. An incumbent Judge can be removed with the assent of two players, but they should not be removed except for abuse of office. A person can cease being the Judge by publicly stating so.
-A request for justice shall take the form of a question or statement. The proper response to a question is an answer to that question, and the proper response to a statement is the truth value of that statement.
-Upon formal submission of a request for justice by a person other than themself in #request-for-justice, the Judge shall, as quickly as possible, issue a response to the request. This response shall be binding only to the extent that it reasonably directly pertains to the request, and only to the extent that it does not blatantly and obviously contradict rules text while still considering the expressed or clearly implied legislative intent.
-Within 4 days of a judge issuing a ruling, a public vote of confidence on that ruling can be initiated in #request-for-justice. Votes may be cast in such a vote for a period of 2 days after initiation. Votes are to be cast by 👍 or 👎 reactions on a clearly designated poll message; if a person's vote is unclear, it is to affirm the judgement. A ruling is overturned if strictly more players vote in favor of overturning than affirming.
-A ruling may be overturned by the Judge who made it within one week of being made. When a ruling is overturned in this manner, the Judge shall then issue a new ruling on the initial request, which shall be binding in the same manner as the original ruling.
-An overturned ruling shall have no bearing on the interpretation of the rules or of the gamestate.
-Any reputable player may become a candidate for the Judge by sending a message in the channel #judge-elections. If there are any Judge candidacies put forward during a week, the player whose message is both popular and has the most 👍 reactions from players becomes the Judge once that week ends. A Judge Candidacy message is popular if it has more 👍 than 👎 reactions from players on its initiating message. Ties are broken in favor of the player with the earliest text message during that week.