The first thing I wondered after reading this article is whether there might be a scheduled task to run the permission reset similarly to how the author ran it via the command line.
It seems most likely that this is some kind of bug where that command or its underlying actions should be called every time the user unchecks something in the settings panel.
This is what we get when the iPhone’s permission system is grafted on top of a desktop OS that was never designed for it. I think they could have done something that is more Unix-like and yet friendly to the GUI end user.
This reminds me of the early days of MacOS where "repair permissions" was the magic fix to everything, or so it was rumored.
Whoa you are bringing back some memories.
And it absolutely was a magic fix. I stand by it.
I remember verifying it really DID fix some problems (just not all) and it was so easy to do you might as well always do it.
(You could see permissions errors in the logs that would go away after running it, which often didn't really fix anything but could make it faster since it didn't have to error out.)
Safari is snappier now