Yikes, that issue you opened is like the exact opposite of proper etiquette for asking maintainers of open source software to help you. Basically what you’re doing is making a feature request, there is no bug or issue with TWRP as multiple people told you on GitHub. It’s absolutely not cool to continue to hound open source contributors for timelines like that. You’re not their boss, if it’s such an important issue to you fix it yourself and create a pull/merge request.
This is not just a nice-to-have thing, this is their project proactively running something that I did not authorize without informing me or giving me any chance to prevent it. I absolutely consider it a huge problem, not just a bug, that this functionality cannot be disabled in any way. Therefore I did not file a simple feature request for the setting because the deeper problem is that this functionality exists in the first place in a non-disableable manner.
I don't feel safe, no amount of discussion about etiquette will make me stop seeing this as a critical vulnerability that needs to be fixed, and it could take days or weeks of work for me to figure out how to compile TWRP properly if I were to fold at this point to the ten people telling me to just do it myself, which is a really stupid (imho) time investment that isn't compatible with my disabilities, sorry.
Something you did caused it to happen. Again, what you’re asking for has nothing to do with their project and is not a vulnerability in the slightest. It’s a feature working as intended, you should be focusing on what you did to cause it to happen. You’re also free to not use TWRP it if it doesn’t work for you.
