Re: Messenger working

[TheJackiMonster]

Hi,

I'm currently working on developing a proper ui for the messenger
service. But more important is to develop a library which provides
easier usage of all the features (for example sharing files, sending
text without manual fragmentation and managing contacts + groups).

My current progress can be tracked on Gitlab
( https://gitlab.com/gnunet-messenger ) which I find easier to manage.
Also because it's only an abstraction layer of multiple given services
of GNUnet, I don't think it needs to be part of framework itself. Maybe
the client-side chat library and both example implementation with GTK
and ncurses for cli can be moved later on to repositories on
gnunet.org.

So if you think about integrating something into pidgin to use the
messenger service. Maybe it makes more sense to use the chat library
which will be more fitting the typical messenger/chat application.

Also if you think some functions or features could be helpful, let me
know.

Happy hacking
Jacki

On Mon, 2021-05-31 at 12:41 +0200, Tobias Platen wrote:
> I got the gnunet messenger working on my laptop.
> The next test will be installing GNUnet on a second computer
> then invoke the messenger using ssh. I'm also thinking about
> using pidgin/libpurple as a ui for the messenger. I did not test
> ROOMKEY and IDENTITY yet. 
> 
> * Welcome to the messenger, 'anonymous'!
> * You try to open a room...
> * You joined the room.
> [95D7GG] * 'anonymous' joined the room!
> [K6G3HE] * 'anonymous' joined the room!
> [K6G3HE] * 'anonymous' gets renamed to 'anonymous'
> [95D7GG] * 'anonymous' gets renamed to 'anonymous'
> aaaaaaaa
> [95D7GG] * 'anonymous' says: "aaaaaaaa"
> hallo 
> [95D7GG] * 'anonymous' says: "hallo"
> [K6G3HE] * 'anonymous' says: "welt"
> 
> Open and connect to rooms using the MESSENGER to chat.
> Arguments mandatory for long options are also mandatory for short
> options.
>   -c, --config=FILENAME      use configuration file FILENAME
>   -d, --door=PEERIDENTITY    peer identity to entry into the room
>   -e, --ego=IDENTITY         identity to use for messaging
>   -h, --help                 print this help
>   -L, --log=LOGLEVEL         configure logging to use LOGLEVEL
>   -l, --logfile=FILENAME     configure logging to write logs to
> FILENAME
>   -p, --private              flag to enable private mode
>   -r, --room=ROOMKEY         key of the room to connect to
>   -v, --version              print the version number
> Report bugs to gnunet-developers@gnu.org.
> Home page: http://www.gnu.org/s/gnunet/
> General help using GNU software: http://www.gnu.org/gethelp/
>

signature.asc
Description: This is a digitally signed message part