GNUnet Messenger API: December 2023
Hey again, I’ve completed the necessary steps to solve the issue I talked last time. There are now three options for service configuration on each peer to specify how many peers need to manage message exchange actively at minimum ( MESSENGER_MIN_ROUTERS ), whether the own peer takes part in this functionality temporarily when required to achieve this minimum ( MESSENGER_AUTO_ROUTING ) and whether the own peer automatically reconnects to other peers keeping at least one external connection ( MESSENGER_AUTO_CONNECTING ). More details can be read in the bugtracker. This should improve the reliability of connections for applications quite a bit. Because those changes adjust defaults to always have at least three peers managing message exchange in a chat room. The exception is when less peers are connected to a chat room at all which should only be valid for private or direct chats with only one other person. One remaining aspect of this issue is that I still need proper testing whet