You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2019. It is now read-only.
Let's say you only want to be seen only by one contact. This can be done by removing the contact from the list, but thats quite anoying because it forces to add the contact again with another friend request. It would be cool if antidote allowed to 'disable' contacts by choice.
The text was updated successfully, but these errors were encountered:
Thanks, that's a nice idea, however I see few issues. Will think about this more in future.
To add friend again you have to know her full Tox ID (including nospam). Friend can change nospam at any time, in that case you won't be able to add him again.
Also it may be confusing that you won't receive messages from "disabled" contacts.
I dont know too much about the internals of tox but i assume the client is the one that notifies its availability to the peers. Just blocking that should be enough to disable a contact. No need to add them again, no?
On 7 Apr 2017, at 12:58, Dmytro Vorobiov ***@***.***> wrote:
Thanks, that's a nice idea, however I see few issues. Will think about this more in future.
To add friend again you have to know her full Tox ID (including nospam). Friend can change nospam at any time, in that case you won't be able to add him again.
Also it may be confusing that you won't receive messages from "disabled" contacts.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Let's say you only want to be seen only by one contact. This can be done by removing the contact from the list, but thats quite anoying because it forces to add the contact again with another friend request. It would be cool if antidote allowed to 'disable' contacts by choice.
The text was updated successfully, but these errors were encountered: