Files and privacy #
libbui contacts Libby and OverDrive for your account, catalogue, and reader
editions. Adobe downloads also contact the activation and licence services
needed to fulfil the selected loan. Covers and book files come from the
content addresses returned by those services. There is no telemetry,
analytics or crash reporting. Requests identify themselves as libbui/<version>.
On Linux and macOS it follows the XDG layout; on Windows it uses the usual
known folders. libbui paths prints the exact locations on your machine.
| What | Where (Linux and macOS) |
|---|---|
| Configuration | ~/.config/libbui/config.toml |
| Pairing | ~/.config/libbui/identity.json |
| Personal collections, observations, follows and annotations | ~/.local/share/libbui/personal-library.json |
| Adobe authorization | ~/.local/share/libbui/ebook-authorization/ |
| Download queue | ~/.local/state/libbui/downloads.json |
| Logs | ~/.local/state/libbui/logs/, one file a day, the last 7 kept |
| Library index | ~/.local/share/libbui/library.json |
| Cover cache | ~/.cache/libbui/covers/ |
| Books | ~/Documents/Libby/ (download_dir) |
XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_CACHE_HOME and XDG_STATE_HOME
are honoured, and LIBBUI_CONFIG_DIR, LIBBUI_DATA_DIR, LIBBUI_CACHE_DIR
and LIBBUI_STATE_DIR override each one.
The pairing file holds Libby's sign-in token for this device. It is a full
login to your library account, so it is written with owner-only permissions
(0600 in a 0700 folder), and libbui refuses to use it if other users can
read it. It is never logged. Deleting it, or libbui unpair, signs this
computer out.
Adobe downloads keep a separate device authorization, including private keys, in the data directory shown above. It is saved with owner-only permissions and reused across downloads. Unpairing Libby does not delete this authorization.
Being a polite client #
Libraries suspend cards that look automated, and the suspension lands on a real person. libbui sends one account request at a time with a pause between them, never polls in the background (except while waiting for a setup code), and never borrows or returns on its own. If the library suspends a card, libbui stops using it and tells you. Please keep scripts built on the command line equally gentle.