@Derp said:
OR, do them in a temproom, which would theoretically make recalling the poses there impossible once its destroyed.
If they are logged, they can be recalled. It's the security that keeps things from getting out of hand, things that need to be taken into account no matter how the information is recorded. So log the whole game already.
I don't think it's a horrible idea, given the "security" caveat, and the security is going to be part of the game culture. The original post (or original poster-by-proxy) probably doesn't realize they are requesting this, but it's the only way to make it work.
I can think of many ways to make this safer, some of which have been touched upon. "That room only" and "last 10 poses", yes. You can even make the logger forget anything older so that nobody else (staff) can pull the information.
Even "that room only" depends upon determining "that room" to be more unique than the dbref. With how often dbrefs get re-used thanks to temprooms and jobs, the chances that you'll end up in a temproom that has been logged before isn't enough to zero to say it's secure.
My security feature: Turn it on only by request, be noisy about it, and remove anything logged when it's turned off. Automatically turn off if the last person leaves the room. I would use this as an easy way for the game to generate wiki-friendly scene logs, but catching up on poses would be a nice secondary feature.
I would say the rest of you are over-thinking it, but in truth it's because I've been thinking about this for years already and that's how I would do it.
