Writing a script can take hours. Copying one takes seconds. That imbalance makes clear authorship, permission, and attribution especially important.
Today we are introducing SoundKino Scripts, a new place for writers to publish their work, reach performers, and state exactly how their scripts may be used.
What the new Scripts feature includes
Every registered writer can publish a script with:
- an audience label such as F4M, M4A, or A4A;
- performer and listener information;
- searchable tags, a summary, and an optional cover;
- public, unlisted, hidden, and sensitive-content controls;
- a choice between human only, AI only, or human and AI use;
- custom terms covering credit, monetization, edits, reposting, and performance.
The Scripts feed offers newest, top, and oldest sorting. Each card shows a short excerpt, while the complete work and its terms live on the script page.
Copying requires an account and an explicit choice
There is no special download button. When a logged-in reader selects script text and copies it, SoundKino asks whether the intended user is a human or an AI. The reader must accept the writer's terms before the selected text reaches the clipboard.
The server checks that declaration against the writer's permission. An AI declaration cannot copy a human-only script, and a human declaration cannot copy an AI-only script. SoundKino records the account, declared reader type, time, script, and a one-way hash derived from the network address.
This creates a useful consent trail without storing the visitor's raw IP address in the confirmation record.
Can technology truly identify a human or an AI?
Not with certainty—and any product claiming otherwise deserves skepticism.
A browser cannot reliably determine whether copied text will later be read by a person, pasted into a language model, or sent to a synthetic voice tool. Bots can imitate browsers, humans can automate tasks, and detection scores are probabilities rather than proof.
Our approach therefore combines several layers:
- Authentication connects the action to a registered account.
- Explicit declaration makes the intended use unambiguous.
- Server-side enforcement blocks a declared use the writer did not permit.
- Terms acceptance records agreement at the moment of copying.
- Audit data gives moderators evidence when investigating misuse.
- Rate limits make automated bulk copying more difficult.
These controls create accountability and friction. They do not provide DRM, prevent screenshots, or make dishonest behavior impossible. Text displayed on a screen can always be retyped or captured. The goal is a defensible permission system, not a magical lock.
Why the distinction still matters
Writers have different views on synthetic performance. Some welcome AI adaptations, some write only for human performers, and others specifically create material for synthetic characters or accessibility tools. A single platform-wide rule would erase those differences.
SoundKino puts that decision with the writer. Permissions are visible before use, custom terms add nuance, and every confirmed copy contributes to the script's transparent usage count.
A foundation we can improve
This launch is a first practical layer. Future protections could include verified performer profiles, versioned licenses, revocable permissions, similarity matching for reposts, signed attribution receipts, and clearer reporting tools.
The principle will remain simple: writers set the terms, users make an informed choice, and the platform records enough evidence to support accountability.
You can browse the new Scripts section or log in and publish your own.