Andreas Reinhold / reiniandClaude Opus 5
1bcb868897
The site now says files are encrypted in the browser and sent in chunks, describes the password generator and its admin settings, explains why uploads need HTTPS and how to serve it, and replaces the old PHP upload cap with the admin's file size limits and the chunk size. The alt texts and captions match the retaken screenshots. The README no longer lists Tailwind CSS, and the website rules describe the encryption and the copied colours accurately. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
10 lines
1013 B
Markdown
10 lines
1013 B
Markdown
---
|
|
paths:
|
|
- 'website/**'
|
|
---
|
|
|
|
# Website
|
|
|
|
## website/ is the live site, uploaded by hand
|
|
website/ is a faithful copy of sealshare.nonameweb.ch (METANET hosting), hand-written HTML/CSS with no build step, uploaded wholesale when it changes. Colours in css/theme.css are copied from the indigo profile in resources/css/material-scheme.json: the standard light and dark values (profiles.indigo.light/dark) and the high-contrast light and dark values (profiles.indigo.contrast.high) — copy them again if indigo is regenerated differently; the site does not follow the admin's colour profile. The comparison tables are dated and every competitor value has a source from the product's own site, docs or repo; an unsourced value is "—", never a guess. Never call SealShare's encryption end-to-end (files are encrypted in the browser with a key the server issues, and the server decrypts them for downloads). Nothing may load from another host except plausible.io. tests/Feature/WebsiteTest.php guards all of this.
|