The Peer Data Structures

not to be confused with P2P.

net/storage Profile etc

The Peer Data Structure

_p[ uniform ] = ({ pplflags, presence, alias, channelset, custom });

... or is the presence going to get stored in the context slaves of the people? we're going to have context slaves per channel anyway.

The History

Access via PSYC

Currently you can obtain a dump of the data structures in either a PSYCish or JSON format, using either a _request_do_list_peers or _request_do_list_peers_JSON method as explained on Command.

The result of a _request_do_list_peers_JSON looks something like this. That means we have the JSON data in the body of the packet. The JSON output lacks the nicknames from your personal nickspace, but maybe your application doesn't need them. This is a very simple structure that doesn't contain trust, expose or other nifty settings.

:_source     psyc://localhost/~symlynx
:_target     psyc://localhost:-47986/

[ {"_contact":"","_level_notification":8}, {"_contact":"symlynx","_level_display":6}, {"_contact":"k","_level_notification":8}, {"_contact":"fippo","_level_notification":1}, {"_contact":"lynx","_level_notification":8}, {"_contact":"l","_level_notification":8} ]

Here's how it looks like without JSON. It gets quite verbose as a message is generated for each peer, but this has the advantage of being mostly user readable using the psyctext template in the body.

:_source     psyc://localhost/~symlynx
:_target     psyc://localhost:-38178/

:_level_display      -
:_nick       Example
:_level_notification 8
:_level_trust        -
:_level_expose       -
[_acquaintance] known as [_nick]: D[_level_display], N[_level_notification], T[_level_trust], E[_level_expose].

TODO: All the levels in here should be converted to degrees!