docs: clarify browser cookies and add releasing guide

This commit is contained in:
Peter Steinberger
2025-12-03 16:03:54 +00:00
parent 6804f2f483
commit cef8af07b5
2 changed files with 63 additions and 0 deletions
+7
View File
@@ -144,6 +144,13 @@ bird check
- Requires Chrome to be logged into x.com
- May prompt for keychain access on first run
### Browser cookie sources (macOS)
- **Chrome (default)**: reads `~/Library/Application Support/Google/Chrome/<Profile>/Cookies` (WAL/SHM copied too). Select with `--chrome-profile <name>`; defaults to `Default` or whatever you set in config.
- **Firefox**: reads `~/Library/Application Support/Firefox/Profiles/<profile>/cookies.sqlite`. Select with `--firefox-profile <name>`; defaults to `*.default-release` if present. Use this when Chrome isn’t logged in.
Precedence still holds: CLI flags > env vars > project config > global config. So a one-off `--firefox-profile default-release` overrides any config defaults.
### Posting via Sweetistics (API key)
If you have a Sweetistics API key, `bird` can post through the Sweetistics SaaS instead of using local Twitter cookies: