SLBridge: documented third-party script API (public channel, owner-only by default, per-object opt-in) #1218

New issue

Open

opened 2026-10-28 16:42:53 +00:00 by sky_line · 0 comments

sky_line commented

2026-10-28 16:42:53 +00:00

Owner

Part of #1213. Lets other people's in-world scripts (combat systems, games, HUDs) talk to Slipstream features in a controlled way.

A documented public channel / message set: e.g. a script asks "is this a Slipstream viewer with capability X?" and gets a minimal answer. Some Slipstream features also accept input from scripts (e.g. a combat HUD feeding hit markers).
Default owner-only: only objects the user owns may talk to the user's viewer. A per-object opt-in (a prompt like a script permission dialog, remembered per object or creator) covers others.
Never: reveal information the user hasn't granted (no viewer fingerprinting to arbitrary scripts beyond the minimal capability answer if the user allows it), or run actions affecting inventory or other avatars without consent.
Rate limits per object.
Document it in the protocol spec with LSL examples.

Design-review this with the owner before implementing: it's the part with the most privacy / abuse surface.

Part of #1213. Lets other people's in-world scripts (combat systems, games, HUDs) talk to Slipstream features in a controlled way. - **A documented public channel / message set:** e.g. a script asks "is this a Slipstream viewer with capability X?" and gets a minimal answer. Some Slipstream features also accept input from scripts (e.g. a combat HUD feeding hit markers). - **Default owner-only:** only objects the user owns may talk to the user's viewer. A per-object opt-in (a prompt like a script permission dialog, remembered per object or creator) covers others. - **Never:** reveal information the user hasn't granted (no viewer fingerprinting to arbitrary scripts beyond the minimal capability answer if the user allows it), or run actions affecting inventory or other avatars without consent. - Rate limits per object. - Document it in the protocol spec with LSL examples. Design-review this with the owner before implementing: it's the part with the most privacy / abuse surface.

sky_line added this to the Slipstream project

2026-10-28 16:42:53 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sky_line/Slipstream#1218

No description provided.

Rows
Columns