You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server logs will occasionally include some hunt-specific information; I haven't done a deep audit but I'm certain that puzzle titles and tags are in there, and pretty sure solutions can be logged as well.
In a multi-tenant world, a server admin might be solving on one team while supporting the site for other teams. They may need to debug issues that require looking at server logs. If those logs contain puzzle information that they don't already know, it could spoil them.
Of course, this would also impact things like BugSnag (particularly around the breadcrumbs), which would be harder to handle here (and probably undesirable, since the breadcrumbs can be quite useful).
What should the philosophy here be?
The text was updated successfully, but these errors were encountered:
My random opinion is that a server admin should only rarely be looking at logs anyway, and it's probably more important for them to be able to debug issues than to remain unspoiled on answers, etc.
The server logs will occasionally include some hunt-specific information; I haven't done a deep audit but I'm certain that puzzle titles and tags are in there, and pretty sure solutions can be logged as well.
In a multi-tenant world, a server admin might be solving on one team while supporting the site for other teams. They may need to debug issues that require looking at server logs. If those logs contain puzzle information that they don't already know, it could spoil them.
Of course, this would also impact things like BugSnag (particularly around the breadcrumbs), which would be harder to handle here (and probably undesirable, since the breadcrumbs can be quite useful).
What should the philosophy here be?
The text was updated successfully, but these errors were encountered: