Limiting the players

[OliverLSanz]

We may need to limit what the players can do:

• How many public worlds they can create.
• How long the world name is.
• How long any other input that is stored at the database is.
• etc.

so that a malicious player can't spoil the game so easily.

[OliverLSanz]

From #24:

LambdaMOO puts a global kilobyte limit to players. This covers all data of all created objects. Something like this is important, to avoid a world that weights gbs!

[OliverLSanz]

At this point anyone could put GBs and GBs of data into the database until it gets full. To prevent this, the following would need to be done:

To avoid one account from filling the database

• [ ] Give each user an account of how much data they creations are taking, and put a limit on it.
• [ ] Update that account with each creation, edition and deletion.

  To avoid one user from creating lots of accounts

• [ ] Put a limit on how many accounts can be created each day/week from the same IP.
• [ ] Also put a limit on how many accounts can be created each single day from anywhere. High enough that it won't be reached organically.

We should also check for possible back doors avoid the limitations, like custom verbs.

---

Despite what stated above, I will just put a limit on the number of public words a user can have. This will avoid one user from filling the lobby with junk worlds. I'll trust nobody takes the effort to fill the database. We should warn users that integrity of the database is not assured and they should backup their worlds often.