A few questions and suggestions after switching from Air Explorer

Hello!
I decided to look for alternative options to Air Explorer and came across this app. I really liked it, thank you for developing it!
But I’ve got a few questions/suggestions:

  1. After comparing files, you can select files for transfer, but you can’t select all files at once with a single button. It would be great to be able to check the boxes next to the files you want to sync.
  2. It would be useful to see the time taken for file comparison/transfer.
  3. During file comparison, there’s only a close button. It would be great to have a collapsed panel.
  4. Could you please tell me whether hasher populates the table during comparison? Or only during synchronization?
  5. Will the Russian language be added?
  6. Was AI (and to what extent) used to write the code?
  7. Could you tell me how the work with hasher is set up? How does it understand that the source file has been modified?

For each issue, I am ready to provide photos/videos showing what I would like the app to look like.

Hello, and welcome! Thank you for trying RcloneView and for the detailed list. Here are answers in order.

1. Selecting all files after a comparison

There is no Select All button or per-row checkboxes yet. What you can do today:

  • Click the first row, scroll to the end, and Shift+click the last row to select everything in between.
  • Ctrl+click adds or removes single rows.
  • The Copy buttons only copy the selected rows that need copying in that direction (files that exist on one side only, or that differ). Hover over a Copy button to see how many files and how much data it will copy.

We have added Select All and per-row checkboxes to our list.

2. Time taken for comparison and transfer

While Compare copies files it shows the speed and the time left, but not the total time for the comparison or for the copy. (Jobs do record it: Job Manager > History has a “Time Spent” column.) We have added this for Compare to our list as well.

3. Collapsing the Compare window

Right now Compare opens on top of the main window, and the main window can’t be used until you close it. We have added your request to our list: collapse it and keep working while the comparison or copy continues.

For 1, 2 and 3: we would be grateful for your input. If you send us your ideas, including the photos or videos you offered (how this looks in Air Explorer and what you would like to see in RcloneView), we will review them carefully and reflect them in RcloneView.

4 and 7. hasher

First, Compare only asks for hashes when “Use hashes for comparison” (bottom left of the Compare window) is checked. Otherwise it compares names and sizes, and hasher isn’t involved.

When it is checked, Compare lists both folders with hashes, and hasher answers each file like this (tested with rclone 1.75.1):

  • If the wrapped remote supplies that hash itself, hasher passes it through.
  • If the cache has a value whose fingerprint still matches the file, hasher returns it.
  • If the wrapped remote can compute the hash but slowly (a local disk, for example), it is computed now and stored in the cache. So in that case, comparing does fill the cache.
  • If the file is smaller than auto_size, hasher reads it now and stores its hashes. auto_size is 0 (off) by default.
  • Otherwise (e.g. hasher over a cloud or crypt remote that has no such hash, and the file isn’t cached), it returns no hash and the cache is not filled.

The cache is filled whenever a file passes through hasher in full: uploading through hasher, or downloading a whole file through it. So a copy or sync through the hasher remote fills it for the files it transfers. Files that a sync only checks are handled the same way as in Compare. To fill the cache for everything at once, run rclone hashsum MD5 --download yourhasher:path. In our test the --download flag was needed: without it, uncached files came back blank.

How hasher knows a file changed: each cached value is stored with a fingerprint of the file: its size, its modification time (if the wrapped remote supports it), and the wrapped remote’s own fast hash (if it has one). If the file’s current fingerprint doesn’t match, the cached value is not used. Uploads, deletes and server-side moves through hasher update the cache too. max_age controls how long values are kept (default off, meaning they never expire). One limitation to be aware of: if a file is changed without going through hasher (by another app, or directly on the wrapped remote) and its size and modification time stay exactly the same, hasher still returns the old hash.

One more thing we found while checking this: with “Use hashes for comparison” checked, if one side has a hash for a file and the other side returns none (for example a file not yet in the hasher cache), Compare currently shows the pair as different even when the contents are the same. rclone check instead reports these as “hashes could not be checked” and matches them by size. We will look into making Compare behave the same way. Until then, a “different” result on a not-yet-cached file may just mean that hasher had no hash for it.

5. Russian

RcloneView is currently available in English, German, Spanish, French, Indonesian, Japanese, Korean and Chinese (Simplified and Traditional). We will add Russian in the next version.

6. AI

Yes, we use AI in development, and we review the changes ourselves.

Thanks again, and we look forward to your feedback!

Thank you for your time. I will try to describe the problems I see at the moment in this point.

  1. When logging in, Yandex Cloud does not allow you to select an account after the first login → success and the second Yandex account are immediately redirected to the first account
    Here, I first created an account called Test. Then I decided to add a second account, but I was immediately redirected to the ‘Success’ page and the account 123 = Test.

  1. At the moment (possibly after a major Yandex outage), it is unavailable. Although everything is fine in airExplorer (as is the case with the client itself).

  1. I used the app for a few days, but I missed a detailed display of information about files in RcloneView. Yes, I can find out the size of the folders, but it would also be useful to have information about:
    1. File size
    2. Hash array (which hashes are available. And when comparing, add an option to output them separately)
    3. In the storage itself, it would be great to have a summary of which hashes are supported, so I know how the comparison will go.
    4. In the hasher, it would be nice to add an interactive selection of hashes, rather than forcing me to enter a list.

Otherwise, thank you for taking my points into account and adding them to the list for implementation.
(By the way, I noticed that in airexplorer, the initial comparison of 60k files takes 10 minutes, while here it takes about half an hour.)

Thanks for the follow-up, and for the screenshots — they make both Yandex points clear.

1 and 2. The second Yandex account and the 410 error

These two have different causes, but the workaround below fixes both.

  • The “Success! All done. Please go back to rclone.” page is rclone’s own local page. By the time it appears, Yandex has already signed in with whichever account your browser was logged in to. rclone’s default Yandex sign-in link does not ask Yandex to show the account chooser, so the second remote (“123”) got the same account as “Test”. The matching 3.1 TB / 2.1 TB figures in your screenshot fit that.
  • The [410 - GoneError] Gone (Ресурс больше недоступен.) error is not specific to RcloneView. Other rclone users have been reporting it since around October 11: bug: 410 error when attempting to use Yandex Disk backend · Issue #10067 · rclone/rclone · GitHub. We reproduced it with a brand-new Yandex account, so it is not related to your account or your files. Disk info (the free space you see) still loads, but listing and downloading return 410. Several users found that it works again with a token from their own Yandex app, and we saw the same: on our test account, a token from our own app could list, download and upload, while the default sign-in still got 410 at the same time. So it looks like Yandex is currently blocking the shared app that rclone signs in with. Yandex hasn’t confirmed this, and the rclone issue is still open. Air Explorer most likely signs in with its own app, which would explain why it still works. Signing in again with the default settings won’t help.

Until this is fixed, you can give each Yandex remote a token from your own Yandex app. Your remotes and jobs stay as they are:

  1. Open https://oauth.yandex.ru/ and create an app. Choose “For API access or debugging”. When we chose “For user authorization”, Yandex asked for Gosuslugi verification. Give the app any name and add these three permissions under “Data access”:
  • Read all of Yandex.Disk (cloud_api:disk.read)
  • Writing in any place on Yandex.Disk (cloud_api:disk.write)
  • Access to information about Yandex.Disk (cloud_api:disk.info)The Redirect URI is fixed to https://oauth.yandex.ru/verification_code. That is expected. Create the app and copy its Client ID.
  1. In your browser, open this link with your Client ID at the end: https://oauth.yandex.ru/authorize?response_type=token&force_confirm=yes&client_id=YOUR_CLIENT_ID Yandex shows a sign-in screen with a large button for the account it will use. If that is not the account for this remote, click the “choose an account” line just above the button and pick the right one. Then press the large button. Yandex shows a long token that starts with y0_. Copy it.
  2. In RcloneView, check where your config file is: Settings > Embedded Rclone > Path Settings > “Local Rclone config location”. By default it is %APPDATA%\rclone\rclone.conf. Quit RcloneView and open that file in Notepad. Find the section for the remote, for example [Test], and replace its token = ... line with this one line. Put your token in place of YOUR_TOKEN:token = {"access_token":"YOUR_TOKEN","token_type":"OAuth","refresh_token":"none","expiry":"2027-10-01T00:00:00+03:00"}
  3. Do steps 2 and 3 again for the other remote (“123”) with the other account. Save the file and start RcloneView.

A few notes:

  • We tested these steps on a new Yandex account with RcloneView 1.6.8. After the token line was replaced, the remote opened normally.
  • The remote names don’t change, so your jobs keep working. Nothing in your Yandex Disk is changed.
  • This kind of token comes without a refresh token, and rclone won’t start without one. That is why the line has "refresh_token":"none" and an expiry date far in the future.
  • The token does not renew itself. If the remote stops working later, repeat steps 2 and 3. We will post here when the default sign-in works again.

If you only want to fix the duplicate account, sign out of Yandex in your browser before adding the second remote. You can also click “Show advanced options” and set auth_url to https://oauth.yandex.com/authorize?force_confirm=yes. Either way, the 410 stays.

We are also looking at a Yandex-specific message for this 410 and a way to show the account chooser by default.

3. File details and hashes

The list already shows file sizes, and right-click > Get Size on a folder shows its path, file count and total size. If you meant something else by file size (for example the exact size in bytes), let us know. What is missing is a proper details view, and you are right that hashes are not shown anywhere today. We have added these to our list:

  • a details panel for a file or folder with size, modified time, path and the hashes the remote can provide (calculated only when you ask, because some remotes have to read the whole file);
  • optional hash columns in Compare, next to name, size and modified time;
  • a “supported hashes” line in each remote’s details. RcloneView already gets this list from rclone; Yandex Disk, for example, supports MD5;
  • a picker for Hasher’s hashes option instead of typing a comma-separated list.

When “Use hashes for comparison” is on, Compare picks one hash type that both sides support, preferring crc32. For Yandex Disk against a local folder, that is MD5. We will show which hash was used.

4. Comparison speed

Thanks for the measurement. We found three things in our Compare that add up here:

  • It walks the tree one folder at a time: it lists the source folder, then the destination folder, then moves on. With 60k files spread over many folders, those round trips add up. Air Explorer probably lists several folders at once.
  • When Compare starts, it also counts the total size of both sides in a separate pass, so every folder is listed twice.
  • Inside each folder, matching names scans the other side’s list again for every file. That gets slow in folders with many thousands of files, and we can make it much cheaper.

All three are on our list.

If you can tell us whether both sides were Yandex, roughly how many folders the 60k files are in, and whether “Use hashes for comparison” was on, that will help us reproduce and measure it. (With hashes on and a local folder on one side, rclone has to read every local file to calculate its MD5, which can add a lot of time on its own.)

Thanks again for the detailed testing — it is genuinely useful.