@kehto/paja 0.35.2 → 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/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Kehto contributors
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
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
- WebRTC is advertised only when the host has the browser WebRTC API, a live
145
- relay boundary, and a connected signer with NIP-44 support. Paja owns the
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
- This implementation tracks pinned
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).