Hi there, On Mon, Jul 1, 2019 at 11:36 AM t3sserakt <t...@posteo.de> wrote: > Hi Marcos, [...]
Thanks very much for your reply, it was quite elucidative. I know about the aims of secushare (I've been lurking and trying to watch its development, as my particular interest on it is really a the realization fully decentralized virtual world, which is what groupchat could be the start of). However, when I learned about groupchat, and looking into its code, I saw no relation between it (as it is, at least) and secushare: it looks to me as being fully a client-server model... So, what I was failing to see was that there is a plan to evolve what groupchat currently is into a serverless, distributed chat system. The 'main task' to achieve that (and the one I'm personally more interested in) seems to be this one: > get rid of the groupchat server, but using available (being online) peers in > a group to do the multicast. This obviously needs peers of the group being > online to have asynchronous messaging. Is there something written up explaining in more detail what, in practical terms, does this mean? A list of tasks to implement, or something like that? As it is, I have several ideas on how to contribute with groupchat as it currently is, but that would be mostly working on the current usability *with* the server model, which seems like a bit of a waste of time, considering the goals for groupchat. Unfortunately, I won't be able to attend to the weekly meetings. Are there minutes, logs or recordings of those meetings? Thanks for taking your time helping me understand more about the goal here, and for your work on secushare in general, -- Marcos Marado _______________________________________________ GNUnet-developers mailing list GNUnet-developers@gnu.org https://lists.gnu.org/mailman/listinfo/gnunet-developers
