#QTOX NOT SAVING SETTINGS OFFLINE#
#QTOX NOT SAVING SETTINGS SERIES#

If a user does want to share a public inbox, messages to the user should be encrypted with the user’s public key.

#QTOX NOT SAVING SETTINGS OFFLINE#

Any sort of PUSH notification mechanism can be added by the user on top of SAFE but can expose people thru timing attacks (disconnecting a person’s wifi and seeing them go offline in a chatroom). If you want to VERIFY that the person on the other side is truly who you think it is, you should use a side channel to do so (such as a video call or chat where you ask them to reminisce about something).įinally, messages should be left in mailboxes on SAFE which the recipient might check, but SAFE doesn’t link the recipient to the mailbox (steganography). It is more a function of the client side. How they get these can vary - it can be in a side channel or with the help of SAFE. They should also have pairwise keys for authentication, so they could have off the record messaging and deniability / unlinkability. People should have private “pairwise” identifiers for each other, rather than global ones. Consider how much SPAM people get just because their email address is exposed. If you want things to be truly SAFE, have a different mechanism than the global public URL/email/DNS scheme for messaging people. Ideally certain Safe Network social protocols or one such protocol will dominate and we’ll have complete user independence and the ability to connect with anyone on Safe Network with freedom to choose the way we each do this that doesn’t depend on anyone else, including the people we want to connect with. Safe Network is a platform which will have many different apps appealing to different people, and so can generate a snowball effect which feeds into and benefits from the viral nature of its social protocols and apps. I think Safe Network has the best shot at this because it is not just one chat app or protocol that will be driving adoption.

adoption, because most people and their contacts are on Facebook and Twitter.

an open protocol so users are not locked into one app or service.

The tough part is no longer lack of p2p messaging, but twofold I think: There are a few now, one based on nostr being discussed recently on my twitter. I’m currently using qtox, which as I understand is fully decentralized - no central server. OffLine: Not sure how one would be able to send message on the network if not connected to it. The Secure Messaging App for the network will actually be simpler to implement as most of the hard stuff (encryption etc) is part of the network. So you could write the (large) message to the network as a file and send the datamap to the other person, if only a short message then prob all contained in the message.Īs to recipient ID becoming known then the Secure Messaging App could use determinable IDs (like wallets do with BTC addresses) so then the recipient can get the messages but no way for nodes/elders that are compromised to know that the IDs belong to the one recipient. Maybe can tag the person who knows (if he doesn’t) For instance when someone orders off a shop there needs to be a message to inform the shop owner. Needs to be an ID since that is how Safe identifies the recipient. There will be of necessity be a messaging protocol allowing people to send a message to an ID. There is a messaging component to the network for internode communication. Maybe someone could think of a way to batch them so it wouldn’t be as expensive.Īnyways, what are your thoughts on instant messaging through SAFE? I suppose that might have to use the PUT method. I’m not sure how this would work for offline messages, though. When we get a message, the client would display it to us, and if it’s configured to save logs it would put several in one batch before making a PUT. When we log on, we would connect to a server, but it wouldn’t have to be the same one every time. We would store our identifying information and credentials on the safe network.

#QTOX NOT SAVING SETTINGS SERIES#

It sounds like there’s going to be a lot of overhead involved with PUTs, so a long series of short, fast messages isn’t the ideal use case. One way to do it would be simply by PUTing the messages that are intended for a given recipient at an agreed-upon key.

I feel like the SAFE Network will make that a possibility.

What we need is an open source protocol that’s truly decentralized, encrypted, extensible. When your home server goes down, you lose your account, and unlike with email, there aren’t many large reliable institutions offering service on these networks. I prefer to think of them as polycentric rather than decentralized. There are “decentralized” solutions like XMPP and Matrix, but these are reliant on “home servers”. When you leave one, you lose all your contacts.

Most of them are proprietary and walled gardens. Right now, I need so many different messenger clients to keep in touch with people. I’m really hoping the SAFE Network will offer a solution to the instant messaging problem.

Qtox not saving settings