The /script/ command will faithfully capture a session including
anything sensitive. The resulting typescript is binary which hinders
efforts to edit out sensitive information. This forces users into the
dilemma of disclosing their script in full (including sensitive info),
or not collaborating at all. Users need to be able to edit the
transcript in a text editor to redact any sensitive or irrelevant
bulky content.
There is also a practical problem in general. Binary typescript cannot
be pasted into a pastebin. Some pastebin services have a “typescript”
data type, but this is actually an unfortunate language clash
(“typescript” is actually a programming language, unrelated). A common
use case of /script/ is to capture problems, study the output for
diagnosis, and share the output with expert collaborators. The sharing
is often done with pastebin services. But those UIs only accommodate
raw text.
Bug trackers will accept binary attachments but then others need to
have the tools and knowledge to handle typescript. The mere extra
hurdle dissuades some people from looking at the bug report. Pasting
the output text into the body of a bug report invites more
participation because it’s more convenient for readers.
So a feature is needed to convert typescript into text. I was
surprised to discover that the /scriptreplay/ command does not have a
feature to convert to raw text.