Currently, configuration files are per-conversation, for both clients and peers. While this makes sense from the perspective of the internal logic, since each conversation is managed mostly independently, it would reduce redundancy in information represented and ease of management if an entire user was configured in a single file with multiple conversations.
Currently, configuration files are per-conversation, for both clients and peers. While this makes sense from the perspective of the internal logic, since each conversation is managed mostly independently, it would reduce redundancy in information represented and ease of management if an entire user was configured in a single file with multiple conversations.
Currently, configuration files are per-conversation, for both clients and peers. While this makes sense from the perspective of the internal logic, since each conversation is managed mostly independently, it would reduce redundancy in information represented and ease of management if an entire user was configured in a single file with multiple conversations.
See also: #20
Progress via
8c852bbd4b.Done with
9e8b242925.