I am trying to wrap my head around this... Fiasco...
So
Apparently GOS has a thing that forces people to enter in a password/code/phrase/PIN instead of Fingerprint every 48 hours.
In surveillance states (like China mentioned above, but I would go so far as to say the USA and many, many western nations fit this description), and in highly crowded areas, and in threat profiles where a person can expect extraordinary efforts and resources to be expended on discovering a typed "pass-thing," fingerprint unlock is vastly preferred, and the risk of being locked out and forced to enter the typed pass-thing is very undesirable.
One thing I've learned on my journey switching from iOS to GOS is that security and convenience are inversely proportional, and that one must balance their threat profile with their patience to avoid privacy/security burnout.
When people suggest privacy screens, 'just don't unlock,' etc, I believe this inverse relationship between security and convenience is what is being referenced.
There are reasons for the 48 hour timer. Reasons include the fallibility of human memory, the varying security profiles between typed pass-things and fingerprints, and probably some other stuff I missed. But while these reasons do not negate the aforementioned concern about typed pass-thing discovery via observation, nor do those concerns negate the reasoning behind the decision to implement the timer.
However, GOS is a project that, to the best of my admittedly limited understanding, has fairly strictly defined it's scope as being about hardening AOSP first, user-friendliness a (very close) second (because the theoretically most secure phone is a brick). GOS devs have to draw the line somewhere in order to deliver in accordance to their project scope.
While it may not seem like a convenience, fingerprint unlock is in fact a convenience feature. It is there to make it convenient to easily open the phone without having to foist the onus of securing their typed pass-thing from observation onto its users. The alternatives - barring a software solution - are hardware solutions (privacy screen) and opsec solutions (deciding not to use the phone, hiding the phone screen while entering the typed pass-thing, entering the typed pass-thing every morning, etc).
And based on the infrequency of complaint about the 48 your timer, GOS has apparently decided it is not so inconvenient to the majority of users as to warrant a software solution on their part.
This can be frustrating. But the solution to this is not the kind of language being thrown around in this thread, I think.
I would hazard to say presenting your case in a calm, detailed manner in the Issues tab in Github (or wherever the repository is, idk off the top of my head), such that others may give their 'thumbs up' on the issue to draw Dev attention to it would be the most effective tactic available, in this situation.
That way, nobody has to be at anyone's throats here, and the buck stops with the devs.
Does that seem fair?