John Seekins

I mean...I'd like our deploys of Hubot to not require downtime. Which using this brain does require. Also, I think it would address issues like #39 .

My understanding is we can only have one instance of Hubot running at a time (because the brain reads/writes a string, which can overwrite values between two instances). Thus, we...

In that case, I guess we leave this be as there's no real difference. Other than _some_ scenarios have slightly improved read/write speed. Which isn't enough of an argument.

I'd love to see Hubot actually able to run more than one instance. If it's just the internal API for the brain causing the issues, that seems solvable. I'm no...

An update on this ticket from way in the past: We ended up switching from statsd emission to Otel emission. Since Otel aggregates stats in-memory before shipping them, our aggregation...