Choose a new name for the app and rename it before 1.0 #272

Open
opened 2026-10-30 11:42:32 -05:00 by ethan-hann · 0 comments
Owner

SavePoint is hard to find under its name, and the name undersells the app. This issue tracks choosing a new name (owner's decision) and, once chosen, renaming the app before 1.0, when it is cheapest. Not an autonomous task: nothing is renamed until the owner picks a name.

Why (checked 2026-10-28)

  • 370 GitHub repos have "savepoint" in the name; searches for "savepoint github" or "savepoint app game mods" return SQL SAVEPOINT docs, a Claude Code snapshot plugin, a PEAK mod and a GTA mod named SavePoint, and two iOS apps, not this project.

  • savepoint.com (2005) and savepoint.app (2026-06) are registered.

  • US trademark SAVEPOINT, Reg. No. 8433363, class 9 (personal financial management software), registered 2026-09-15 (USPTO TSDR serial 99664733); a pending SAVEPOINT application in classes 9/42 was seen on Trademarkia only. Same word and class, unrelated goods: a question for counsel.

  • "SavePoint" sounds like a save-file backup tool. The app keeps whole game states (version, mods and saves) and switches between them; mods are a side effect, so the name must not imply a mod manager.

What a good name needs: searchable (" github", " mod" and " app" find only this project), says or hints at the job (several states of the same game, going back), easy to say and spell, not a mod-manager name, and free on GitHub, Nexus, Steam, Flathub, winget and Scoop, with a usable domain and no conflicting software trademark.

Already ruled out

  • Mod-prefixed names (ModStash, ModKeep, ModAnchor, ModShelf, ModSnap): the owner rejects them, since the app is not a mod manager.

  • PatchLock: a live Deadlock patch tracker uses the name on patchlock.app.

  • Savault: two live software products use it (a design-tools directory with a Chrome extension, and a Windows save-to-notes app); savault.app registered 2026-07.

  • Snaptych and Timecask: both .com and .app registered in 2026. Savewarp: "save warping" is a known Source-engine speedrun glitch. Splitsave: student finance apps. Keepsnap, Savyr: domains taken. Backpoint passes the checks but is bland and easy to confuse with "backup".

  • Also crowded or taken: Quicksave, Checkpoint, Keepsake, Rewind, Rewynd, Chronark, Snapvault (NetApp), Snappoint (Microsoft), Revault, GameVault, Holdfast, Mulligan.

  • Lesson from two rounds: freshly coined names often have their domains registered already, so check RDAP before falling for one.

Next angle to try: names built on "several versions of the same game side by side" (parallel states, alternate timelines, layers), which is closest to what the app does.

How to vet a candidate: gh api search/repositories -f q="<name> in:name" (single word, not hyphenated), winget search, the Flathub appstream list, the Steam storesearch API, RDAP for .com (rdap.verisign.com) and .app (pubapi.registry.google; 200 means registered), Nexus and AUR by web search, and a trademark search in classes 9 and 42.

What the rename touches (inventory 2026-10-28; about 8,760 mentions in tracked files, most of them mechanical)

  • Names stored inside every user's snapshot history: the refs/savepoint/removed/ ref namespace, Savepoint-Captured-At and Savepoint-Empty-Folders trailers, the SavePoint: keep-text prefix, savepoint@localhost author, and marker or journal files (.savepoint-empty-start, savepoint-switch.json, savepoint-free-up.json, savepoint-reclaim.json, savepoint-move-in-progress.txt). Keep these as they are, or read both spellings; never break existing history.

  • User data folders: Windows %APPDATA%\SavePoint and %LOCALAPPDATA%\SavePoint Data; Linux ~/.config/savepoint, ~/.local/share/savepoint, ~/.local/state/savepoint; macOS ~/Library/Application Support/SavePoint. Only Windows has folder-migration code; Linux and macOS would open empty without a move.

  • Install identity: the Velopack pack id SavePoint (Directory.Build.props), the exe name (AssemblyName), asset names, the Windows setup folder, the single-instance id, the window class, the Linux desktop entry and its markers. A new pack id is a second install with no update path (D38), and the setup empties %LOCALAPPDATA%\<pack id>, so the new id must never name a data folder. Changing AssemblyName breaks every avares://SavePoint/ URI.

  • Text and docs: 240 catalog strings, docs/ (437 mentions in 7 guides), all 11 screenshots in docs/images, README and other root files, agent docs, docfx.json and the docs site path. docs.tortal.tech// maps to the repo name through the proxy (D55), so a repo rename needs a proxy change; Forgejo and GitHub redirect old repo URLs.

  • Code identifiers: projects, namespaces and the solution (Savepoint.Core, Savepoint.App, Savepoint.slnx), test projects, MSBuild targets, icons.

When a name is chosen: record it as the next numbered decision in docs/decisions.md, then plan the rename as its own batch: data-folder migration on every OS, a bridge for the old install id, dual-reading or keeping the in-history names, the docs site and repo rename, and regenerated screenshots.

SavePoint is hard to find under its name, and the name undersells the app. This issue tracks choosing a new name (owner's decision) and, once chosen, renaming the app before 1.0, when it is cheapest. Not an autonomous task: nothing is renamed until the owner picks a name. **Why** (checked 2026-10-28) - 370 GitHub repos have "savepoint" in the name; searches for "savepoint github" or "savepoint app game mods" return SQL SAVEPOINT docs, a Claude Code snapshot plugin, a PEAK mod and a GTA mod named SavePoint, and two iOS apps, not this project. - savepoint.com (2005) and savepoint.app (2026-06) are registered. - US trademark SAVEPOINT, Reg. No. 8433363, class 9 (personal financial management software), registered 2026-09-15 (USPTO TSDR serial 99664733); a pending SAVEPOINT application in classes 9/42 was seen on Trademarkia only. Same word and class, unrelated goods: a question for counsel. - "SavePoint" sounds like a save-file backup tool. The app keeps whole game states (version, mods and saves) and switches between them; mods are a side effect, so the name must not imply a mod manager. **What a good name needs:** searchable ("<name> github", "<name> mod" and "<name> app" find only this project), says or hints at the job (several states of the same game, going back), easy to say and spell, not a mod-manager name, and free on GitHub, Nexus, Steam, Flathub, winget and Scoop, with a usable domain and no conflicting software trademark. **Already ruled out** - Mod-prefixed names (ModStash, ModKeep, ModAnchor, ModShelf, ModSnap): the owner rejects them, since the app is not a mod manager. - PatchLock: a live Deadlock patch tracker uses the name on patchlock.app. - Savault: two live software products use it (a design-tools directory with a Chrome extension, and a Windows save-to-notes app); savault.app registered 2026-07. - Snaptych and Timecask: both .com and .app registered in 2026. Savewarp: "save warping" is a known Source-engine speedrun glitch. Splitsave: student finance apps. Keepsnap, Savyr: domains taken. Backpoint passes the checks but is bland and easy to confuse with "backup". - Also crowded or taken: Quicksave, Checkpoint, Keepsake, Rewind, Rewynd, Chronark, Snapvault (NetApp), Snappoint (Microsoft), Revault, GameVault, Holdfast, Mulligan. - Lesson from two rounds: freshly coined names often have their domains registered already, so check RDAP before falling for one. **Next angle to try:** names built on "several versions of the same game side by side" (parallel states, alternate timelines, layers), which is closest to what the app does. **How to vet a candidate:** `gh api search/repositories -f q="<name> in:name"` (single word, not hyphenated), `winget search`, the Flathub appstream list, the Steam storesearch API, RDAP for .com (rdap.verisign.com) and .app (pubapi.registry.google; 200 means registered), Nexus and AUR by web search, and a trademark search in classes 9 and 42. **What the rename touches** (inventory 2026-10-28; about 8,760 mentions in tracked files, most of them mechanical) - Names stored inside every user's snapshot history: the `refs/savepoint/removed/` ref namespace, `Savepoint-Captured-At` and `Savepoint-Empty-Folders` trailers, the `SavePoint:` keep-text prefix, `savepoint@localhost` author, and marker or journal files (`.savepoint-empty-start`, `savepoint-switch.json`, `savepoint-free-up.json`, `savepoint-reclaim.json`, `savepoint-move-in-progress.txt`). Keep these as they are, or read both spellings; never break existing history. - User data folders: Windows `%APPDATA%\SavePoint` and `%LOCALAPPDATA%\SavePoint Data`; Linux `~/.config/savepoint`, `~/.local/share/savepoint`, `~/.local/state/savepoint`; macOS `~/Library/Application Support/SavePoint`. Only Windows has folder-migration code; Linux and macOS would open empty without a move. - Install identity: the Velopack pack id `SavePoint` (Directory.Build.props), the exe name (AssemblyName), asset names, the Windows setup folder, the single-instance id, the window class, the Linux desktop entry and its markers. A new pack id is a second install with no update path (D38), and the setup empties `%LOCALAPPDATA%\<pack id>`, so the new id must never name a data folder. Changing AssemblyName breaks every `avares://SavePoint/` URI. - Text and docs: 240 catalog strings, docs/ (437 mentions in 7 guides), all 11 screenshots in docs/images, README and other root files, agent docs, docfx.json and the docs site path. docs.tortal.tech/<name>/ maps to the repo name through the proxy (D55), so a repo rename needs a proxy change; Forgejo and GitHub redirect old repo URLs. - Code identifiers: projects, namespaces and the solution (Savepoint.Core, Savepoint.App, Savepoint.slnx), test projects, MSBuild targets, icons. **When a name is chosen:** record it as the next numbered decision in docs/decisions.md, then plan the rename as its own batch: data-folder migration on every OS, a bridge for the old install id, dual-reading or keeping the in-history names, the docs site and repo rename, and regenerated screenshots.
ethan-hann added this to the 1.0 milestone 2026-10-30 11:42:32 -05:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#272
No description provided.