Share links: per-device AI limits and an MCP "Share links" switch
All checks were successful
Verify and publish V2 container / build-and-push (push) Successful in 28s

- Each MCP server gets a "Share links" switch (off by default). Shared Explain and Ask use
  only the servers that have it on.
- Visitor AI requests are limited per device instead of per IP, so one campus network
  doesn't share an allowance. Each browser gets a random id in a signed, HTTP-only cookie
  (20 requests per 10 minutes per link). Forged ids are replaced. A link-wide cap of 500
  requests per hour stays as a cost backstop.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Elijah 2026-11-15 16:12:45 -07:00
parent 031f7bec31
commit 60cf2322f7
7 changed files with 128 additions and 45 deletions

View file

@ -101,7 +101,8 @@ network and process modules in JavaScript (Node 24's permission model does not b
New: MCP servers with per-server instructions and per-area switches (`server/ai/mcp.ts`,
`runChatWithMcp` in `service.ts`); per-share AI switches (migration 4, `shares.ai`;
`POST /api/public/:token/explain|chat`, rate-limited, no tools); flashcard Standard mode with
`POST /api/public/:token/explain|chat`, limited per device via a signed visitor cookie plus a
per-link cap; MCP servers join only with their "Share links" switch on); flashcard Standard mode with
"repeat missed cards until known" next to Spaced repetition on the deck page; streak visuals
restyled in the app palette (marker highlighter, accent bar, mono numerals); document Side by
side / Original view with generated previews for Word and PowerPoint. Item 13 (pictures in