Clearly define API end-points for privates
Clearly define API end-points for privates

We updated the architecture document to reflect that conversations can
be both privates and channels and they are addressed by the tuple (type,
target).

dionyziz/ting,mbalamat/ting,dionyziz/ting,mbalamat/ting,odyvarv/ting-1,odyvarv/ting-1,sirodoht/ting,sirodoht/ting,dionyziz/ting,dionyziz/ting,gtklocker/ting,gtklocker/ting,VitSalis/ting,VitSalis/ting,mbalamat/ting,odyvarv/ting-1,gtklocker/ting,sirodoht/ting,sirodoht/ting,VitSalis/ting,VitSalis/ting,gtklocker/ting,mbalamat/ting,odyvarv/ting-1