What makes Architext not ready for real random users?

[OliverLSanz]

• [ ] A public "tabern" and one or two more escape room words.
• [ ] A escape room word that serves as tutorial for the other verbs.
• [ ] Untested with friends.
• [x] Server should be secure.
• [x] There is no error message if cant connect to server.
• [x] Remove apostrophes from verb syntax
• [x] Review verb names
• [x] I am not 100% sure about the way item visibility works.
• [x] I'm an unsure about the ux of custom verb creation -> I can change it latter retaining the same representation method.
• [x] Client too wide in desktop.
• [x] Bugs.
• [x] Imports freeze all user sessions.
• [x] Not load tested. -> Who cares. Users will load test it for me.
• [x] There is no rate or content limit for each user / IP / each field length / number of things... -> I can think about this latter.
• [x] I'm unsure about the ux of snapshots -> Changing this latter won't be a breaking change

[OliverLSanz]

About item visibility.

Option A: Listed items should not exist. Takable items are the only ones listed. Downside: Lazy builders may not like this.

Option B: Everything stays as it is.

I'm taking B.

[OliverLSanz]

About verbs

Remove apostrophes from verbs syntax

textto '' ─ sends the text to the selected user. takefrom '' ─ moves the item from the user's inventory to the room. give '' ─ moves the item from the room to the user's inventory tpuser '' ─ teleports the user to the selected room.

I will change it to: verb argument one - argument two

I could write a smart algorithm to handle most of the cases, but probably it will be future work:

string = "user name message to send"
n = 0

do:
  n = n + 1
  x = first n words of string
  y = rest of the string
  exact = user name whose name is x if there is one, otherwise retain the previous value of exact
  options = user names that start with the word x followed by a whitespace but have more text in them.
  if exact and not options:
    result = exact
  if not exact and not options:
    error, there is no user with that name
while not result

This would require:

• Avoid verbs with dangling whitespaces (I should be doing this if I'm not already). -> Done