Skip to content

Make creators responsible for chat in projects that connect players - #57

Closed
Mistium wants to merge 5 commits into
mainfrom
player-contact
Closed

Mistium wants to merge 5 commits into
mainfrom
player-contact

Conversation

@Mistium

@Mistium Mistium commented Oct 16, 2026

Copy link
Copy Markdown
Member

Makes the creator of a project that lets players talk to each other responsible for that chat. MistWarp can't see or police chat that runs through other services (CloudLink, WebSocket extensions, OriginChats, Rotur and others), so the leverage is on the project itself.

What changes

  • Detection. A project connects players when it uses a known gallery extension (matched by normalised URL, or by extension ID, so copies hosted elsewhere count too) or an extension an admin marks with POST /v1/admin/extensions/connects-players. Extension IDs are now stored on project.extensions[].id at upload.
  • Declaration. PUT /v1/projects/:id/player-contact lets the owner add a public contact for chat and accept the chat rules (playerContactTermsVersion = 1). Only the owner can declare, minor accounts can only give an https link, and class accounts can't declare. Transferring a project clears the declaration.
  • Sharing gate. Publishing, or setting the visibility to public or unlisted, returns 400 player_contact_required until the project is declared.
  • Delisting, not unsharing. Undeclared connecting projects keep working by link but are left out of every list (playerContactMissing on the index entry, filtered alongside shadow bans; the author and admins still see them). Owners get a player_contact_needed notification, at most once per project and owner. This is sent after an upload, a merge, an admin index, a moderator restore, an admin flag or an ownership transfer, and once at startup by a migration.
  • Chat reports. New report type chat on projects that let players talk, with an optional player name. Spam, harassment, hate, scam and other also notify the owner as player_chat_report. That notification never names the reporter, and it is skipped for reporters the owner blocked or muted, for blocked or shadow-banned reporters, and after the first one per reporter and project in six hours. Owners who are minors or class accounts don't get the text. Sexual, violent and urgent reports stay with moderators. A named player becomes the report subject, so Rotur can act on that account, and the snapshot says the name wasn't checked.
  • Class accounts can't open, remix or see inside other people's connecting projects, and connecting projects can't be used as classroom starters.
  • GET /v1/projects/:id gains playerContact (connects, services, declared, contact, required, missing, ...). Custom extension URLs are only shown to editors.

Also fixed

OSL copies arrays on assert, so storeProjectExtensions never saved the URLs and project lists of extension records, and blocking an extension URL never saved either. Both now write the array back.

Decisions for you

  • Chat rule wording. The rules, including "act on reports within 48 hours", are in the site PR. Bump playerContactTermsVersion in both repos if you change them.
  • Unsharing. Existing shared projects aren't unshared. They drop out of lists until their owners declare.
  • Blob URL. /blobs/projects/:id/project.json stays public for shared projects. Anyone signed out can play them anyway, so the class-account block is account-level, not a sandbox.
  • Not covered.
    • The remix tree and profile review lists don't filter undeclared projects. They don't filter shadow-banned ones either.
    • The built-in MistWarp multiplayer isn't covered, because it's switched off.
    • Plain HTTP or cloud-variable chat is left to the creator's own declaration.
  • Not legal advice. Your Online Safety Act risk assessment should still mention projects that connect players.

Testing

  • Checks: osl lsp check main.osl is clean, every *.test.osl passes with no warnings, and osl compile builds. There are new tests in player-contact-policy.test.osl and banned-owners.test.osl.
  • End to end against a local build:
    • The sharing gate, declaration validation, the owner-only and minor rules, delisting and relisting in Explore and on profiles.
    • Notifications, chat reports (including refusal on projects without chat, and throttling).
    • The admin flag, URL blocking, and detection of a hosted CloudLink copy by ID.
  • Review: two rounds of independent review, with every must-fix and should-fix finding addressed.

No visible surface in this repo; the screenshots are in the site PR.

Projects that use an extension known to connect players (CloudLink,
WebSocket, OriginChats, Rotur and others from the galleries, plus any
extension an admin flags) now need chat details before they can be
shared: a public contact for chat and acceptance of the chat rules.

Undeclared projects are left out of every list until the creator adds
them, without unsharing anyone's work, and the owner is told why.
Players can report chat in a project; everyday reports reach the creator
as well as moderators, while sexual, violent and urgent ones stay with
moderators. Class accounts can't open other people's projects that
connect players.

Also fixes extension records and the URL blocklist never saving their
appended entries.
- Detect connecting extensions by their extension ID as well as the
  gallery URL, and normalise gallery URLs before matching.
- Accept chat reports only for projects that let players talk and that
  the reporter can see, skip owner notifications from blocked, muted or
  shadow banned reporters, send at most one per reporter and project
  every six hours, and leave the text out for minor and class owners.
- Keep class accounts from remixing or seeing inside other people's
  connecting projects.
- Notify each owner once per project, reindex under the project lock,
  cache admin flags instead of reading the extension policy on every
  request, and cover the admin index, merge and restore paths.
- Keep chat report evidence while chat reports are open, filter space
  list summaries, and treat undeclared projects as unlisted in activity.
- Hide custom extension URLs from viewers who can't edit the project.
- Keep chat notification markers in their own collection, so project
  diagnostics never prune or show them.
- Only the owner can take responsibility for chat, and minor accounts
  can only give an https link as their public contact.
- Take the history lock as well as the upload lock when saving chat
  details or reindexing, so a concurrent upload can't be reverted.
- Resolve parent segments in gallery URLs.
- Refuse classroom starter projects that let players talk.
@Mistium

Mistium commented Oct 17, 2026

Copy link
Copy Markdown
Member Author

Closing alongside MistWarp/scratch-gui#147: the player named in a chat report becomes the report subject and is sent to Rotur automatically with no evidence. Will reopen once that's fixed.

@Mistium Mistium closed this Oct 17, 2026
@Mistium Mistium mentioned this pull request Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant