Internxt synchronization does not work in the following cases. Why?

[hixcube]

Introduction: "Synchronization" consists of automatic, continuous, and consistent updating between source and destination: consequently, the addition, modification, or deletion of any object on one side is replicated on the other. This is the definition of the principle of synchronization, not my opinion.

That said, I'd like to understand why, after creating a 2KB text file in the root directory of a storage device:
"D:\New Text File"
After a couple of minutes, the file correctly replicates on the Internxt drive at the path:
C:\Users\User\InternxtDrive - 21d6f245-a419-4844-aeef-003cf67d1f06\DiskD

But if, after another two minutes, I delete the file "D:\New Text File" from the original path (from the source), I expect it to also be deleted, from the Internxt drive at the path:
C:\Users\User\InternxtDrive - 21d6f245-a419-4844-aeef-003cf67d1f06\DiskD

and this doesn't happen. NEVER (!)

Another side of the same coin: if, from the original path (the source), I change the contents of the same 2KB text file "D:\New Text File" by adding more text or deleting part of it, the change is NEVER (!) replicated on the Internxt drive, contrary to the principle of synchronization.

I would like an explanation for this anomalous behavior that invalidates the functionality of Internxt. But I would be even happier if this anomaly were resolved, because it is the basis of synchronization. This is the reason I paid for and am using Internxt.

That said, I'd like to add a couple of things that, if anyone knows, it's because they discovered them on their own, not because Internxt communicated them; in fact, it's not explained in the guides:

1. Zero-sized objects (files and folders) are not replicated on the Internxt drive, even if they have a reason to exist in the source file structure because they have control functions, because they are needed by the program that uses that folder, or because the name of an empty file represents a note I might use to remind myself of something.

2. Although both Windows and Linux have long since overcome the 256-character file path length limitation (258
   by adding \0—the terminating null character, to be precise)—in fact, the actual length that Internxt is able to synchronize appears to be significantly less than 256 characters.

But that's not all... those 256 characters also include the length of Internxt's default local path, which is:
_C:\Users\UserName\InternxtDrive - 21d6f245-a419-4844-aeef-003cf67d1f06_

So if we have a file at the path:
D:\Hardware\Computer\NAS-Synology_DS918+\Purchases\RAM-Disks-RAM_M.2-Cable\RAM_M.2\2nd Purchase\Compatibility-Synology Samsung MZ-V6E250BW SSD 960 EVO, 250 GB, M.2, NVMe, BlackOrange -.jpg

which alone is 188 characters long (200 to be precise) by adding the string:
_C:\Users\UserName\InternxtDrive - 21d6f245-a419-4844-aeef-003cf67d1f06_

The full path, including the file name, becomes:
C:\Users\UserName\InternxtDrive - 21d6f245-a419-4844-aeef-003cf67d1f06\D:\Hardware\Computer\NAS-Synology_DS918+\Purchases\RAM-Disks-RAM_M.2-Cable\RAM_M.2\2nd Purchase\Compatibility-Synology Samsung MZ-V6E250BW SSD 960 EVO, 250 GB, M.2, NVMe, BlackOrange -.jpg

Which is 259 characters. (261 actually)

Which therefore won't be synced, like all files under the same conditions...

[hixcube]

Up, please...

[xbokos]

Same issue here... :(

[hixcube]

Another gem:

I confirm that Internxt cloud upload does not work in the following cases:

1. a) any addition of a new file to a local folder, b) its deletion, c) any changes to the file are - Not replicated in the cloud,

2. files stored locally with paths even shorter than the old, outdated Windows standard of 256 characters to which you must add the length of the fixed string:
   "C:\Users\UserName\InternxtDrive - 21d6f245-a419-4844-aeef-00ABCDE12345" to which you must also add the "nul" character and the terminator at the end of the path, are not uploaded to the cloud.

3. Large files don't upload,

4. Empty folders or files with size 0, (even if they have a specific reason for being there)

5. Files preceded by a period,

6. If a file is moved from Windows Explorer to the local Internxt folder with the intent of uploading it, and the upload fails, the file dies there: it remains "forgotten" in "C:\Users\UserName\InternxtDrive - 21d6f245-a419-4844-aeef-00ABCDE12345*" without being uploaded. To attempt a new, unlikely upload, the file must be deleted before dragging the same file from the local folder to InternxtDrive again, and again, and again...

7. On Android, the nested file and folder structure isn't replicated exactly as it is on devices. On Internxt, files are simply uploaded. Without structure, No hierarchical order.

For days I've been trying to upload a 1.4 GB file for testing: the upload bandwidth initially fluctuates between 0 and 2.1 Mbps, but looking at the connection graph with narrow triangular spikes, you can see that 2.1 Mbps is reached only for an instant, then drops to zero and starts again in an infinite loop. But after a couple of hours, the bandwidth begins to fluctuate between 0 and 8 Kbps, with peaks at 60 Kbps, before completely dropping to zero. Sometimes the Internxt app crashes and I have to start over.

Someone might argue: "It's not necessarily Internxt's fault. The path between your PC and the Internxt server is long, there are many nodes to traverse, and there's a good chance of a bottleneck along the network." Or maybe my ISP is limiting my speed.

If that's the case, someone should explain to me why Uploads to Dropbox or Google Drive are stable between 2.5 and 6.6 Mbps. Even the free 50 GB Mega plan is faster.

Reading my comments here, Internxt support emailed me asking me to attach the contents of the C:\Users\User\AppData\Roaming\internxt-drive\logs folder, which weighs 1.6 GB in total. But first, they should explain how to send them at an upload speed between 0 and 4 Kbps

**Curiously, though—an explanation from Internxt would be needed here—if I drag the same 1.4 GB file from Windows Explorer on my PC to the Windows Explorer window that opens by clicking the Internxt icon in the Windows taskbar, then the globe icon, I can upload the file at a speed varying between 78 and 342 Mbps!

Unfortunately, the result I get in this case is not a syncable file; it's just a snapshot of a file, an image. Frozen in time, not updating, a simple upload. So the million-dollar question: if a simple upload works, why not sync? - PS: Retrying to "sync" the same file 15 minutes later, the upload speed is between 0 and 80 Kbps! **

I'm on FTTH EPON with upload speeds up to 700 Mbps, with a minimum upload speed stated by my ISP of 28 Mbps.