Bot interface

[ihh]

• Each user account has an associated "bot" with behavior described by a state machine (finite-state transducer)
• A bot consists of moods (states) and reactions (transitions)
  • States have output labels (rhs of spontaneous emission) and output rates
  • Transitions have an input label (matching keyword) & an output label (rhs of reply), both optional
  • Bots have a single public state and a private state for each user
• Use wikimess messaging and passport-twitter
  • Public state listens to wikimess broadcast messages & Twitter (streaming API, search or whatever)
  • Private state listens to wikimess mailbox and Twitter direct messages

Domain-specific language for moods and reactions; edit in simple textbox

• List of transitions
  • e.g. syntax @src?{keyword}rate=>@dest{output}
  • ?{keyword}, rate, @dest and {output} are all optional, but at least one of @dest or {output} must be present
  • first named @src is initial mood

[ihh]

@bored,@quiet:
{hello|{clickhole|the onion&daily mash}} => @interested {$Surprised!}

@bored:
10 => @bored {$Hurry!}
20 => @quiet {So $bored.}

@interested:
=> @bored {$Never_say_die.}

Rates are expressed as time parameters: when in state @bored, roughly every ten seconds you'll get a $Hurry!, and after roughly twenty seconds it'll print So $bored. and go quiet.

[ihh]

Per-player rate limits

If a bot's reaction rate in any given state exceeds this limit, its rate will be rounded to that

Effective update rate needs to be scaled by (T,B,S)

• max time since last login M (if greater than this, player rate is zero)
• time-since-last-login factor exp(-(t/T))
• per-bot rate limit B
• max rate for entire system S

Each Player has own values for these parameters: they are model attributes, but attributes that cannot be edited via web API, and have sensible default parameters

[ihh]

NB no need for JSON schema; controller should just try PEGjs parser