A few weeks back my department re-organized. Along with splitting into separate divisions, each division now has a separate SourceSafe repository. It's more organized that way.
Today, I logged onto another division's SS database to look at a project. I used the "guest" account, which is read-only. I checked out a project and looked at it in VS2005 (yes, really). When I return to MY project in VS2005 it has now set the VSS binding to use the guest account, so I can't actually check out any files to actually, you know, do work. The only fix I've found is to drop the project binding, then re-bind them. It's not that big of an inconvenience, except that this could potentially repeat every time I have to look at a project that resides in a different SS database.
WTF #1: Changing the login credentials for a project without prompting me first.
WTF #2: Changing the login credentials for a project that is bound to a different SS database. Yes, this database has a guest account with the same password. No, it is not the appropriate thing to do.