When I think about tradeoffs in #ActivityPub I think in part about what problems are hard or easy, and who might have solved it.

For example: I _could_ write my own queue, but building something that wouldn't embarass me if it appeared in a #jepsen ( https://jepsen.io ) blog entry is actually _really difficult_.

Something that won't lose data in a variety of failure modes and that can be relocated to a separate container/system if needed.

So it's a no-brainer to use someone else's.

A new #Jepsen report! We analyzed @redpandadata (a Kafka-compatible distributed queue) and discuss crashes, aborted reads, inconsistent offsets, and lost/stale messages, along with some potentially surprising aspects of the Kafka transaction protocol. https://jepsen.io/analyses/redpanda-21.10.1

Here's a summary about the Freenode stuff that I thought was helpful. I don't know where this is all going to settle out, but I've registered #riemann and #jepsen over on irc.libera.chat. Will stick around on Freenode for a bit just in case. https://gist.github.com/joepie91/df80d8d36cd9d1bde46ba018af497409

New #Jepsen report: we worked with @ScyllaDB to identify and fix cases of LWT split-brain in healthy clusters due to improper hashing and membership changes, as well as documentation improvements. Notably, Scylla no longer claims non-LWT isolation! https://jepsen.io/analyses/scylla-4.2-rc3

RT @TzachL
Hello #clojure friends
If you have some free time and you know #jepsen, this might be relevant for you
https://www.scylladb.com/company/careers/co/engineering/7C.71C/clojure-contractor-temp/all/ #scylladb

A #Jepsen report! We worked together with Dgraph Labs to follow up 2018 work on version 1.0.2 (all issues fixed!), and found some new bugs in tablet migration with version 1.1.1:

https://jepsen.io/analyses/dgraph-1.1.1