emdee/tox_profile
2
3
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update 'ToxMultiDevice'

emdee 2022-09-30 18:42:22 +02:00
parent 8152a8ab90
commit 332580ba07
1 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
ToxMultiDevice.md

@ -224,7 +224,7 @@ Conversations that need to be added to the spec:
<grayhatter> then the file will get canceled / "marked as accpeted on a different device" <grayhatter> then the file will get canceled / "marked as accpeted on a different device"
<nurupo> so, Alice accepts and completes the file transfer on her phone <nurupo> so, Alice accepts and completes the file transfer on her phone
``` ```
[h][^8][i][^9][j][^10] [h][^8] [i][^9] [j][^10]
``` ```
<nurupo> hm <nurupo> hm
<nurupo> ok <nurupo> ok
@ -265,30 +265,32 @@ Conversations that need to be added to the spec:
* Ability to address device id explicitly * Ability to address device id explicitly
* [a][^1]Does this design document define a way in which friends (and perhaps groups) are to be synced? And how would friend/group syncing work across multi-devices that don't have a common time base? ## Footnotes
* [a][^1] Does this design document define a way in which friends (and perhaps groups) are to be synced? And how would friend/group syncing work across multi-devices that don't have a common time base?
* [b][^2] I haven't fully decided on the final spec for this question. * [b][^2] I haven't fully decided on the final spec for this question.
Currently my plan is to retain information about changes as a numerical delta, and use the largest delta. But as I haven't started on this section, really I have no idea. Currently my plan is to retain information about changes as a numerical delta, and use the largest delta. But as I haven't started on this section, really I have no idea.
* [c][^3]What about in the case of an A/V call? Does that get broadcast to call connected clients or only the last 3? A tox client running on a mobile device that had not sent a user-generated message missing a call would be bad. * [c][^3] What about in the case of an A/V call? Does that get broadcast to call connected clients or only the last 3? A tox client running on a mobile device that had not sent a user-generated message missing a call would be bad.
* [d][^4]I'm likely to drop that idea in total. * [d][^4] I'm likely to drop that idea in total.
Currently toxcore sends everything to all devices. Currently toxcore sends everything to all devices.
* [e][^5]With other services such as Discord, when a call comes in depending on what is on, I could have two PCs, a laptop and cellphone all ring, but whatever device I answer on obviously gets the call. * [e][^5] With other services such as Discord, when a call comes in depending on what is on, I could have two PCs, a laptop and cellphone all ring, but whatever device I answer on obviously gets the call.
* [f][^6]how is primary toxID different from any other ID? which device is the primary one? as far as I understood they are all equal. * [f][^6] how is primary toxID different from any other ID? which device is the primary one? as far as I understood they are all equal.
* [g][^7]I'm not sure there's going to be anything like a primary ID in the final source. When discussing it, the idea of a master device came up as a security tool. But the longer I consider it, the less I think it'll help at all * [g][^7] I'm not sure there's going to be anything like a primary ID in the final source. When discussing it, the idea of a master device came up as a security tool. But the longer I consider it, the less I think it'll help at all
* [h][^8]Does it make sense to think about sending the file to both * [h][^8] Does it make sense to think about sending the file to both
clients, if the user accepts on multiple devices? Especially for clients, if the user accepts on multiple devices? Especially for
bigger files or multiple recipients a P2P protocol (e.g. torrent) bigger files or multiple recipients a P2P protocol (e.g. torrent)
may be useful. may be useful.
* [i][^9]Yeah, I've given that a little thought. The current idea * [i][^9] Yeah, I've given that a little thought. The current idea
floating around has been to implement something torrent like inside floating around has been to implement something torrent like inside
group chats. Maybe we could use that as well? As far as multiple group chats. Maybe we could use that as well? As far as multiple
devices, what I think is best is transfer the file to the first to devices, what I think is best is transfer the file to the first to
@ -296,7 +298,7 @@ Currently toxcore sends everything to all devices.
way the sender doesn't have to spend the extra data for the way the sender doesn't have to spend the extra data for the
receivers convenience. receivers convenience.
* [j][^10]I like that idea. Especially if one thinks about those users * [j][^10] I like that idea. Especially if one thinks about those users
on a phone with limited traffic. You wouldn't want to use all your on a phone with limited traffic. You wouldn't want to use all your
available data just so others can sync. You could add a button on available data just so others can sync. You could add a button on
top of lets say a picture saying "sync with my other devices" to top of lets say a picture saying "sync with my other devices" to