diff --git a/CLAUDE.md b/CLAUDE.md index f00c566..388c1a2 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -18,9 +18,9 @@ at launch (via symlink/junction, with a copy fallback). See [docs/](docs/): Beyond the MVP management layer above: -- **Browse tab** — the SiloAPI canonical catalog (GitHub + ModHub + Nexus), search, +- **Browse tab** — the SiloAPI canonical catalog (GitHub + ModHub), search, category filter, pagination, per-source buttons w/ versions, in-app GitHub install - with a streaming progress bar, detail drawer. ModHub/Nexus are index-only + with a streaming progress bar, detail drawer. ModHub is index-only (open-page; their CDNs gate direct download). - **Catalog-routed updates** — "⟳ Updates" checks the whole library against the catalog's latest-across-sources (fixes the GitHub-vs-ModHub false-"outdated" bug); diff --git a/docs/social/VIDEO_PLAN.md b/docs/social/VIDEO_PLAN.md index 94dd38e..44ffbc8 100644 --- a/docs/social/VIDEO_PLAN.md +++ b/docs/social/VIDEO_PLAN.md @@ -46,7 +46,7 @@ from this set — you should almost never re-shoot. | V4 | **Organize dry-run** | The read-only preview ("12 into Vehicles, 3 into Maps") before anything moves. | | V5 | **Conflicts** | A real one from your set — duplicate active map (instant-crash) or a filltype/script collision. | | V6 | **Provenance / integrity** | A mod's drawer → integrity check → **✓ Verified** (and a **Modified** with changed files if you have one). | -| V7 | **Browse one catalog** | Search a mod; show ModHub/GitHub/Nexus folded into one record with the latest version; a GitHub in-app install with the progress bar. | +| V7 | **Browse one catalog** | Search a mod; show ModHub/GitHub folded into one record with the latest version; a GitHub in-app install with the progress bar. | | V8 | **Update by drop → Adopt** | Drop a newer ModHub `.zip` into the folder; open the mod; the drawer's "newer build — Adopt vX" banner; adopt; version updates. | | V9 | **Loadouts** | Save the current set; switch to another; watch the active set change. | | V10 | **Collections** | Publish the active set as a link (secret gist); open a shared link and show the preview + "heads-up" (what you'd need to install). | @@ -67,7 +67,7 @@ The old [`demo-video-script.md`](./demo-video-script.md) was written ~2026-07-31 - **Collections** (V10) — share a mod-set as a *link* (secret gist or public repo), with an import preview that tells you what you'd need. The "here's my co-op pack / the server's list" story. Missing entirely from the old script. -- **Update by drop → Adopt** (V8) — the real ModHub/Nexus update flow: drop the new zip, Silo says +- **Update by drop → Adopt** (V8) — the real ModHub update flow: drop the new zip, Silo says "newer build — Adopt," done. Very demo-able; add to the "keeps mods current" beat. - **Tile UI + green active switch** (V3) — the old script says "click the dot." Visuals changed; re-shoot those beats. diff --git a/docs/social/demo-video-script.md b/docs/social/demo-video-script.md index e50afd7..1978262 100644 --- a/docs/social/demo-video-script.md +++ b/docs/social/demo-video-script.md @@ -78,16 +78,16 @@ A follow-along beat sheet for a **narrated screen-share** on your own machine (y against the real build its source published. Verified means byte-for-byte the same. Modified tells you exactly which files differ." - "It's provenance, not antivirus — it proves *what* a mod is, it doesn't guess intent. And it - works across ModHub, GitHub, and Nexus." + works across ModHub and GitHub." ### 6 · One catalog, every source — and easy updates (6:30–7:45) -- **DO:** Open **Browse**. Search a mod. Show it pulling ModHub/GitHub/Nexus into one record with the +- **DO:** Open **Browse**. Search a mod. Show it pulling ModHub/GitHub into one record with the latest version. If it's a GitHub mod, show the in-app install with the progress bar. Then show the **update-by-drop** flow: with a mod out of date, drop the newer `.zip` into your folder, open the mod, and hit the drawer's **⬆ Adopt** banner. - **SAY:** - - "A mod might live on ModHub, get newer builds on GitHub, and a mirror on Nexus. Silo pulls them - into one record so you actually see the latest version across all three — not whichever site + - "A mod might live on ModHub, get newer builds on GitHub. Silo pulls them + into one record so you actually see the latest version across both — not whichever site updated last." - "ModHub won't let anyone download for you, so you grab the zip and drop it in — and Silo notices it's a newer build and offers to adopt it in one click. That's the whole update, done." diff --git a/docs/social/video-showcase-script.md b/docs/social/video-showcase-script.md index 7177349..d274a98 100644 --- a/docs/social/video-showcase-script.md +++ b/docs/social/video-showcase-script.md @@ -44,12 +44,12 @@ changed files if you have one). > "Here's the part I haven't seen anywhere else. Silo hashes your installed mod and checks it against > the real build its source published. Verified means byte-for-byte identical. Modified tells you > exactly which files differ. It's provenance, not antivirus — it proves *what* a mod is, and it -> works across ModHub, GitHub, and Nexus." +> works across ModHub and GitHub." ### 2:00–2:30 · One catalog, every source + updates *(V7, V8)* -`[SHOW]` **Browse**; search a mod; the merged ModHub/GitHub/Nexus record with the latest version. Then +`[SHOW]` **Browse**; search a mod; the merged ModHub/GitHub record with the latest version. Then quick: drop a new zip in → the mod drawer's **Adopt** banner. -> "A mod might live on ModHub, get newer builds on GitHub, and mirror on Nexus. Silo folds them into +> "A mod might live on ModHub, get newer builds on GitHub. Silo folds them into > one record so you see the actual latest — not whichever site updated last. And when you drop a new > version in to update, Silo spots it and offers to adopt it in a click." diff --git a/landing/browse/index.html b/landing/browse/index.html index a1f12b0..e7b4fa1 100644 --- a/landing/browse/index.html +++ b/landing/browse/index.html @@ -5,9 +5,9 @@
Loading the catalog… - aggregated from ModHub, GitHub and Nexus into one searchable record each. + aggregated from ModHub and GitHub into one searchable record each. Every mod links back to its original source — Silo indexes, it doesn't host.
@@ -317,7 +316,7 @@The Browse tab is where you find new mods without leaving Silo. It reads the SiloAPI catalog, a single index that merges the same mod across GitHub, ModHub, and Nexus Mods, so you see one card per mod instead of three scattered listings. The header shows how many mods and sources the catalog currently holds.
+The Browse tab is where you find new mods without leaving Silo. It reads the SiloAPI catalog, a single index that merges the same mod across GitHub and ModHub, so you see one card per mod instead of scattered listings. The header shows how many mods and sources the catalog currently holds.
Any mod you already have shows an In library badge, so you can tell at a glance what is new.
Each card carries one button per source the mod lives on — GH, MH, Nexus — each labelled with that source's own version, because those versions drift apart. A download arrow (⬇) means Silo can install it for you; an up-right arrow (↗) means the button opens the source's page instead.
Each card carries one button per source the mod lives on — GH, MH — each labelled with that source's own version, because those versions drift apart. A download arrow (⬇) means Silo can install it for you; an up-right arrow (↗) means the button opens the source's page instead.
GitHub release mods are directly installable. Click the GitHub button (or Install ⬇ in the detail drawer) and Silo downloads the .zip straight into your mods folder, showing a live progress bar with the megabytes transferred. When it finishes you'll see Installed … and the library rescans automatically. You do not need to connect a GitHub account just to install — connecting is only for Star/Watch actions.
Installing only adds a new .zip to your mods folder; it never edits or removes anything you already have. To undo an install, remove that mod from your library like any other.
-Silo can list ModHub and Nexus mods but cannot download them for you — those CDNs require the download to go through their own website. Their buttons read Open page ↗ and take you to the source. Grab the .zip there, drop it in your mods folder, and Silo files a new mod automatically on the next scan. If you're updating a mod you already manage — dropping the newer .zip over Silo's copy — Silo notices the newer build and offers to adopt it; see Applying an update.
Silo can list ModHub mods but cannot download them for you — its CDN requires the download to go through the ModHub website. The button reads Open page ↗ and takes you to the source. Grab the .zip there, drop it in your mods folder, and Silo files a new mod automatically on the next scan. If you're updating a mod you already manage — dropping the newer .zip over Silo's copy — Silo notices the newer build and offers to adopt it; see Applying an update.
Click anywhere on a card to open a side drawer with the cover image, author, version, category, tech name, rating and downloads, and the full Available from source list. For a GitHub source it also shows live repo stats (stars, forks, watchers, issues) and, once you connect GitHub, Star and Watch buttons. Use Read more → to expand the full description.
@@ -327,7 +327,7 @@Two things happen behind the scenes:
Where a downloadable asset exists, click Install in the Updates panel (or Download & install in the drawer). Silo downloads the new archive, verifies it is a valid, complete .zip, backs up your current file, and only then writes the new version in place. Afterward it rescans so your library reflects the new version.
Safety: Silo will not overwrite your file until the download is validated and a backup is made. If the write fails partway, it restores the original from that backup, so you're never left with a broken mod. Mods indexed as open-page only (typical for ModHub and Nexus) have no direct-download asset — for those, update by drop-in, below.+
Safety: Silo will not overwrite your file until the download is validated and a backup is made. If the write fails partway, it restores the original from that backup, so you're never left with a broken mod. Mods indexed as open-page only (typical for ModHub) have no direct-download asset — for those, update by drop-in, below.-
ModHub and Nexus don't allow direct download, so you update those the manual way: on the source page, download the new .zip and save it into your mods/ folder, replacing the file that's there. Silo sees that the file no longer matches its managed copy and, rather than silently trusting or discarding it, surfaces it as something to reconcile.
ModHub doesn't allow direct download, so you update those the manual way: on the mod's page, download the new .zip and save it into your mods/ folder, replacing the file that's there. Silo sees that the file no longer matches its managed copy and, rather than silently trusting or discarding it, surfaces it as something to reconcile.
Open that mod and the drawer leads with a banner: "A newer build is in your mods folder — v1.0.3.0. Silo manages v1.0.2.0." with two buttons:
backups/, and if the mod is active the new build is re-projected. The library now shows the new version; you're done.Under GitHub account, press Connect GitHub. A browser opens to github.com/login/device; enter the code Silo shows and authorize. Connecting gives faster update checks (5,000 requests/hour) and access to private repos, and it enables in-app GitHub installs from the Browse tab. By default the connection is read-only; use Enable actions to grant the public_repo scope so Star and Watch land on your account. You can Disconnect anytime, or use a Personal Access Token instead via the token option.
Silo does not ask for a Nexus account or API key. Nexus mods appear in the Browse catalog as an index only: Silo links back to each mod's Nexus page (Open page ↗) so you download from Nexus directly. There's nothing to connect and no key stored, and adult / age-restricted content is excluded from the index. This keeps Silo within Nexus's API terms while still letting you find and open their mods from one place.
The panel footer shows your installed Silo version.
The Integrity check in a mod's detail drawer compares your file against the trusted build SiloAPI hashed from its source. Unverified means there's no trusted build to compare against yet — usually because that mod isn't in the catalog. It is not a warning about the mod. Folder mods can't be verified at all (there's no archive to hash). This is a provenance check, not a virus scan.
Connecting GitHub is optional and lives in Settings → GitHub account → Connect GitHub: a browser opens to github.com/login/device; type in the code shown. This raises update-check limits to 5,000/hr, enables in-app installs and Star/Watch on mod pages, and lets you publish collections. The token stays on your machine, and a Disconnect button removes it at any time. There is no Nexus account to connect — Nexus is index-only.
Connecting GitHub is optional and lives in Settings → GitHub account → Connect GitHub: a browser opens to github.com/login/device; type in the code shown. This raises update-check limits to 5,000/hr, enables in-app installs and Star/Watch on mod pages, and lets you publish collections. The token stays on your machine, and a Disconnect button removes it at any time.
Farming Simulator 25 · mod manager · free & open source
Organize hundreds of mods, and Silo reads the game log to name the mod that actually crashed you, catches conflicts before you launch, verifies a mod is the real build, and pulls ModHub, GitHub and Nexus into one catalog. Its changes to your mod folder are designed to be reversible.
+Organize hundreds of mods, and Silo reads the game log to name the mod that actually crashed you, catches conflicts before you launch, verifies a mod is the real build, and pulls ModHub and GitHub into one catalog. Its changes to your mod folder are designed to be reversible.
The log scrolls a wall of red and names nothing. You disable mods at random and pray.
Two mods claim the same map, filltype or vehicle type. One quietly wins, or your save corrupts.
ModHub says outdated, GitHub shipped days ago, and you can't tell which number is real.
A mod lives on ModHub, its dev on GitHub, a mirror on Nexus. No one place tells the whole story.
A mod lives on ModHub, its dev on GitHub. No one place tells the whole story.
One record per mod that pulls ModHub, GitHub and Nexus together, so you see the latest version found across them instead of whichever source happened to update last.
+One record per mod that pulls ModHub and GitHub together, so you see the latest version found across them instead of whichever source happened to update last.
Silo hashes an installed mod and checks it against the trusted build its source published — a clean match, or the exact files that were changed. Provenance, not antivirus: it confirms what a mod is, it doesn't guess intent. It works across ModHub, GitHub and Nexus — a cross-source integrity check that's rare among mod tools.
+Silo hashes an installed mod and checks it against the trusted build its source published — a clean match, or the exact files that were changed. Provenance, not antivirus: it confirms what a mod is, it doesn't guess intent. It works across ModHub and GitHub — a cross-source integrity check that's rare among mod tools.
Star the repo on GitHub, endorse it on Nexus, jump to the ModHub page to rate it, all through your own accounts. Silo just opens the door. Your credentials and data stay yours.
+Star the repo on GitHub, jump to the ModHub page to rate it, all through your own accounts. Silo just opens the door. Your credentials and data stay yours.
Real screens — click any to enlarge.
It manages your Farming Simulator 25 mods. Silo organizes the library and reads log.txt to name the mod that crashed you. It flags conflicts such as duplicate maps and colliding filltypes, vehicle types or scripts. And it pulls ModHub, GitHub and Nexus into one catalog that shows the latest version found across all three.
It manages your Farming Simulator 25 mods. Silo organizes the library and reads log.txt to name the mod that crashed you. It flags conflicts such as duplicate maps and colliding filltypes, vehicle types or scripts. And it pulls ModHub and GitHub into one catalog that shows the latest version found across both.
Windows is the tested, supported platform today. macOS (Intel & Apple Silicon) and Linux builds exist but are experimental and largely untested — we're actively seeking testers on those platforms. It's one native app with per-OS game discovery and no runtime to install.
Yes. Silo keeps one record per mod that pulls all three together, so you see the latest version found across them. You can act on each through your own accounts: star on GitHub, endorse on Nexus, rate on ModHub. Silo just opens the door; your credentials stay on your machine.
+Yes. Silo keeps one record per mod that pulls both together, so you see the latest version found across them. You can act on each through your own accounts: star on GitHub, rate on ModHub. Silo just opens the door; your credentials stay on your machine.