View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007146||GNUnet||messenger service||public||2022-01-07 18:23||2022-03-15 19:34|
|Summary||0007146: messenger-cli and messenger-gtk feature request: integrate with GNUnet conversation|
|Description||GNUnet conversation exists in a standalone manner, but it feels to me like an obvious place to have it available is on messenger(cli or gtk): there we already manage contacts and "text conversations", so it makes sense to have in there the option to also start a "conversation" (secure voice communication, as defined in the description of Conversation).|
|Tags||No tags attached.|
This is definitely something I have though about. Conversation relies on GNS more heavily than the messenger service at the moment but both have a common dependency with the IDENTITY service and its EGOs as accounts/identities. So adding an integration of conversation to those applications requires libgnunetchat to utilize GNS for contact management (which is something I already plan to implement) and the IDENTITY service need to be used to aquire the users EGO (because this is only visible to the messenger service for now, not to libgnunetchat).
For now the core functionality is texting and sending files because I'm working on the things given to NLnet as requirements to complete functionality ( https://nlnet.nl/project/GNUnet-Messenger/ ).
A brief list of features libgnunetchat needs is the following:
- transmitting files (WIP)
- discover contacts (WIP)
- exchange/verify contacts (WIP)
- open private chats (works)
- create group chats (works)
messenger-gtk and messenger-cli are effectively only the interfaces to this library.
This feature could be implemented in current state, I think because I managed to integrate using the namestore and GNS for contact management and exchange. So it's not really more complicated than opening a conversation connection, potentially reusing peer information from the messenger room records.
I will still focus on the core functionality for now. Because a feature like this would definitely some additional UI changes for sure to be usable inside the application.