TPV Policy compliance checklist (before Viewer Directory application) #214
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#214
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Track compliance with the Second Life Third Party Viewer Policy (https://secondlife.com/corporate/third-party-viewers) before we apply for the Viewer Directory. Section numbers follow the policy.
Done / verified (2026-09-30)
Slipstream Release/Slipstream Beta/Slipstream Test(scripts/ci/version.sh) plus the version. Login and the viewer statistics packet sendgetChannelAndVersion()(llviewerstats.cpp). The stats packet isn't omitted or falsified.To do
564763931009220608, llappviewer.cpp, inherited from upstreamcefc3f0a7c). Register our own "Slipstream Viewer" Discord application and swap the ID. Until then, presence shows up as Alchemy's app. It's on by default (EnableDiscord=1), with name and location off by default.llpanellogin.cppcomputes channel/version and doesn't display them. Add a visible label to the login panel. The About window already shows both.Refs the website privacy page and About-window changes (2026-09-30).
Checklist items verified on 2026-09-30 are done. Open items remain (viewer name/version on the login screen, installer scope, documenting feature limitations, shared-experience review) and nothing is being worked on right now, so this moves from In Progress to To Do.
Moving this back to the backlog: the verified items are done and the open ones (login screen naming, installer scope, documenting limitations, shared-experience review) are waiting on the application timing, not on current work.