Skip to content

Products: TigerHub — a public list link, in practice - #49

Open
saucissefarciehumaine-prog wants to merge 1 commit into
TigerTag-Project:mainfrom
saucissefarciehumaine-prog:redo/tigerhub-sharing
Open

saucissefarciehumaine-prog wants to merge 1 commit into
TigerTag-Project:mainfrom
saucissefarciehumaine-prog:redo/tigerhub-sharing

Conversation

@saucissefarciehumaine-prog

Copy link
Copy Markdown
Contributor

One page, one subject, branched from current main (d1858fc) — not stacked on anything.

The question this answers. "I published a list link — who can open it, and how do I take it back?" glossary.md sends the reader here for it ("Friend code / list link — the two ways to share an inventory… See TigerHub"), so do products/README.md and architecture/overview.md, and tigerhub.md answers in one clause: "publish a read-only list anyone can open in a browser." The page everyone points at says the least. This fills it, as a section — the home you suggested in #21, not a new page.

What it says. The token is the key (no account, no app — a password you chose to share); links are made and revoked from the apps, not from the website, and republishing mints a new token; the viewer sees that list and nothing else. Then a four-row table putting the link beside the other way to share, a friend.

The #21 correction, applied. "The old URL goes dead immediately" is gone. It was a promise about backend propagation I could not point at. What the page claims now is only what the apps offer: revoking withdraws a list, and publishing again afterwards produces a new token, so an earlier link is not revived by it.

A fact has one home — tightened during the rebase. The friend column originally carried "request → accept" and "either side can remove", which are concepts/inventory-and-cloud-sync.md:83-85's to state. Both cells are now three words, and the sentence under the table says explicitly that the friend half is summarised only to sit beside the link, and sends the rules to the page that owns them. The comparison is what this page adds; the mechanism stays where it lives.

Not touched: the publish a public list link TODO in guides/README.md — that list is about guides, and whether this section retires a planned one is your call.

Two files, both locales. Existing page, no new route, no sidebar entry. i18n/fr mirror updated with its sourceHash refreshed. pnpm check:docs, check:i18n and build all green locally (131 pages, all internal links valid).

🤖 Generated with Claude Code

An addition to products/tigerhub.md (its home), not a new page: the token is
the whole key; links are made and revoked from the apps, TigerHub only renders
them; publishing again yields a new token; read-only and scoped to that list.
Plus the link-vs-friend table, pointing at the sharing model owned by
concepts/inventory-and-cloud-sync.md.

No claim on how fast a revoked link stops resolving — only what the apps
offer.

i18n/fr mirror updated, hash current. check:docs, check:i18n and build green
locally.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 14, 2026

Copy link
Copy Markdown

@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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant