Pidgin Setup for Library IM Services

Getting Started | Centralized Logging | Usage Statistics | Meebo Me Widget

Instructions PURPLEHOME Environment Variable for Centralized Logging To save Pidgin transcripts/logs in a centralized location, set an environment variable. Pidgin will also store all of its settings at this location, along with the logs. The environment variable must be called PURPLEHOME. Enter a file path to specify where logs will write. For example, we use the PURPLEHOME variable: g:\pidginstuff You can set this variable manually, or you can automate this through a registry edit. For instance, your systems staff might call the registry edit in a user's login script. To set the environment variable manually: Right-click on My Computer   Go to Properties --> Advanced tab Click Environment Variables button    In System Variables (second box down), set a variable called PURPLEHOME with its Value being the path to the desired location (Example: g:\pidginstuff). To make the registry edit: Create a text file ending in *.reg (for instance, pidgin.reg). Inside the text file, paste the following text. To run the registry edit, double-click the text file, or call it from a login script. Of course, change the PURPLEHOME location to suit your needs. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "purplehome"="G:\\PIDGINSTUFF" Once the variable is set, copy the files that contain Pidgin's settings to the network location you specified. Do this so that, when Pidgin opens, it can find account settings, populate its buddy list, etc. Highlight and copy the entire directory to your centralized location, starting with AND including c:\documents and settings\username\application data\.purple Your new directory of Pidgin transcripts and settings will then include the following folders and files: g:\pidginstuff\.purple\logs g:\pidginstuff\.purple\icons g:\pidginstuff\.purple\blist.xml g:\pidginstuff\.purple\accounts.xml Pros and cons of centralized logging Pros 1. Data safety If you use a network drive that is backed up, your data is safer than it would be on an individual hard drive. 2. Simultaneous multi-staff user access Run Pidgin on multiple computers. So long as the environment variable is set to the proper location, all computers will use the same settings and save their logs to the same location. 3. Staff access to transcripts All staff can get to the transcripts if they are set to write to a networked drive. This is useful for training purposes. Cons 1. Logging of personal IMs Staff must understand that all IMs done through Pidgin on a computer with this set are logged, including any personal IMs through Pidgin. One solution is to train staff to use Pidgin for public service and use another application (such as Trillian or a native IM client such as AIM) for personal IMing. 2. Settings vulnerability If staff change Pidgin settings to one computer with the PURPLEHOME variable set, changes apply to all computers with the PURPLEHOME variable. This means, if TarHeelLibrarian2390 logs in to AIM using Pidgin, when another user starts Pidgin on a PURPLEHOME computer, it automatically logs in as TarHeelLibrarian2390.

Proceed to Usage Statistics >>