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
Since the shared-phrase is user chosen it is possible that more than 1 send and receive party use the same phrase at the same time on the same helper server.
Right now this could cause either
mixup of receiver B receiving data from sender A and vice versa
both senders to "connect" to each other and sending data at each other while the receivers get no data at all
The solution would be to let the helper server generate a phrase that is not in use at the moment and send it back to the sender. The sender then can forward the phrase to the receiver and everything else then works like usual.
I'll see what I can do. I would really like to keep it in such a way that order of connection of sender and receiver is irrelevant, but I don't think that is possible. This won't be top priority until some more sending and receiving issues are fixed, but once those are done, I'll fix this one.
About croc: QFT is peer-to-peer, croc uses a relay.
Won't fix, i dont want to use random phrases as those generally suck, maybe i will find a nice solution soon, but for now, i don't think i have a solution here.
Since the
shared-phrase
is user chosen it is possible that more than 1 send and receive party use the same phrase at the same time on the same helper server.Right now this could cause either
mixup of receiver B receiving data from sender A and vice versa
both senders to "connect" to each other and sending data at each other while the receivers get no data at all
The solution would be to let the helper server generate a phrase that is not in use at the moment and send it back to the sender. The sender then can forward the phrase to the receiver and everything else then works like usual.
This reminds me a lot of croc.
The text was updated successfully, but these errors were encountered: