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
I was imagining a client UI with a new option called "Allow data" or something, that could allow for users to (very slowly) upload images or generic binary data in roughly 5kb chunks (burst of 25 messages, broken up into 5 sub-bursts of 5 messages, each 200 bytes) and could be repeated by other nodes that also allow data. The first packet would contain the number of chunks, and the filename/type. The client could then display a loading bar as each chunk comes in. It would be pretty useful, and on short turbo you could send a 20kb jpeg in seconds. (Even at 1 second per message, closer to medium-fast, that would only take 1.5 minutes, anything under 10 - 15 minutes could be incredibly useful imo)
Each "sub-burst", all receiving nodes directly connected to the origin would send a confirmation back, repeat the sub-burst out, and await the next sub-burst. After 5 of them, the chunk will be rendered by all client devices, checked for errors, and another confirmation sent back to the origin. If everyone got all the data correctly, it moves on to the next chunk, if anyone (that has the "allow data"mode on) didn't get the message correctly, the whole process repeats until everyone has all of it. If the same node doesn't correctly receive the data 3 times, it just should just move on anyways, so it doesn't hold up the others. Each node should only ever really be holding the current sub-burst and the previous sub-burst, which is only a few kB at a time. Maybe leave a gap every sub-burst for other messages to come through?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I was imagining a client UI with a new option called "Allow data" or something, that could allow for users to (very slowly) upload images or generic binary data in roughly 5kb chunks (burst of 25 messages, broken up into 5 sub-bursts of 5 messages, each 200 bytes) and could be repeated by other nodes that also allow data. The first packet would contain the number of chunks, and the filename/type. The client could then display a loading bar as each chunk comes in. It would be pretty useful, and on short turbo you could send a 20kb jpeg in seconds. (Even at 1 second per message, closer to medium-fast, that would only take 1.5 minutes, anything under 10 - 15 minutes could be incredibly useful imo)
Each "sub-burst", all receiving nodes directly connected to the origin would send a confirmation back, repeat the sub-burst out, and await the next sub-burst. After 5 of them, the chunk will be rendered by all client devices, checked for errors, and another confirmation sent back to the origin. If everyone got all the data correctly, it moves on to the next chunk, if anyone (that has the "allow data"mode on) didn't get the message correctly, the whole process repeats until everyone has all of it. If the same node doesn't correctly receive the data 3 times, it just should just move on anyways, so it doesn't hold up the others. Each node should only ever really be holding the current sub-burst and the previous sub-burst, which is only a few kB at a time. Maybe leave a gap every sub-burst for other messages to come through?
Beta Was this translation helpful? Give feedback.
All reactions