Repository navigation
Guides: add Publish a public list link on TigerHub - #21
saucissefarciehumaine-prog wants to merge 7 commits into
Conversation
First page of the guides section: the wrong purchases that only reveal themselves after delivery - chip references, sealed PN532 dongles, the 3.5 vs 3.5B screen, unpowered USB hubs, metric screws, CF filament. Sources: Tiger-Scale-V3 README (sealed dongles, BOM), the TigerTag chip concept page (NTAG213/215), the compatibility matrix (MIFARE Classic), team and builder reports on the Discord (3.5 vs 3.5B, hub write failures, screws). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Chip-level problems ordered by frequency: detection checks, blank/Init chips, wrong data, printer-side support, TigerTag+ verification failures (fixable vs by-design), interrupted writes, and what to include when asking in #help-and-support. Stacked on the buying-pitfalls branch: cross-references it twice instead of duplicating the hub-power and on-metal explanations. Sources: the TigerTag chip concept page, the TigerTag+ product page, the compatibility matrix and Snapmaker page, builder reports on the Discord (marked as reported). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
From the #help-and-support history (Aug 2025): a write failing on a chip carrying non-TigerTag data, where a blank chip works first try. Documents the convert path and the community wipe workaround. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The signature now belongs to the TigerTag+ Certified tier, per the updated tigertag-plus product page on main. Section retitled, and the rewritten-after-signing row now says the chip stays readable, simply no longer certified. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The foundational how-to from the guides TODO list: which chips to buy, which reader, encoding from phone or desktop, Twin Tag pairs, encoding in series, and what home encoding cannot do (Certified). Stacked on the guides stack; cross-references buying-pitfalls and troubleshooting instead of restating them. Removes the matching line from the README TODO block. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Second guides-TODO item: writing a TigerData / TigerData+ record onto a physical NTAG chip. Flags the desktop-only constraint (mobile cannot burn an existing chipless record yet), and that a promoted TigerData+ becomes a TigerTag+ (identified, not signed). Stacked on guide-buy-encode-chips. Removes the matching README TODO line. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Third guides-TODO item: sharing a read-only inventory or wishlist as a /list/<token> link, no app or account for the viewer. Covers publishing, revoking (new token on re-publish), and the public-link vs friend-code distinction. Stacked on guide-promote-chipless. Removes the matching README TODO line. UI wording kept at the level the source supports (generate / revoke) to avoid inventing button paths. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
@saucissefarciehumaine-prog is attempting to deploy a commit to the Tiger-Project Team on Vercel. A member of the Team first needs to authorize it. |
|
Closing with #2, #19 and #20 — the full reasoning and the rules for redoing these are in #2, please read that one first. This branch is the top of the stack: it carries all five pages, so merging it would have merged everything under it in one go, including the page rejected in #1. Specific to this one: The What is genuinely yours in this page and worth keeping: treat the token like a shared password, revoking then re-publishing yields a new token, and the distinction between a public link and sharing with a friend. None of that is written anywhere today. It belongs on the TigerHub page, or in One caution on the revocation wording: "the old URL goes dead immediately" is a promise about backend behaviour. If it is not verified against the implementation, phrase it as what the app offers rather than as a guarantee about propagation. Bring it back as an addition to the page that owns the subject rather than as a new one, and it lands quickly. |
2 participants
Guides TODO #3: publishing a public read-only list link on TigerHub.
Covers the
https://tigersystem.io/list/<token>mechanism — publish from Tiger Studio / Connect, revoke (a re-publish mints a new token), and a table contrasting the public link with the friend-code path.Stacked on the guides stack (…→ buy-encode → promote-chipless → this). Removes the matching README TODO line — after this, only "migrate a spreadsheet inventory" remains, and I've opened a separate question-issue for it since the import format isn't documented anywhere I can source.
Source:
products/tigerhub.md,concepts/inventory-and-cloud-sync.md. UI wording deliberately kept at "generate / revoke a share link" — the source doesn't spell out exact button paths and I didn't want to invent them.🤖 Generated with Claude Code