POC mode: strip moderation controls, backlog them - #22
Merged
Conversation
This is a proof of concept and the controls that kick, filter or restrict
players have been costing more than they protect. Every one of them has
now caused an outage or a support incident at some point, and none of them
defends against a threat a five-person family server actually has.
Removed:
Profanity Guard chat filter mod, pure moderation
FORCE_GAMEMODE forced everyone back to survival on join, overriding
an op who had deliberately switched to creative
Already gone for the same reason: the playtime limiter (dead since the
droplet move), spawn protection (silently blocked building near the
house), the airborne kick (kicked players for using Ad Astra in space),
and the anticheat (kicked a whitelisted player for opening a door).
Deliberately KEPT, and this is the part worth arguing about: the
whitelist and online-mode. Those are not moderation. They are the
difference between a private family server and an open one. The game
port is scanned continuously, which any day's log shows as a stream of
VANILLA connection attempts from hosts nobody invited. Turning off the
whitelist puts a server with children on it in front of those. If it
comes off, that should be a deliberate decision to run a public server,
not a side effect of reducing friction, and everything else gets
revisited at the same time.
Also kept: PrismProtect, which blocks nothing and kicks nobody. It is
what makes griefing reversible, so removing it removes the undo rather
than a restriction.
specs/0006 records what came off, what stayed and why, and the order
things should return in. Anticheat only comes back with a config file,
ops exemption and server-side logging, because the last one had none of
those.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a proof of concept. Controls that kick, filter or restrict players have been costing more than they protect.
Removed
truetofalseAlready gone for the same reason, listed so the picture is complete: the playtime limiter (dead since the droplet move), spawn protection (silently blocked building near the house), the airborne kick (kicked players for using Ad Astra in space), and the anticheat (kicked a whitelisted player for opening a door).
Every single one of those caused an outage or a support incident.
Deliberately kept, and this is the part worth arguing about
The whitelist and
ONLINE_MODE. These are not moderation. They are the difference between a private family server and an open one.The game port is scanned continuously. Any day of logs shows a stream of
VANILLA connection attemptentries from hosts nobody invited. Turning off the whitelist puts a server with children on it directly in front of those.If it comes off, that should be a deliberate decision to run a public server, not a side effect of reducing friction, and everything else gets revisited at the same time. Say the word and I will do it, but I am not doing it silently.
PrismProtect also stays. It blocks nothing and kicks nobody. It is what makes griefing reversible, so removing it removes the undo, not a restriction.
Backlog
specs/0006-poc-moderation-backlog.mdrecords what came off, what stayed, why, and the order things should return in:Verified
Removing Profanity Guard is server-side only, so no player needs to re-import anything.