voltkit-rtc-server 0.1.0__tar.gz

voltkit_rtc_server-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+.venv/
+dist/
+build/
+__pycache__/
+*.egg-info/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/

voltkit_rtc_server-0.1.0/CHANGELOG.md

@@ -0,0 +1,57 @@
+# Changelog
+
+## 0.1.0 (2026-10-23)
+
+The first release under the name `voltkit-rtc-server`, imported as
+`voltkit_rtc.server`. The name says what the package is for: your backend,
+where the API secret lives. The `voltkit-rtc` 0.1.0 published on PyPI earlier
+the same day was this same code under the package's first name; it is yanked,
+so install `voltkit-rtc-server` and import from `voltkit_rtc.server`.
+`voltkit_rtc` itself is a namespace shared by VoltKit's Python packages, with
+no `__init__.py` of its own, so `import voltkit_rtc` alone holds nothing.
+
+Every call of `@voltkit-rtc/server` 0.4.8, with the same requests, replies,
+retries, errors and redaction. The behaviour is pinned by the shared vectors
+(`docs/server-sdk-vectors.json`, generated from the Node SDK) and described in
+`docs/SERVER-SDK-SPEC.md`.
+
+- `StreamClient` with `ensure_room`, `create_room`, `create_token`, `get_room`,
+  `list_rooms`, `list_participants`, `delete_room`; chat (`create_chat_token`,
+  `get_chat_info`, `list_messages`, `send_message`, `delete_message`,
+  `list_chat_mutes`, `mute_chat`, `unmute_chat`); usage (`get_usage`,
+  `get_usage_series`); billing (`get_balance`, `get_rates`); broadcast
+  (`create_stream`, `get_stream`, `list_streams`, `update_stream`,
+  `delete_stream`, `create_stream_token`; not offered on VoltKit cloud today).
+  `StreamClient.from_env()` reads `VOLTKIT_RTC_URL`, `VOLTKIT_RTC_SECRET` and
+  the optional `VOLTKIT_API_URL`; the plain constructor reads nothing.
+- Transient failures (`network`, 429, 5xx except `billing-unavailable`) are
+  retried with jittered backoff (200 ms doubling, plus up to 100 ms) on every
+  call that is safe to repeat; `create_room`, `create_stream` and
+  `send_message` are sent once. A delete whose reply was lost resolves when the
+  retry answers 404.
+- One deadline per attempt (`timeout`, default 10 s) that covers the headers
+  and the body, on `http.client` with no third-party dependency. A redirect is
+  never followed with the API key (`redirected`); the public rates may follow
+  one. An injectable `Transport` for proxies, instrumentation and tests.
+- The API key never reaches an error, a log line or a printed client: the
+  server's words, a redirect's target and the transport's own error are
+  redacted in every encoding the Node SDK redacts (URL-encoded, form-encoded,
+  JSON-escaped, HTML character references, and each of those escaped once
+  more); URL credentials are hidden; a key that no HTTP header can carry, or
+  that no VoltKit key has, is refused when the client is made. `repr`, `str`,
+  `vars` and `pickle` show nothing.
+- Webhooks: `verify_webhook` and `parse_webhook` over the raw body, with lists
+  of secrets for a rotation, several `v1` signatures, a 300-second tolerance in
+  both directions, constant-time comparison, and the shared golden vector.
+- `StreamError` with `code`, `status`, `message`, `retryable` and the
+  predicates `is_not_found`, `is_out_of_minutes`, `is_quota`,
+  `is_capacity_exhausted`, `is_broadcast_disabled`, `is_billing_unavailable`;
+  `ERROR_CODES` and `REST_ERROR_CODES` from the shared registry.
+- Typed (`py.typed`, `TypedDict`s for every reply), Python 3.9 to 3.14.
+
+Compared with the unpublished 2026-10-15 draft: local token minting
+(`tokens.py`) is gone, since VoltKit tokens are signed by the controller with a
+secret a customer never holds; `urllib` gave way to `http.client` so the
+deadline covers the body; the key is validated and redacted in every form
+rather than replaced as a literal; the missing `screen-share-ended` code was
+added to the registry.

voltkit_rtc_server-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 VoltKit
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.