@kehto/paja 0.35.3 → 0.36.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -3
- package/dist/browser-host.js +2540 -1819
- package/dist/browser-host.js.map +1 -1
- package/dist/{chunk-HTLBCTIN.js → chunk-DK5RJN5P.js} +155 -84
- package/dist/chunk-DK5RJN5P.js.map +1 -0
- package/dist/cli.d.ts +2 -1
- package/dist/cli.js +1 -1
- package/dist/index.d.ts +2 -2
- package/dist/index.js +3 -1
- package/dist/{server-B7uqpu8g.d.ts → server-D1H77278.d.ts} +36 -1
- package/package.json +7 -7
- package/dist/chunk-HTLBCTIN.js.map +0 -1
package/README.md
CHANGED
|
@@ -141,13 +141,16 @@ and is not added to Paja's in-memory relay view. Paja's scoped-relay hook
|
|
|
141
141
|
likewise waits for the backend result and returns `false` after denial or
|
|
142
142
|
transport failure.
|
|
143
143
|
|
|
144
|
-
|
|
145
|
-
|
|
144
|
+
By default, WebRTC needs the browser WebRTC API, live relays, and a connected
|
|
145
|
+
NIP-44 signer. An explicitly configured multiplayer profile instead uses an
|
|
146
|
+
isolated temporary key shared with that window’s CVM transport. Paja owns the
|
|
146
147
|
`RTCPeerConnection` and data channels, uses signed kind-25050 Nostr events for
|
|
147
148
|
encrypted offer/answer signaling, and asks for explicit session consent with a
|
|
148
149
|
network-metadata warning. Napplets receive only NAP session/events and JSON data
|
|
149
150
|
channel payloads—never SDP, ICE state, relay sockets, or peer-connection objects.
|
|
150
|
-
|
|
151
|
+
Connecting or disconnecting a signer updates the runtime's service registration
|
|
152
|
+
before the replacement iframe loads, so an advertised WebRTC domain can answer requests.
|
|
153
|
+
The default signaling implementation tracks pinned
|
|
151
154
|
[NAP-WEBRTC `5fae95dd2c8e59bd06c654e0845656add077dcda`](https://github.com/napplet/naps/blob/5fae95dd2c8e59bd06c654e0845656add077dcda/naps/NAP-WEBRTC.md)
|
|
152
155
|
and the kind/tag conventions in
|
|
153
156
|
[NIP-100 PR #363 at `ead1cd6`](https://github.com/nostr-protocol/nips/pull/363).
|
|
@@ -739,3 +742,11 @@ Paja explicitly installs operation and prompt limiters from `@kehto/rate-limit`
|
|
|
739
742
|
in `createPajaPermissionAdapter`. These are Paja host choices; runtime and Firewall
|
|
740
743
|
do not impose them on other hosts. Limiter configuration and counters are separate
|
|
741
744
|
from approval grants.
|
|
745
|
+
|
|
746
|
+
### Configurable multiplayer providers
|
|
747
|
+
|
|
748
|
+
The **Multiplayer providers** sidebar accepts explicit JSON settings, also available
|
|
749
|
+
as `simulation.multiplayer` in a Paja config file. Select `soy-rtc/1`, signaling
|
|
750
|
+
relays, and CVM families with pinned tool schemas. Optional static STUN/TURN
|
|
751
|
+
settings receive separate endpoint approval. No provider is selected from an app
|
|
752
|
+
URL. See [configuration and interoperability](/paja-multiplayer).
|