[Magisk] TechnoSparks:
I am very sorry for the lack of activities in the past week. To put it simply, I had some issues with the computer at home and therefore I am unable to push new changes to the code and make adjustments to the reported problems, in addition to leaving my own laptop at my hostel. :eek:

VR25 the developer of fbind manage to make bind mounting work in the presence of a supposed "older" implementation of SDCardFS. The algorithm needs to check if Android mounted the respective bind mount in other runtimes (Read and Write). If the mountpoints are non-existent, we manually create the bind mounts to the mentioned runtimes. An update will be made in my blog post in regards to this technical details if anyone is interested. Technically, the current GitHub repository is already updated with this new logic. However, I haven't tested the module yet and I am pretty sure that the module is broken (as per to current latest version on the git repo).

Plus, assignments - during - mid-semester - break - which i hate. I will get my hands extra dirty tomorrow and release the bleeding version disguised as (public) beta in the Magisk repo. This way, a broad audience can be reached when the module breaks for their devices :v

Now moving on to replies:

____________________________________

The sudden not working may be mysterious indeed, but based on your first initial report it seems that your kernel is using another variant of SDCardFS. This has been fixed and a new bleeding release will be updated on Google Drive using the same link. You may test it out when I give the greenlight maybe at night tomorrow UTC+8 :)

____________________________________

Ah it seemed you too. Based on the reported situation, it is highly probable that you are affected because of the different SDCardFS like some other users initially faced. This has been fixed and a new bleeding release will be updated on Google Drive using the same link. You may test it out when I give the greenlight maybe at night tomorrow UTC+8 :)

My forum settings set that No. of posts viewed in a page is 50. So I cannot find which one, since I posted many links to GDrive. But I think we should get back to square one with a newer version of the module as mentioned above when I completed it! :D

____________________________________

To first make matters easier, I would to stress that this is a simple module (i.e. not complex). It just binds another folder to another. The "save space" is just a beneficial side effect of this trick. Now since that is explained, I would like to also emphasise that my webpage (documentation) should be a great starting point for using the module. I know you may have already read the docs, so to answer your questions:

Chrome downloads files to "/internal/Download". To make the module functional for this specific use case, we bind a path from external, to this "/internal/Download" path. So no, we do not need to change anything in any applications.

Yes, you will need to copy/move the original folder first. But make sure to leave an empty directory "WhatsApp" in internal. What happens from then on after you binded the folder is that whatsapp will always put files onto /internal/WhatsApp. But since such path was binded FROM an external path, the contents of /internal/WhatsApp will get updated and physical changes to the external storage will take effect. No you do not need to periodically unlink.

[MENTION=3330854]the gladiator[/MENTION] have explained it well. Consider my points as reaffirmation to his. :)