tokwise 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/dist/browser-cookies.js +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -43,7 +43,7 @@ npm link
|
|
|
43
43
|
```bash
|
|
44
44
|
# Optional: save a browser cookie for private collections or liked videos.
|
|
45
45
|
# Easiest on macOS: pull it straight from a logged-in Chromium browser.
|
|
46
|
-
tokwise auth from-browser # auto-detects Chrome, Brave, Edge, Arc, or Chromium
|
|
46
|
+
tokwise auth from-browser # auto-detects Chrome, Brave, Edge, Arc, Dia, or Chromium
|
|
47
47
|
tokwise auth refresh # re-pull later when the session goes stale
|
|
48
48
|
|
|
49
49
|
# Or paste a cookie manually (works everywhere).
|
|
@@ -155,7 +155,7 @@ tokwise sync --collection "name-123" # uses the @handle saved with your cookie
|
|
|
155
155
|
|
|
156
156
|
The bare-slug form needs the username tied to your cookie. Tokwise tries to detect it automatically when you run `tokwise auth set` or `tokwise auth from-browser`; you can also set it explicitly with `tokwise auth set-username <handle>` or `--username` on those commands. `tokwise auth show` reports the saved handle.
|
|
157
157
|
|
|
158
|
-
Private collections usually require a fresh browser cookie from a logged-in session. On macOS, `tokwise auth from-browser` reads and decrypts it straight from a logged-in Chromium browser (Chrome, Brave, Edge, Arc, or Chromium) via the macOS Keychain, and `tokwise auth refresh` re-pulls it when the session goes stale. On other platforms or browsers, paste it manually with `tokwise auth set`. Cookies are stored locally only (`auth.json`, chmod 600).
|
|
158
|
+
Private collections usually require a fresh browser cookie from a logged-in session. On macOS, `tokwise auth from-browser` reads and decrypts it straight from a logged-in Chromium browser (Chrome, Brave, Edge, Arc, Dia, or Chromium) via the macOS Keychain, and `tokwise auth refresh` re-pulls it when the session goes stale. On other platforms or browsers, paste it manually with `tokwise auth set`. Cookies are stored locally only (`auth.json`, chmod 600).
|
|
159
159
|
|
|
160
160
|
## Transcription
|
|
161
161
|
|
package/dist/browser-cookies.js
CHANGED
|
@@ -3,12 +3,13 @@ import fs from "node:fs/promises";
|
|
|
3
3
|
import os from "node:os";
|
|
4
4
|
import path from "node:path";
|
|
5
5
|
import { runProcess } from "./process.js";
|
|
6
|
-
export const SUPPORTED_BROWSERS = ["chrome", "brave", "edge", "arc", "chromium"];
|
|
6
|
+
export const SUPPORTED_BROWSERS = ["chrome", "brave", "edge", "arc", "dia", "chromium"];
|
|
7
7
|
const CHANNELS = {
|
|
8
8
|
chrome: { dir: "Google/Chrome", service: "Chrome Safe Storage", account: "Chrome" },
|
|
9
9
|
brave: { dir: "BraveSoftware/Brave-Browser", service: "Brave Safe Storage", account: "Brave" },
|
|
10
10
|
edge: { dir: "Microsoft Edge", service: "Microsoft Edge Safe Storage", account: "Microsoft Edge" },
|
|
11
11
|
arc: { dir: "Arc/User Data", service: "Arc Safe Storage", account: "Arc" },
|
|
12
|
+
dia: { dir: "Dia/User Data", service: "Dia Safe Storage", account: "Dia" },
|
|
12
13
|
chromium: { dir: "Chromium", service: "Chromium Safe Storage", account: "Chromium" },
|
|
13
14
|
};
|
|
14
15
|
export function isChromiumBrowser(value) {
|
package/package.json
CHANGED