Constraints for user input

[OliverLSanz]

Like a limit for name and description lengths

[OliverLSanz]

Also, it's needed to limit where newlines are allowed.

• Descriptions? OK.
• User names? NOT SO OK.

[OliverLSanz]

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! This is more related to #102

[OliverLSanz]

Constraints ordered priority-wise

Priority 1

To avoid one user breaking the UI for all players.

• [x] World name: limited length and no line breaks.
• [x] Snapshot name: limited length and no line breaks.
• [x] User name: limited length and no line breaks.

  Priority 2

  To avoid one user leveraging communication commands to show misleading info.

• [ ] Emote verb: no line breaks
• [ ] Say verb: no line breaks
• [ ] Shout verb: no line breaks

  Priority 3

  Avoid creators from breaking the UI for users in the world.

• [ ] Item names: limited length, no line breaks
• [ ] Exit names: limited length, no line breaks
• [ ] Room names: limited length, no line breaks

  Other considerations

  Keep in mind that:

• users may try to bypass these constraints in a number of ways, like manually modifying world exports.
• some values can be entered from many places. For example, the world name can be entered from world creation, edition, public snapshot deployment... The same happens for other values, like item names.
• I'm not taking into account the avoidance of really big messages that can deplete disk or memory. I leave that for #102 and #113

[OliverLSanz]

Priority one constraints are enough for now.