technical_behavior_and_limitations.md

mkdocs/docs/faq/technical_behavior_and_limitations.md

@@ -273,21 +273,22 @@ practice. The alternative to this strategy is to create a setup where
 a filesystem proxy of sorts is spawned for each uid:gid combination
 needed and the main mergerfs process makes requests to those proxies
 to do the work needed. The problem is that that kind of setup is both
-more complex and slower.
+more complex and slower. If it is found that the current strategy
+causes issues the more complex one will be reconsidered.
 
+As a result of this change it is now necessary for the FUSE
+`default_permissions` feature be used for proper entitlements
+management. mergerfs does allow it to be disabled but it should only
+be done so for debugging purposes.
 
 
 ## Does mergerfs support idmap?
 
-Yes. At least in so far as it's been enabled now the FUSE itself
-allows a filesystem to indicate it is allowed.
-
+Yes. 
 Requires that
 [kernel-permissions-check](../config/kernel-permissions-check.md) be
 enabled (the default.)
 
-If there are any usage issues contact the [author](../support.md).
-
 
 ## What happens if a branch filesystem blocks?