How This Site Runs

The sts Team formed in November 2025, and stsqz.com went live on June 17, 2026. Every line of code from day one to now was written and maintained by members by hand - no site-builder templates. This page is about the principles behind the place, for the curious.

Local-first: your data stays on your device

This is the single most important design decision on the site. All five AI lab tools (speech to text, text recognition, background removal, audio & video, anime photo) do their computing inside your browser:

• Files are never uploaded - processing a many-megabyte video produces zero upload traffic
• AI models download to your device only the first time you use a tool, and work offline from then on
• Close the page and nothing changes; everything works fully without an account

The trade-off: our "server" barely computes at all. The payoff: your privacy is safe by construction.

Light: fast where it should be

All the site's text and code is handwritten and loaded on demand - no kitchen-sink dependencies; static assets ship pre-compressed; HTTP/3 is supported, and capable browsers automatically take the faster road. Pages must stay usable on cheap devices and slow networks - and the heavy interfaces (docs hub, arcade) all respect the system's "reduce motion" setting.

Secure: tight by default

HTTPS everywhere; a strict content security policy whitelists exactly what code a page may run; registration and membership applications both pass slider human-verification; the feedback and application channels are rate-limited - built to stop floods, not people. None of this is visible day to day, but it's always working.

A direct line: the feedback channel

/feedback is a mailbox straight to the team: suggestions, bug reports, complaints - all welcome, anonymous or signed. The team replies right under your message, and messages from the same network exit show up connected on the page. Submissions are rate-limited: built to stop floods, not people.

A little open source

We packaged our whole method for "de-AI-ing AI-written pages" into an open-source skill, human-ui-copy, published on GitHub (MIT). This site was its first rehabilitation case - see the De-AI Your Pages guide in this hub. More of the team's work will follow the same path.

Why this content

The games were written by members, the animated shorts made by members, the tutorials written after stepping in every pit themselves. This site is, first of all, the team's portfolio and playground - "website" comes second. If one of these guides helped you, that's what it exists for.