2 do we need to export functions in some special way?

     2 * due to server bugs, some offline buddies are still notified on publication,

     3 startup/shutdown hook to inform other modules, that they should free/register handlers?

     3   causing error reply, that pep accepts as event. check message type/presence of error tag.

     4 due to server bugs, some offline buddies are still notified on publication, causing error reply, that pep accepts as event. check message type/presence of error tag.

     4 * do something about information duplication in CMakeLists

     5 * check input/output for validity, where applicable

     6 * extract common code into one place

     7 * either put request methods into ui modules (compatibility measure) or rename them into pep_*

     8 * add avatar

     9   * pep_avatar, avatar_cache, avatar, aavatar (separate)

    10     *       hook_avatar_metadata_in                               @ pep_avatar  

    11           | hook_avatar_need_data_in (or symbol-resolved request) @ avatar_cache  

    12           V hook_avatar_data_in                                   @ pep_avatar  

    13             hook_avatar_in                                        @ avatar_cache

    14     * (!!!) how to handle outgoing event? what and where should do what?

    15   * handle url avatars (curl)

    16   * report absence of avatar