Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Aug 13, 2015, 4:56:34 PM (8 years ago)
- Author:
-
mmcco
- Comment:
-
cleanup
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v55
|
v56
|
|
| 14 | 14 | |
| 15 | 15 | == Clean-up ideas == |
| 16 | | * We have 344 `#if 0` blocks in the code base - are all of them still relevant and necessary? |
| | 16 | * Drop many `#if 0` blocks. |
| 17 | 17 | * It seems like the typing status functionality could be condensed a lot, or that "API" could be defined to something more useful/broad. The IM conversation API (found in `libpurple/conversationtypes.h`) consists of: |
| 18 | 18 | * '''2''' core functions |
| … |
… |
|
| 135 | 135 | Privilege separation is one of the easiest ways to improve Pidgin's security. |
| 136 | 136 | |
| 137 | | After initial library loading, there are three types of file access for Pidgin: |
| | 137 | After initial library loading, there are four types of file access for Pidgin: |
| 138 | 138 | * access to libpurple-specific files in `~/.purple/` |
| 139 | 139 | * access to files in arbitrary locations for file transfers |
| 140 | 140 | * GTK-related files (icons, etc.) from `/usr/share` |
| | 141 | * access to binaries (these should probably be replaced or removed) |
| 141 | 142 | |
| 142 | 143 | Of course, the third does not apply to libpurple. |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!