FolksBackendA single backend to libfolks, such as Telepathy or evolution-data-server. Each backend provides FolksPersonas which are aggregated to form FolksIndividuals.
FolksAntiLinkableInterface for FolksPersona subclasses from backends which support storage of, anti-linking data.
FolksUtils — Utility functions to simplify common patterns in Folks client code.
FolksPersonaRepresents a "shard" of a person from a single source (a single FolksBackend), such as an XMPP contact from Telepathy or a vCard contact from evolution-data-server.
FolksObjectCacheA generic abstract cache for sets of objects. This can be used by subclasses to implement caching of homogeneous sets of objects. Subclasses simply have to implement serialisation and deserialisation of the objects to and from GVariants.
FolksRole — Role a contact has in an organisation.
FolksIndividualA physical person, aggregated from the various FolksPersonas the person might have, such as their different IM addresses or vCard entries. An individual must always contain at least one FolksPersona.
FolksPresenceDetailsInterface exposing a FolksPersona's or FolksIndividual's presence; their current availability, such as for chatting.
FolksAbstractFieldDetails — Object representing any type of value that can have some vCard-like parameters associated with it.
FolksLocation — A location. Typically latitude and longitude will be based on WGS84. However, folks often has no way of verifying that and just has to assume it's true.
FolksImFieldDetails — Object representing an IM address value that can have some parameters associated with it.
FolksDebug — Manages debug output and status reporting for all folks objects.
FolksIndividualAggregatorStores FolksIndividuals which have been created through aggregation of all the FolksPersonas provided by the various FolksBackends.
FolksLocalIdDetailsThis interface represents the list of "iid"s corresponding to FolksPersonas from backends with write support so that they can be linked.