Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is a feature: FLAG_SECURE is real and used by many apps. i.e. Chrome's Incognito mode.

Sure, you have workarounds for power-users, but Google is locking the Android ecosystem progressively for regular users. Just like the Manifest v3 for Chrome.

Maybe Google is doing the "Embrace, extend, and extinguish" strategy that worked really well for Microsoft in the past.



Do you have any evidence for that?

The thread is about behavior caused by a presumably erroneous ".nomedia" file residing in certain users' screenshot folders.

The FLAG_SECURE feature doesn't appear to have anything to do with that. Two entirely separate things, unless you can show otherwise.


The thread describes a bug indeed, but the feature really exists.

Quoting the Android SDK reference : "FLAG_SECURE [...] Treat the content of the window as secure, preventing it from appearing in screenshots" [1] Try to screenshot while in Chrome's incognito, you'll see it in action.

[1] https://developer.android.com/reference/android/view/WindowM...


> Two entirely separate things, unless you can show otherwise.

Read the error message! It's clearly related to the real feature, which means the bug can't be "entirely separate".


> but Google is locking the Android ecosystem progressively for regular users.

FLAG_SECURE has existed for as long as Android has. It can't possibly be evidence of locking down the ecosystem progressively as it's always been part of the ecosystem.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: