About unique_file_id and some features

[tissole]

This is a continuation of #3. What exactly is unique_file_id? I searched on the internet but I could not find anything relevant. I guess these values are some sort of checksums. How TG obtains these ids from the files uploaded? A user could generate these values for local files?

If 2 files are identical but have different names, one is named Introduction to Python.pdf, and the other one is named 145536456.pdf, a problem could arrive if the bot deletes the one named correctly and keep the other. How this could be prevented?

Maybe the bot could delete the file containing only numbers and keep the one containing words?
Or keeping the file that has a caption?
Or adding an option so that users choose manually what to delete?

It would be helpful if a list of duplicates (with the name, caption, and size of files) could be dumped in a text file locally or sent to Saved Messages, so the users have an idea of what has been deleted.

In the above scenario, after the purge, I would not find the file Introduction to Python.pdf, but I could check the list of duplicates and found the corresponding duplicate named 145536456.pdf

[m4mallu]

You won't get these parameters for the local file type, Coz we are talking about a file in the cloud. When a local file is being uploaded to telegram cloud servers, telegram will assign some default parameters (unique_file_id, big file id, small file id, etc. ) to the uploaded ones. According to these parameters, the telegram has indexed the files in the cloud.

As I said earlier, a unique thing in a particular file in different chats is the one and only 'unique_file_id available in the file attributes. So we cant consider file_name, file_caption, etc. for indexing a chat. That's why this bot makes a list with the same.

It can be considered to provide a report of the process after the operation. Updates will be pushed in the future...

[tissole]

Thanks for the answer! I completely understand what you're saying. A file can only be considered unique by its unique_file_id and not by its size, caption, name, etc. I only ask if is possible that when 2 files have the same uniq_id to keep the one that also has a caption. Or when 2 or more files have the same uniq_id to keep the file that has words in the title. Or to have an option to delete files interactively.

But again, how TG obtains unique_file_id? What hash algorithm does TG use?

[m4mallu]

All are in my previous answer. Try to search for the cloud file operations and procedures. Tg is putting some attributes like unique_file_id and others when a file is uploaded to its servers.

Better knowing these.. please consider reading Tg docs and pyrogram docs (framework).

It can consider keeping the captioned file when in indexing .. code needs a next-level update.

[tissole]

I have not explained it properly. I will try my best.

Problem. If the bot finds 2 identical files (same unique id), one named Intro to Python.pdf and the other 145536456.pdf, it will delete one of them. If I'm unlucky it will delete Intro to Python.pdf. After that, if I search in the channel for that file I will not find it, because it was deleted and the one kept has the wrong title.

Solution. After the purge, the bot dumps a text file with the names of deleted files. The user searches and finds that the file Intro to Python.pdf has been deleted, but his copy 145536456.pdf is still in the channel. The user renames that to Intro to Python. Problem solved :)

Problem. Bot encounters 2 identical videos when indexing. One of them is properly captioned like How to get more views on Youtube, the other has a weird name like 1885345 and is uncaptioned.

Solution. After the purge command is sent, the bot deletes the uncaptioned file and keeps the captioned file.

The dump file should contain identical files in groups, for example, if finds 7 duplicate that's one group, other 3 duplicates is another group and so on. For easy reading. The file kept has to be clearly marked for easy finding in the channel.

[m4mallu]

It can be done. Am rewriting its code to do the stuff in a more convenient and global way. Thanks for the suggestions.

[tissole]

Great, thank you!