{"action":"created","issue":{"url":"https://api.github.com/repos/qTox/qTox/issues/3758","repository_url":"https://api.github.com/repos/qTox/qTox","labels_url":"https://api.github.com/repos/qTox/qTox/issues/3758/labels{/name}","comments_url":"https://api.github.com/repos/qTox/qTox/issues/3758/comments","events_url":"https://api.github.com/repos/qTox/qTox/issues/3758/events","html_url":"https://github.com/qTox/qTox/issues/3758","id":180238711,"number":3758,"title":"[feature suggestion] Show QR codes for the contact ToxIDs, not only for user's own ToxID","user":{"login":"yurivict","id":271906,"avatar_url":"https://avatars.githubusercontent.com/u/271906?v=3","gravatar_id":"","url":"https://api.github.com/users/yurivict","html_url":"https://github.com/yurivict","followers_url":"https://api.github.com/users/yurivict/followers","following_url":"https://api.github.com/users/yurivict/following{/other_user}","gists_url":"https://api.github.com/users/yurivict/gists{/gist_id}","starred_url":"https://api.github.com/users/yurivict/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yurivict/subscriptions","organizations_url":"https://api.github.com/users/yurivict/orgs","repos_url":"https://api.github.com/users/yurivict/repos","events_url":"https://api.github.com/users/yurivict/events{/privacy}","received_events_url":"https://api.github.com/users/yurivict/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/qTox/qTox/labels/invalid","name":"invalid","color":"e6e6e6"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-09-30T07:31:16Z","updated_at":"2016-09-30T10:09:43Z","closed_at":"2016-09-30T07:36:48Z","body":"I wanted to add the same user to Antox, but Antox fails to accept the text (messaged and pasted) ToxID due to some bug. It would have been possible to scan it from the screen, but qTox doesn't show QR codes for the contacts ToxIDs.\r\n\r\nI think qTox should show QR codes for contacts for flexibility."},"comment":{"url":"https://api.github.com/repos/qTox/qTox/issues/comments/250708853","html_url":"https://github.com/qTox/qTox/issues/3758#issuecomment-250708853","issue_url":"https://api.github.com/repos/qTox/qTox/issues/3758","id":250708853,"user":{"login":"initramfs","id":3128050,"avatar_url":"https://avatars.githubusercontent.com/u/3128050?v=3","gravatar_id":"","url":"https://api.github.com/users/initramfs","html_url":"https://github.com/initramfs","followers_url":"https://api.github.com/users/initramfs/followers","following_url":"https://api.github.com/users/initramfs/following{/other_user}","gists_url":"https://api.github.com/users/initramfs/gists{/gist_id}","starred_url":"https://api.github.com/users/initramfs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/initramfs/subscriptions","organizations_url":"https://api.github.com/users/initramfs/orgs","repos_url":"https://api.github.com/users/initramfs/repos","events_url":"https://api.github.com/users/initramfs/events{/privacy}","received_events_url":"https://api.github.com/users/initramfs/received_events","type":"User","site_admin":false},"created_at":"2016-09-30T10:09:43Z","updated_at":"2016-09-30T10:09:43Z","body":"@yurivict The Tox ID and the public key differs in that the Tox ID has additional information like the nospam code and a checksum. The very idea of attaching a nospam code is such that friend requests can only be made to you by having a valid, up-to-date tox ID. Without such a construct, if your public key actually gets out (goes *public*), you could be faced with a torrent of friend requests that you can't stop (you can ignore them, but you can't stop them coming in). As such, the best way I understand it, is that the nospam code is there to work as a blocking filter, in which unsolicited friend requests are simply dropped. The checksum itself is pretty trivial, it's basically there to validate data entry before submitting into toxcore.\r\n\r\nIf you look at the usecase of having the ability to \"add\" a friend at any time (despite already have traded PKs) this is usually limited to having tox running multiple different accounts (on potentially multiple devices). In the first case where tox is running on multiple accounts on the same host, the idea is to provide exclusion between each account (you shouldn't be able to tie one account to another). As such, there would have been no way to add a friend via PK alone on your second account. In the case of having a single alias for multiple devices, this is currently being worked on in a separate issue in which IIRC you will only have one tox ID between all devices and friends/messages may be automatically syned across approved devices, eliminating the manual process of \"readding\" a friend."}}
{"actor":{"display_login":"initramfs"}}