telstore 0.1.0 → 0.1.1

package/README.md

@@ -1,19 +1,19 @@
-# telark
+# telstore
 
 Split large files into 1.8GB chunks, store them on Telegram, and restore them intact.
 
 ## Quick start
 
 ```bash
-npx telark login                        # once only
-npx telark config chat @my_backups      # where backups go, from now on
-npx telark data.tar                     # split it and send it there
-npx telark data.tar --to @somewhere     # somewhere else, this run only
-npx telark config                       # every setting and where its value comes from
-npx telark status                       # account, destination, unfinished backups
-npx telark list                         # what is already stored in the destination
-npx telark restore telark-20260905-7f3a91
-npx telark delete telark-20260905-7f3a91   # take it back out of the chat, for good
+npx telstore login                        # once only
+npx telstore config chat @my_backups      # where backups go, from now on
+npx telstore data.tar                     # split it and send it there
+npx telstore data.tar --to @somewhere     # somewhere else, this run only
+npx telstore config                       # every setting and where its value comes from
+npx telstore status                       # account, destination, unfinished backups
+npx telstore list                         # what is already stored in the destination
+npx telstore restore telstore-20260905-7f3a91
+npx telstore delete telstore-20260905-7f3a91   # take it back out of the chat, for good
 ```
 
 ## What you need
@@ -21,19 +21,19 @@ npx telark delete telark-20260905-7f3a91   # take it back out of the chat, for g
 - Node.js 18 or newer.
 - An `api_id` and `api_hash` from <https://my.telegram.org> → API development tools. The `login` command asks for both, plus your phone number and the verification code.
 
-telark signs in with your own Telegram account (MTProto), not a bot. That is a hard requirement: the Bot API caps uploads at 50MB per file, while a user account gets 2GB.
+telstore signs in with your own Telegram account (MTProto), not a bot. That is a hard requirement: the Bot API caps uploads at 50MB per file, while a user account gets 2GB.
 
 ## Settings and flags
 
-There are two ways to say what telark should do, and they never overlap. **`config` writes;
+There are two ways to say what telstore should do, and they never overlap. **`config` writes;
 flags do not.** A flag applies to the run you typed it on and changes nothing on disk, so
 `--to @elsewhere` sends one backup elsewhere without moving the destination for the next one.
 
 ```bash
-npx telark config                       # everything, and whether it is yours or a default
-npx telark config chat                  # one value, bare, ready to pipe
-npx telark config chunkSize 500MB       # change it for good
-npx telark config chunkSize --unset     # back to the default
+npx telstore config                       # everything, and whether it is yours or a default
+npx telstore config chat                  # one value, bare, ready to pipe
+npx telstore config chunkSize 500MB       # change it for good
+npx telstore config chunkSize --unset     # back to the default
 ```
 
 | Setting | Flag | Default | Meaning |
@@ -63,24 +63,24 @@ follows carries a summary card:
 🗄 data.tar
 ━━━━━━━━━━━━━━━
 💾 21.4 GB · 12 chunks
-🆔 telark-20260905-7f3a91
+🆔 telstore-20260905-7f3a91
 📅 2026-09-05 16:40 UTC
 
-↩ npx telark restore telark-20260905-7f3a91
-#telark
+↩ npx telstore restore telstore-20260905-7f3a91
+#telstore
 ```
 
-`npx telark list` reads those cards straight out of the chat — one search, no downloads —
+`npx telstore list` reads those cards straight out of the chat — one search, no downloads —
 and lays them out as a table:
 
 ```
 Destination  https://web.telegram.org/k/#@my_backups
 
-BACKUP ID               FILE            SIZE  CHUNKS  CREATED
-telark-20260905-7f3a91  data.tar     21.4 GB      12  2026-09-05
-telark-20260901-9de447  photos.zip  940.3 MB       1  2026-09-01
+BACKUP ID                 FILE            SIZE  CHUNKS  CREATED
+telstore-20260905-7f3a91  data.tar     21.4 GB      12  2026-09-05
+telstore-20260901-9de447  photos.zip  940.3 MB       1  2026-09-01
 
-2 backups. Restore with: npx telark restore <backup-id>
+2 backups. Restore with: npx telstore restore <backup-id>
 ```
 
 A backup uploaded before the card existed still gets a row, with dashes where the caption
@@ -88,22 +88,22 @@ says nothing — `list` reports what the chat holds and never fills gaps with gu
 
 ## How it works
 
-Every run mints a `backupId`. The file is read directly by offset — no temporary copies — and uploaded as documents named `<backupId>.partNNNN`. Once every chunk is up, telark sends a JSON manifest listing the message id and sha256 of each one. Restore needs only the `backupId`: it finds the manifest in the chat, downloads each chunk to its exact position in a `.partial` file, checks every chunk's sha256 and size, and renames it to the real file only after *all* chunks match.
+Every run mints a `backupId`. The file is read directly by offset — no temporary copies — and uploaded as documents named `<backupId>.partNNNN`. Once every chunk is up, telstore sends a JSON manifest listing the message id and sha256 of each one. Restore needs only the `backupId`: it finds the manifest in the chat, downloads each chunk to its exact position in a `.partial` file, checks every chunk's sha256 and size, and renames it to the real file only after *all* chunks match.
 
-If the connection drops during an **upload**, just run the same command again — progress lives in `~/.telark/state/` and finished chunks are skipped, keeping the same `backupId`. Two things to know about rerunning:
+If the connection drops during an **upload**, just run the same command again — progress lives in `~/.telstore/state/` and finished chunks are skipped, keeping the same `backupId`. Two things to know about rerunning:
 
-- Running again against a destination that differs from the one in the unfinished progress makes telark **refuse to run** rather than silently redirect — one backup cannot be split across two destinations. The error names the chat to pass as `--to` to carry on, or the state file to delete to start a new backup. It reads the same whether the mismatch came from a flag or from your configured `chat`.
+- Running again against a destination that differs from the one in the unfinished progress makes telstore **refuse to run** rather than silently redirect — one backup cannot be split across two destinations. The error names the chat to pass as `--to` to carry on, or the state file to delete to start a new backup. It reads the same whether the mismatch came from a flag or from your configured `chat`.
 - Running again **without** `--chunk-size` resumes at the size the backup started with, whatever your configured `chunkSize` says today. A setting is what to use when nobody asks for anything; it is not somebody asking.
-- Running again **with** a `--chunk-size` that differs from that size makes telark **refuse to run**: the chunks already in the chat were cut that way and cannot be re-cut. Drop the flag to carry on, or delete the state file to start a new backup — which leaves the chunks already sent in the chat with nothing pointing at them.
+- Running again **with** a `--chunk-size` that differs from that size makes telstore **refuse to run**: the chunks already in the chat were cut that way and cannot be re-cut. Drop the flag to carry on, or delete the state file to start a new backup — which leaves the chunks already sent in the chat with nothing pointing at them.
 
-`Ctrl-C` during an upload names the backup it was working on, so `telark status` and a later `restore` have something to go on. telark keeps the **20 most recent** unfinished backups in `~/.telark/state/`; starting a new one past that drops the oldest record and says which id it dropped. Only the local record goes — the chunks that backup sent stay in the chat, searchable by that id, but it can no longer be resumed.
+`Ctrl-C` during an upload names the backup it was working on, so `telstore status` and a later `restore` have something to go on. telstore keeps the **20 most recent** unfinished backups in `~/.telstore/state/`; starting a new one past that drops the oldest record and says which id it dropped. Only the local record goes — the chunks that backup sent stay in the chat, searchable by that id, but it can no longer be resumed.
 
 **Restore keeps no state to resume from.** Pressing `Ctrl-C` mid-restore saves nothing — running again starts over.
 
 ## Deleting a backup
 
 ```bash
-npx telark delete telark-20260905-7f3a91
+npx telstore delete telstore-20260905-7f3a91
 ```
 
 It prints what it is about to destroy, asks once, and then removes every chunk message and
@@ -129,14 +129,14 @@ that is usually the one you want gone.
 
 ## Limits worth knowing
 
-- A chunk cannot exceed 1950MB: Telegram accepts at most 4000 parts of 512KB per file, an arithmetic ceiling of about 1953MB, and telark stops at 1950MB to leave a safety margin.
+- A chunk cannot exceed 1950MB: Telegram accepts at most 4000 parts of 512KB per file, an arithmetic ceiling of about 1953MB, and telstore stops at 1950MB to leave a safety margin.
 - The data is **not** encrypted. Don't upload anything you would mind sitting on someone else's infrastructure.
-- Deleting a chunk message on Telegram destroys the backup, with no way to recover it. Use `npx telark delete <backup-id>` when that is what you actually want.
+- Deleting a chunk message on Telegram destroys the backup, with no way to recover it. Use `npx telstore delete <backup-id>` when that is what you actually want.
 - Keep the `backupId`. Without it you have to hunt for the manifest in the chat by hand.
 
 ## Where the config lives
 
-`~/.telark/config.json` (mode 600) holds `apiId`, `apiHash` and the session at the top level, with everything `config` manages under `settings`:
+`~/.telstore/config.json` (mode 600) holds `apiId`, `apiHash` and the session at the top level, with everything `config` manages under `settings`:
 
 ```json
 {
@@ -149,4 +149,4 @@ that is usually the one you want gone.
 
 Editing it by hand is fine, and a value that cannot be used is named on the next run — with the file and the key, never with a flag you did not type.
 
-`npx telark logout` **only deletes the locally stored session** and keeps the rest — the session is still alive on Telegram's side. To revoke access for good, open Telegram → Settings → Devices (Active sessions) and terminate that session.
+`npx telstore logout` **only deletes the locally stored session** and keeps the rest — the session is still alive on Telegram's side. To revoke access for good, open Telegram → Settings → Devices (Active sessions) and terminate that session.

package/bin/{telark.js → telstore.js}

@@ -70,14 +70,14 @@ async function main() {
 
     case 'restore':
       if (!parsed.args[0]) {
-        throw new Error('Missing backup id. Example: npx telark restore telark-20260905-7f3a91')
+        throw new Error('Missing backup id. Example: npx telstore restore telstore-20260905-7f3a91')
       }
       await runRestore(parsed.args[0], parsed.options)
       return
 
     case 'delete':
       if (!parsed.args[0]) {
-        throw new Error('Missing backup id. Example: npx telark delete telark-20260905-7f3a91')
+        throw new Error('Missing backup id. Example: npx telstore delete telstore-20260905-7f3a91')
       }
       await runDelete(parsed.args[0], parsed.options)
       return

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "telstore",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Split large files into chunks and store them on Telegram",
   "keywords": [
     "telegram",
@@ -11,19 +11,19 @@
     "cli",
     "mtproto"
   ],
-  "homepage": "https://github.com/shovity/telark#readme",
+  "homepage": "https://github.com/shovity/telstore#readme",
   "bugs": {
-    "url": "https://github.com/shovity/telark/issues"
+    "url": "https://github.com/shovity/telstore/issues"
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/shovity/telark.git"
+    "url": "git+https://github.com/shovity/telstore.git"
   },
   "type": "module",
   "license": "MIT",
   "author": "shovity",
   "bin": {
-    "telark": "bin/telark.js"
+    "telstore": "bin/telstore.js"
   },
   "files": [
     "bin",
@@ -39,4 +39,4 @@
   "dependencies": {
     "telegram": "^2.26.22"
   }
-}
+}

package/src/caption.js

@@ -8,7 +8,7 @@ const DIVIDER = '━'.repeat(15)
 
 // The hashtag is what `list` searches for, and it lives on the manifest alone: chunk
 // captions stay out of that search so a twelve-chunk backup is one hit, not thirteen.
-export const MANIFEST_TAG = '#telark'
+export const MANIFEST_TAG = '#telstore'
 
 // A file name may legally contain a newline or a tab, and either one would push the
 // rest of the card down a row and take its shape apart.
@@ -32,7 +32,7 @@ export function manifestCaption({ id, name, size, chunks, createdAt }) {
     `🆔 ${id}`,
     `📅 ${utcMinutes(createdAt)}`,
     '',
-    `↩ npx telark restore ${id}`,
+    `↩ npx telstore restore ${id}`,
     MANIFEST_TAG,
   ].join('\n')
 }

package/src/chat.js

@@ -1,4 +1,4 @@
-// How telark talks about a destination. None of this touches Telegram — it is string
+// How telstore talks about a destination. None of this touches Telegram — it is string
 // handling around a target the user typed — so it lives apart from the client that does.
 
 export function normalizeChatTarget(input) {
@@ -17,7 +17,7 @@ export function normalizeChatTarget(input) {
 
 // Telegram's web client addresses a chat by putting the raw target in the fragment, which
 // covers both a negative channel id and an @username. Saved Messages is the exception: it
-// is reached by the account's own id, which telark does not know, so it gets no link
+// is reached by the account's own id, which telstore does not know, so it gets no link
 // rather than a guessed one that lands somewhere else.
 export function chatUrl(chat) {
   const text = String(chat)

package/src/cli.js

@@ -23,22 +23,22 @@ const OPTIONS = {
   help: { type: 'boolean', short: 'h' },
 }
 
-export const HELP = `telark — split large files into chunks and store them on Telegram
+export const HELP = `telstore — split large files into chunks and store them on Telegram
 
 Usage:
-  npx telark login                        Log in to Telegram, only needed once
-  npx telark <file>                       Split a file and upload it to Telegram
-  npx telark list                         List the backups stored in the destination
-  npx telark restore <backup-id>          Download the chunks and reassemble the file
-  npx telark delete <backup-id>           Remove a backup's chunks and manifest from the chat
-  npx telark status                       Show the account, the destination and unfinished backups
-  npx telark config                       Show every setting and where its value comes from
-  npx telark logout                       Remove the saved session
+  npx telstore login                      Log in to Telegram, only needed once
+  npx telstore <file>                     Split a file and upload it to Telegram
+  npx telstore list                       List the backups stored in the destination
+  npx telstore restore <backup-id>        Download the chunks and reassemble the file
+  npx telstore delete <backup-id>         Remove a backup's chunks and manifest from the chat
+  npx telstore status                     Show the account, the destination and unfinished backups
+  npx telstore config                     Show every setting and where its value comes from
+  npx telstore logout                     Remove the saved session
 
 Settings:
-  npx telark config <name>                Print one setting's value
-  npx telark config <name> <value>        Change it for good
-  npx telark config <name> --unset        Drop it and fall back to the default
+  npx telstore config <name>              Print one setting's value
+  npx telstore config <name> <value>      Change it for good
+  npx telstore config <name> --unset      Drop it and fall back to the default
 
   chat          Where backups go: @username, -100123..., or me. No default.
   chunkSize     Size of each chunk, default 1800MB. Examples: 1.8GB, 500MB.
@@ -69,7 +69,7 @@ export function interruptMessage(command, { backupId } = {}) {
 
     return (
       `\n${backup} — run the same command again to continue, ` +
-      'or "npx telark status" to see what is left.\n'
+      'or "npx telstore status" to see what is left.\n'
     )
   }
 
@@ -138,13 +138,13 @@ export function route(argv) {
 
   const [first, ...rest] = positionals
 
-  // `telark --to @chan` with no file used to mean "remember this destination". Flags no
+  // `telstore --to @chan` with no file used to mean "remember this destination". Flags no
   // longer write anything, so that line now asks for a run that has nothing to upload —
   // say where the destination actually lives instead of printing help at someone who was
   // perfectly clear about what they wanted.
   if (first === undefined && values.to && !values.help) {
     throw new Error(
-      `Nothing to upload. To change the destination for good, run "npx telark config chat ${values.to}". ` +
+      `Nothing to upload. To change the destination for good, run "npx telstore config chat ${values.to}". ` +
         'To use it for one run, pass --to alongside a file or a command.',
     )
   }

package/src/client.js

@@ -22,7 +22,7 @@ export function documentFileName(message) {
   return named?.fileName ?? null
 }
 
-// The one place telark searches a chat. Both callers want documents and nothing else,
+// The one place telstore searches a chat. Both callers want documents and nothing else,
 // and getMessages is preferred over a raw Api.messages.Search because it handles offsets,
 // hashes and pagination itself, so we don't hand-build easily mistyped fields. The raw
 // message is kept alongside the flat fields because downloading needs it whole.
@@ -42,9 +42,9 @@ export async function searchDocuments(client, peer, { search, limit }) {
   }))
 }
 
-// How telark finds a backup's manifest, in one place because restore and delete must not
+// How telstore finds a backup's manifest, in one place because restore and delete must not
 // disagree about it. The search is by backup id, but the answer is decided by the file name
-// telark itself wrote — a caption is text a person can edit, a file name is not.
+// telstore itself wrote — a caption is text a person can edit, a file name is not.
 export async function findManifestMessage(client, peer, backupId) {
   const wanted = manifestFileName(backupId)
   const found = await searchDocuments(client, peer, { search: backupId, limit: 100 })
@@ -56,7 +56,7 @@ export async function readMessageBytes(client, message) {
   return await client.downloadMedia(message)
 }
 
-// The one place telark removes messages from a chat, and the mirror of searchDocuments
+// The one place telstore removes messages from a chat, and the mirror of searchDocuments
 // above. GramJS has its own deleteMessages, and it is the right thing to call — it resolves
 // the peer and picks between channels.DeleteMessages and messages.DeleteMessages, which is
 // exactly the choice a fake client would never catch us getting wrong.
@@ -64,7 +64,7 @@ export async function readMessageBytes(client, message) {
 // What it does on top of that is the problem: it splits the ids into batches of a hundred
 // and fires every batch at once through Promise.all. A ten-thousand-chunk backup would put
 // a hundred requests in flight together, none of them under the retry policy or the stall
-// deadline that every other network wait in telark carries. Batching here instead keeps
+// deadline that every other network wait in telstore carries. Batching here instead keeps
 // one request outstanding at a time, under both.
 //
 // Telegram does not complain about an id that is no longer there, so sending a batch twice
@@ -123,7 +123,7 @@ export async function closeQuietly(client, disconnect, onWarn) {
 
 export function assertLoggedIn(config) {
   if (!config.session || !config.apiId || !config.apiHash) {
-    throw new Error('Not logged in — run "npx telark login" first.')
+    throw new Error('Not logged in — run "npx telstore login" first.')
   }
 }
 
@@ -139,7 +139,7 @@ export async function connect(config, { verbose = false } = {}) {
   await client.connect()
 
   if (!(await client.isUserAuthorized())) {
-    throw new Error('Session expired — run "npx telark login".')
+    throw new Error('Session expired — run "npx telstore login".')
   }
 
   return client

package/src/commands/config.js

@@ -12,7 +12,7 @@ const GAP = '  '
 function unknownKey(name) {
   if (isManagedByLogin(name)) {
     return new Error(
-      `"${name}" is managed by "npx telark login", not by config. ` +
+      `"${name}" is managed by "npx telstore login", not by config. ` +
         `Settings you can change: ${SETTING_KEYS.join(', ')}.`,
     )
   }
@@ -37,7 +37,7 @@ function listLines(values, source, stored) {
     return [key, `${spec.format(value)}${note}`, source(key) === 'settings' ? '' : '(default)']
   })
 
-  // Keys telark does not know are left in the file untouched, but a value that silently
+  // Keys telstore does not know are left in the file untouched, but a value that silently
   // does nothing is worse than one that is refused: show them, so a typo is visible from
   // the command rather than only from opening the file that also holds the session.
   const strays = Object.keys(stored).filter((key) => !SETTING_KEYS.includes(key))
@@ -50,8 +50,8 @@ function listLines(values, source, stored) {
   if (strays.length > 0) {
     lines.push('')
     lines.push(
-      `Ignored, telark does not know these: ${strays.join(', ')}. ` +
-        'Remove one with: npx telark config <name> --unset',
+      `Ignored, telstore does not know these: ${strays.join(', ')}. ` +
+        'Remove one with: npx telstore config <name> --unset',
     )
   }
 
@@ -65,21 +65,21 @@ export async function runConfig(args = [], options = {}, deps = {}) {
   if (extra.length > 0) {
     throw new Error(
       `Too many arguments: a setting takes one value, but got ${args.length}. ` +
-        `Did you mean: npx telark config ${name} "${[value, ...extra].join(' ')}"`,
+        `Did you mean: npx telstore config ${name} "${[value, ...extra].join(' ')}"`,
     )
   }
 
   // Both of these would otherwise be obeyed halfway and reported as a success: a listing
   // that quietly dropped the --unset, or an unset that quietly dropped the value beside it.
   if (options.unset && name === undefined) {
-    throw new Error('--unset needs the setting to drop. Try: npx telark config chat --unset')
+    throw new Error('--unset needs the setting to drop. Try: npx telstore config chat --unset')
   }
 
   if (options.unset && value !== undefined) {
     throw new Error(
       `--unset takes no value, but "${value}" was given. ` +
-        `Use "npx telark config ${name} --unset" to drop it, ` +
-        `or "npx telark config ${name} ${value}" to set it.`,
+        `Use "npx telstore config ${name} --unset" to drop it, ` +
+        `or "npx telstore config ${name} ${value}" to set it.`,
     )
   }
 

package/src/commands/delete.js

@@ -56,7 +56,7 @@ function stateMessageIds(record) {
         throw new Error(
           `The record of unfinished backup ${record.state.id} gives ` +
             `${JSON.stringify(msgId)} as the message id of chunk ${Number(index) + 1}, which ` +
-            `is not a message id. ${record.file} is damaged, so telark is not deleting ` +
+            `is not a message id. ${record.file} is damaged, so telstore is not deleting ` +
             'anything.',
         )
       }
@@ -106,7 +106,7 @@ export async function runDelete(backupId, options = {}, deps = {}) {
   if (records.length > 1) {
     throw new Error(
       `Two local records both claim to be backup ${backupId}: ` +
-        `${records.map((r) => r.file).join(' and ')}. telark will not guess which one to ` +
+        `${records.map((r) => r.file).join(' and ')}. telstore will not guess which one to ` +
         'drop — remove the wrong one by hand and run again.',
     )
   }
@@ -120,7 +120,7 @@ export async function runDelete(backupId, options = {}, deps = {}) {
     if (!manifestMessage && !record) {
       throw new Error(
         `No backup ${backupId} found in ${chatName(chat)}, and no unfinished record of it on ` +
-          'this machine. Check the id with "npx telark list", or use --to to point at the ' +
+          'this machine. Check the id with "npx telstore list", or use --to to point at the ' +
           'right chat.',
       )
     }
@@ -131,7 +131,7 @@ export async function runDelete(backupId, options = {}, deps = {}) {
     if (manifestMessage) {
       manifest = parseManifestJson(await readMessageBytes(client, manifestMessage))
 
-      // The manifest was found by the file name telark itself wrote, and that name is the
+      // The manifest was found by the file name telstore itself wrote, and that name is the
       // id this command was asked about. A body naming a different backup is a file that was
       // renamed or replaced, and its message ids point at somebody else's chunks — the one
       // mistake in this whole command that nothing can undo.
@@ -139,7 +139,7 @@ export async function runDelete(backupId, options = {}, deps = {}) {
         throw new Error(
           `The manifest named ${manifestFileName(backupId)} describes backup ` +
             `${JSON.stringify(manifest.id)}, not ${backupId}. Its message ids point at ` +
-            'another backup\'s chunks, so telark is not deleting anything.',
+            'another backup\'s chunks, so telstore is not deleting anything.',
         )
       }
 

package/src/commands/list.js

@@ -36,7 +36,7 @@ function utcDay(unixSeconds) {
 }
 
 // The card is text in a chat, which means a person can edit or predate it. The id is the
-// one field restore cannot be wrong about, so it always comes from the file name telark
+// one field restore cannot be wrong about, so it always comes from the file name telstore
 // wrote; the caption only decorates. A card that cannot be read back leaves the rest
 // unknown, because inventing it would describe a backup that does not exist.
 function toRow(message) {
@@ -106,14 +106,14 @@ export async function runList(options = {}, deps = {}) {
     .map(toRow)
 
   if (rows.length === 0) {
-    log(`No backups found in ${chatName(chat)}. Upload one with: npx telark <file>`)
+    log(`No backups found in ${chatName(chat)}. Upload one with: npx telstore <file>`)
     return rows
   }
 
   for (const line of renderTable(rows)) log(line)
 
   log('')
-  log(`${rows.length} backup${rows.length === 1 ? '' : 's'}. Restore with: npx telark restore <backup-id>`)
+  log(`${rows.length} backup${rows.length === 1 ? '' : 's'}. Restore with: npx telstore restore <backup-id>`)
 
   return rows
 }

package/src/commands/restore.js

@@ -78,7 +78,7 @@ export async function runRestore(backupId, options = {}, deps = {}) {
     if (delayMs > LONG_WAIT_MS) {
       warn(
         `\nTelegram wants ${formatDuration(delayMs / 1000)} of waiting before the next part ` +
-          `(${err.message}). telark is waiting and will carry on by itself, leave it running.\n`,
+          `(${err.message}). telstore is waiting and will carry on by itself, leave it running.\n`,
       )
       return
     }
@@ -112,7 +112,7 @@ export async function runRestore(backupId, options = {}, deps = {}) {
     const partial = `${target}.partial`
 
     // Only ENOENT means "no file yet". Treating a permission or I/O error as absence
-    // would have telark overwrite the user's file without asking.
+    // would have telstore overwrite the user's file without asking.
     let exists = true
     try {
       await fs.stat(target)

package/src/commands/status.js

@@ -78,7 +78,7 @@ export async function runStatus(options = {}, deps = {}) {
       'Destination',
       settingsError ??
         (settings.chat === null
-          ? 'none set — run "npx telark config chat @my_backups" to set one'
+          ? 'none set — run "npx telstore config chat @my_backups" to set one'
           : describeChat(settings.chat)),
     ),
   )

package/src/commands/upload.js

@@ -103,7 +103,7 @@ export async function runUpload(filePath, options = {}, deps = {}) {
 
   // The chunks already in the chat were cut at the size this backup started with, and
   // nothing can re-cut them. Carrying on at a different size would abandon every one of
-  // them in the chat, where telark can no longer find them — so an unfinished backup
+  // them in the chat, where telstore can no longer find them — so an unfinished backup
   // keeps its own chunk size, and a flag that disagrees is refused rather than obeyed.
   //
   // Only a flag is a disagreement. A configured chunkSize says what to use when nobody asks
@@ -164,10 +164,10 @@ export async function runUpload(filePath, options = {}, deps = {}) {
 
     // Only a new backup adds to the directory, so this is the one place it can grow.
     // The report goes out even when the caller asked for silence: this is not narration
-    // about a transfer, it is telark dropping the only record of someone else's chunks.
+    // about a transfer, it is telstore dropping the only record of someone else's chunks.
     for (const gone of await pruneStates(configDir)) {
       writeErr(
-        `\nDropped the record of unfinished backup ${gone.id}: telark keeps the ` +
+        `\nDropped the record of unfinished backup ${gone.id}: telstore keeps the ` +
           `${MAX_STATES} most recent. The chunks it sent are still in ${gone.chat}, ` +
           'searchable by that id, but that backup can no longer be resumed.\n',
       )
@@ -185,7 +185,7 @@ export async function runUpload(filePath, options = {}, deps = {}) {
     if (delayMs > LONG_WAIT_MS) {
       warn(
         `\nTelegram wants ${formatDuration(delayMs / 1000)} of waiting before the next send ` +
-          `(${err.message}). telark is waiting and will carry on by itself, leave it running.\n`,
+          `(${err.message}). telstore is waiting and will carry on by itself, leave it running.\n`,
       )
       return
     }
@@ -289,7 +289,7 @@ export async function runUpload(filePath, options = {}, deps = {}) {
       throw new Error(
         `${absPath} changed during the upload ` +
           `(size ${stat.size} → ${after.size}, mtime ${stat.mtimeMs} → ${after.mtimeMs}). ` +
-          'This backup mixes old and new data and cannot be trusted — telark is not sending the manifest. ' +
+          'This backup mixes old and new data and cannot be trusted — telstore is not sending the manifest. ' +
           'Wait until the file settles, then run again to create a new backup.',
       )
     }
@@ -316,7 +316,7 @@ export async function runUpload(filePath, options = {}, deps = {}) {
 
     await clearState(key, configDir)
 
-    log(`\nDone. Restore with:\n  npx telark restore ${state.id}`)
+    log(`\nDone. Restore with:\n  npx telstore restore ${state.id}`)
 
     return { id: state.id, chunks: chunks.length }
   } finally {

package/src/config.js

@@ -5,7 +5,7 @@ import path from 'node:path'
 const FILE_NAME = 'config.json'
 
 export function defaultConfigDir() {
-  return path.join(os.homedir(), '.telark')
+  return path.join(os.homedir(), '.telstore')
 }
 
 export function configFile(dir = defaultConfigDir()) {
@@ -19,7 +19,7 @@ function isPlainObject(value) {
 // `config.json` is hand-editable now that the `config` command invites people into it,
 // which puts it in the same category as a manifest or a state file: believed only after it
 // has been checked. A `settings` that is not an object would make every lookup below it
-// return undefined, and telark would then run happily on built-in defaults while the
+// return undefined, and telstore would then run happily on built-in defaults while the
 // user's own choices sat there ignored — so it is named and refused instead.
 export function checkConfigShape(raw, file) {
   if (!isPlainObject(raw)) {
@@ -32,7 +32,7 @@ export function checkConfigShape(raw, file) {
   if (raw.settings !== undefined && !isPlainObject(raw.settings)) {
     throw new Error(
       `"settings" in ${file} holds ${Array.isArray(raw.settings) ? 'a list' : typeof raw.settings}, ` +
-        'not a group of settings. telark will not guess what was meant — fix that entry, ' +
+        'not a group of settings. telstore will not guess what was meant — fix that entry, ' +
         'or remove it to fall back to the defaults.',
     )
   }
@@ -57,7 +57,7 @@ export async function loadConfig(dir = defaultConfigDir()) {
   } catch (err) {
     throw new Error(
       `Corrupt config file: ${file} is not valid JSON (${err.message}). ` +
-        'Fix the syntax to keep your session, or delete the file and run "telark login" again.',
+        'Fix the syntax to keep your session, or delete the file and run "telstore login" again.',
     )
   }
 

package/src/manifest.js

@@ -8,7 +8,7 @@ export function newBackupId(now = new Date(), randomHex = () => randomBytes(3).t
   const yyyy = now.getUTCFullYear()
   const mm = String(now.getUTCMonth() + 1).padStart(2, '0')
   const dd = String(now.getUTCDate()).padStart(2, '0')
-  return `telark-${yyyy}${mm}${dd}-${randomHex()}`
+  return `telstore-${yyyy}${mm}${dd}-${randomHex()}`
 }
 
 export function chunkFileName(id, i) {
@@ -72,7 +72,7 @@ export function manifestMessageIds(manifest) {
       throw new Error(
         `Manifest gives ${JSON.stringify(msgId)} as the message id of chunk ${index + 1}, ` +
           'which is not a message id. Deleting from this manifest could remove the wrong ' +
-          'messages, so telark is not deleting anything.',
+          'messages, so telstore is not deleting anything.',
       )
     }
 
@@ -85,7 +85,7 @@ export function parseManifest(input) {
 
   if (manifest.v !== MANIFEST_VERSION) {
     throw new Error(
-      `Manifest uses version ${manifest.v}, this build of telark only understands version ${MANIFEST_VERSION}.`,
+      `Manifest uses version ${manifest.v}, this build of telstore only understands version ${MANIFEST_VERSION}.`,
     )
   }
 
@@ -147,7 +147,7 @@ export function parseManifest(input) {
   // uniform: every chunk is chunkSize, except the last one which is the remainder.
   // A correct total with individually wrong sizes yields a file with a hole or
   // extra length while every per-chunk sha256 still matches — silently wrong data,
-  // precisely what telark must never produce.
+  // precisely what telstore must never produce.
   manifest.chunks.forEach((chunk, index) => {
     const expected = Math.min(manifest.chunkSize, manifest.size - index * manifest.chunkSize)
     if (chunk.size !== expected) {

package/src/settings.js

@@ -9,7 +9,7 @@ import { formatBytes } from './progress.js'
 
 export const DEFAULT_LIMIT = 20
 
-// The three keys telark writes for itself. Naming them separately is what lets the
+// The three keys telstore writes for itself. Naming them separately is what lets the
 // unknown-key error say "managed by login" instead of listing a session as something the
 // user forgot to spell correctly.
 const MANAGED_BY_LOGIN = new Set(['session', 'apiId', 'apiHash'])
@@ -181,7 +181,7 @@ export function resolveSettings(options = {}, config = {}, { file = 'the config
 export function requireChat(values) {
   if (values.chat === null || values.chat === undefined) {
     throw new Error(
-      'No destination set — run "npx telark config chat @my_backups" to set one ' +
+      'No destination set — run "npx telstore config chat @my_backups" to set one ' +
         '("config chat me" for Saved Messages), or pass --to to choose one for this run.',
     )
   }

package/src/state.js

@@ -120,11 +120,11 @@ export async function listStates(configDir = defaultConfigDir()) {
 // delete needs the file a record came from, not just its contents — and the name of that
 // file is a hash of the path, size and mtime *inside* the record, so recomputing it would
 // be trusting an untrusted file to say where it lives. A hand-edited path yields a key that
-// names no file at all, clearState ignores a file that is not there, and telark reports a
+// names no file at all, clearState ignores a file that is not there, and telstore reports a
 // record dropped that is still sitting on disk. Matching the id inside each file is the one
 // way that cannot point at the wrong one.
 //
-// Every record claiming the id is returned rather than the first: two of them means telark
+// Every record claiming the id is returned rather than the first: two of them means telstore
 // cannot know which to drop, and that is the caller's decision to refuse, not ours to make
 // by picking one.
 export async function findStates(backupId, configDir = defaultConfigDir()) {

package/src/uploader.js

@@ -13,7 +13,7 @@ const read = promisify(readCallback)
 
 // Telegram splits its upload API by file size: only files above 10MB may use the
 // "big" family. GramJS picks the same threshold (LARGE_FILE_THRESHOLD in
-// node_modules/telegram/client/uploads.js), and telark follows it.
+// node_modules/telegram/client/uploads.js), and telstore follows it.
 export const LARGE_FILE_THRESHOLD = 10 * 1024 * 1024
 
 async function readExactly(fd, length, position) {