I can't say what made me choose it out of all the other critically-acclaimed titles on the carousel. [...] The setting is the ABC live broadcast control room at the 1972 Summer Olympics in Munich. The action is a terrorist attack.

Does the MLS specification offer a practical mechanism for the end users to mitigate the effect of a compromised Authentication Service? No, it does not; it only refers to the approaches based on key transparency, but they are not practical in real-world applications, and, to the best of my knowledge, are not implemented in any of the communication platforms that deployed MLS.

$ cargo run -- --debug
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.25s
     Running `target/debug/notedeck --debug`

$ cargo --version
cargo 1.86.0 (adf9b6ad1 2025-02-28)
$ rustc --version
rustc 1.86.0 (05f9846f8 2025-03-31) (built from a source tarball)

$ cargo run -- --debug
error: failed to load manifest for workspace member `/home/ekzyis/prog/notedeck/crates/notedeck_chrome`
referenced by workspace at `/home/ekzyis/prog/notedeck/Cargo.toml`

Caused by:
  failed to load manifest for dependency `notedeck_clndash`

Caused by:
  failed to parse manifest at `/home/ekzyis/prog/notedeck/crates/notedeck_clndash/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.80.0-nightly (6087566b3 2024-04-30)).
  Consider adding `cargo-features = ["edition2024"]` to the top of Cargo.toml (above the [package] table) to tell Cargo you are opting in to use this unstable feature.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.