@kehto/paja 0.35.3 → 0.37.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 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,19 @@ 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).
753
+
754
+ The same sidebar discovers CVM tool inventories from a `nevent`, a CEP-15 tool
755
+ schema hash, or an HTTPS website's `/.well-known/napplet.json`. Choose a provider,
756
+ local family label, and tools; generated JSON is read-only and shows its source.
757
+ Manual JSON remains editable. Saved families persist per host origin and coexist
758
+ in the registry, including without a multiplayer signaling profile. Saves and
759
+ removals reload the host. ContextVM doesn't define named-family manifests or
760
+ `naddr` discovery; labels and membership are local choices.