list(1)

💖 list(1) 💖

okay bestie, sit down, hydrate, because we're doing list today. this one lives in the General Commands Manual, section 1, and it's literally the "who even is authenticated around here" command. no cap. 🫶

---

✨ NAME ✨

list — List all authenticated bindings (User ID and certificate pairs)

like. it lists your authenticated bindings. User ID + certificate pairs. that's the whole vibe. 💅

---

🌸 SYNOPSIS 🌸

list [--email] [-h|--help] [PATTERN]

---

💜 DESCRIPTION 💜

So what does it actually do? It lists all authenticated bindings — User ID and certificate pairs, bestie. that's it, that's the job.

but here's the ✨filter✨: only bindings that meet the specified trust amount get shown. and by default that means bindings that are fully authenticated, i.e. they have a trust amount of 120. if it doesn't hit that bar, it's not making the cut. not on this list. 🙈

and okay, important one: even if no bindings are shown, the exit status is 0. so like, an empty list is still a slay. it's not an error, it's just quiet. 💀

now, if --email is provided, a pattern matches if it's a case insensitive substring of the email address as-is, or the normalized email address. 🎀

Note: unlike the email address, the pattern is not normalized. In particular, puny code normalization is not done on the pattern. so the pattern stays exactly as you typed it, no glow-up applied. 😭

---

🎀 OPTIONS 🎀

• --email — Changes the USERID parameter to match User IDs with the specified email address.

It interprets the USERID parameter as an email address, which is then used to select User IDs with that email address. 💌

Unlike when comparing User IDs, email addresses are first normalized by the domain to ASCII using IDNA2008 Punycode conversion, and then the resulting email address is converted to lowercase using the empty locale. so yeah, the emails get the full normalization treatment. the pattern does not. iykyk. ✨

If multiple User IDs match, they are each considered in turn, and this function returns success if at least one of those User IDs can be authenticated.

Note: The paths to the different User IDs are not combined. 🚫 they stay separate, don't be trying to merge them.

• -h, --help — Print help (see a summary with '-h')
• [PATTERN] — A pattern to select the bindings to authenticate.

The pattern is treated as a UTF-8 encoded string, and a case insensitive substring search (using the current locale) is performed against each User ID. 🔍

If a User ID is not valid UTF-8, the binding is ignored. sorry bestie, it's not invited to the party. 🙈

---

🦋 EXTRA 🦋

EXAMPLES:

# List all bindings for example.org that are at least partially #
authenticated.  $ sq-wot --keyring keyring.pgp \
    --partial \
    --trust-root 8F17777118A33DDA9BA48E62AACB3243630052D9 \
  list @example.org

# The same as above, but output in DOT format and convert it to # an SVG
using Graphviz's DOT compiler.  $ sq-wot --format dot \
    --keyring keyring.pgp \
    --partial \
    --trust-root 8F17777118A33DDA9BA48E62AACB3243630052D9 \
  list @example.org \
  | dot -Tsvg -o example_org.svg

---

and that's the whole page, bestie!! 💖 you now know list better than most people know their own keyring. main character energy fr fr. go list something. 🦋👑

signing off from section 1 of the General Commands Manual — it's list(1), and yes, the footer really does just say list again, iconic of it honestly. 🌈💅