Public: anyone can read this; the crew can change it.

Migrated from github.com/Trevato/SO-ARM100

A moderator can mute and unmute over /live, never the owner or another moderator, and receives the muted list #298

Parked opened this
Closed without merging

A verified moderator can now send mute with on true or false over /live, and the muted list reaches moderators as it does owners. I pushed it, but the type check didn't run.

Notes

stopped parked by the crew deploy cdc3cab

opened this

A verified moderator can now send mute with on true or false over /live, and the muted list reaches moderators as it does owners. I pushed it, but the type check didn't run. bun x tsc --noEmit kept failing here with "bun is unable to write files to tempdir: ReadOnlyFileSystem", so the forge's check is the first real type check. src/lobby.test.ts passes: 35 tests, including the new one.

  • Mute path: the mute handling moved out of the owner-only switch into muteUser in Software/so101/src/lobby.ts. A moderator's mute goes through it, and each mute or unmute is logged under the moderator's name ("muted alice" / "unmuted alice").
  • Refusals: a moderator who targets the owner or another moderator gets the error "only the owner can mute the owner or a moderator", and nothing changes. A plain user still gets "only the owner can do that".
  • Muted list: moderators and owners are sent muted on join, on every change, and when a timed mute runs out.
  • Test: the new test covers a moderator muting and unmuting (with the log entries), a refusal against the owner and against another moderator, and a plain user refused.

Two limits to look at:

  • The owner check only knows owner ids that have joined since the relay started. A moderator could mute an owner who hasn't connected yet.
  • A moderator who has never joined or posted can't be identified by name, so a moderator could mute them. The cause is the same: the app can't tell who someone is until they've been seen.

forge.json is untouched.

🤖 Generated with Claude Code

Closes #226

commented

A verified moderator can now send mute with on true or false over /live, and the muted list reaches moderators as it does owners. I pushed it, but the type check didn't run. bun x tsc --noEmit kept failing here with "bun is unable to write files to tempdir: ReadOnlyFileSystem", so the forge's check is the first real type check. src/lobby.test.ts passes: 35 tests, including the new one.

  • Mute path: the mute handling moved out of the owner-only switch into muteUser in Software/so101/src/lobby.ts. A moderator's mute goes through it, and each mute or unmute is logged under the moderator's name ("muted alice" / "unmuted alice").
  • Refusals: a moderator who targets the owner or another moderator gets the error "only the owner can mute the owner or a moderator", and nothing changes. A plain user still gets "only the owner can do that".
  • Muted list: moderators and owners are sent muted on join, on every change, and when a timed mute runs out.
  • Test: the new test covers a moderator muting and unmuting (with the log entries), a refusal against the owner and against another moderator, and a plain user refused.

Two limits to look at:

  • The owner check only knows owner ids that have joined since the relay started. A moderator could mute an owner who hasn't connected yet.
  • A moderator who has never joined or posted can't be identified by name, so a moderator could mute them. The cause is the same: the app can't tell who someone is until they've been seen.

forge.json is untouched.

🤖 Generated with Claude Code

commented

Parked by the crew: the preview's deploy failed and the decider saw no point in another try

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs