Comment 65 for bug 688576

Hello,
I'm new to KDE and learning to get use to its particularities but for weeks I wondered why my home partition was getting full and why it took such a long time putting big files in the trash, whereas it had always been instant on any other OS / DE I ever used.
I seriously thought there was something wrong with my installation or there was a bug or something.
Then I found this thread and I'm falling off my chair.
This is actually expected? I see the logic, but it is so confusing and so unexpected from a user's perspective, it really seems strange to me.
How can the user be aware that deleting a file will have a different behaviour depending on where the file is? OK, there are specs, but not all users will read the specs before using a desktop environment.

I would be totally OK if in case of lack of "support" for a "local trash", a warning would tell me the file would be removed directly. But expecting the user to guess that is really not user-friendly.
This said, of course I would love to see it work on the various drives I have to use, and wondered if there was a solution for NTFS and exFAT systems.

And I can't help but wonder why is it not working with KDE and just working without issue on other desktop environments in the same conditions? (just tried a Debian with Cinnamon I have lying around and a deleted file on an external exFAT drive is put in the .Trash-1000 folder of the drive, no questions asked - same drive plugged into Manjaro KDE puts the deleted file in my home trash)

Thanks very much in advance for considering this issue and this user feedback.