Where Does Tuba Store Accounts and Settings?
Tuba keeps settings in dconf with tokens in Secret Service on Linux. No flat config file exists despite expectations.
Last updated
Tuba is Linux-native Fediverse with split secrets. Settings branch through dconf per account with timeline and proxy options. Tokens live in Secret Service as OAuth bodies, never passwords. Cache fills standard trees beneath.
No flat config file exists to quote, which this post states instead of inventing. Flatpak mediates secrets through portals with overrides available. Posts and timelines stay server-side with local prefs, tokens and cache.
Where Tuba stores this, by platform
/dev/geopjr/Tuba
Settings branch with per-account children for prefs and visibility. No flat file exists despite expectations. Dump the branch for migration.
~/.cache/tuba
Media and API cache in standard trees with Flatpak twins beneath var. Clear freely without touching settings or tokens. In-memory caches supplement on-disk.
Frequently asked questions
How do I back up Tuba?
Dump the Tuba dconf branch with per-account children for prefs while tokens stay in the keyring. Search secrets by app ID through standard tools. Cache clears through its own folders without touching either store.
Where is the Tuba config file?
It does not exist despite expectations. Settings live in dconf with tokens in Secret Service and cache in standard trees. Flatpak portals mediate secrets with overrides where needed.
How does Tuba store passwords?
Through OAuth tokens only, never passwords, in Secret Service bodies with account metadata. Native keyrings back them with portal fallbacks under Flatpak. Verify through search tools or keyring managers.
Notice an outdated path? Let us know.