* rc: (451 commits)
ping: delay kick until after ames processes breach
aqua: make faster so moon-az can finish
ping: fix comments
ping: avoid fragile state transitions
ames: don't say not responding if we haven't been talking
eth-watcher; don't start timer if already started
chat: hotfixing a class name
chat: fix sidebar toggle on chat update
dojo: set prompt on watch
gen: add comments on new generators
chat-cli: our-self with bowl set
keys: add +keys for diagnostics
verb: add +verb %bowl to print bowl on every event
azimuth-tracker: add |kick
clay: don't make |cancel require argument
jael: allowed skipped rifts
ames: make life printf helpful
Revert "|ames-verb: fix generator sample type"
|ames-verb: fix generator sample type
gall: correctly construct wire for ap-specific-take
...
Signed-off-by: Jared Tobin <jared@tlon.io>
We were calling it directly, rather than through the (initialized) tc core,
causing the bowl in its context to be the *bowl, resulting in [~zod /] audience.
The old version of ping hung when your sponsor breached while you had an
outstanding poke. I believe it would do the same if your sponsor
changed and the old sponsor didn't respond to you.
This explicitly subscribes to Jael for updates to our sponsorship tree,
and kicks the pings of any ships that change rift and any changed
sponsors.
Sending a %code letter without output would cause its code to be evaluated on
the recipients' ships. While that shouldn't naturally occur post-#2009, and
evaluation of %code letters remains virtualized, it's still remote code
execution, and worth fixing as such.
