Not sure if this is the correct place to post, but I just wanna kinda rant a bit.

I’m not the only one that hates this, right?

An app can just do a “This App Does Not Allow Screenshots”? Like… wtf?

Like, its my phone, and some app can just decide to disable a fuction of my phone. It’s my phone and if I wanna take a screenshot, I’m taking a screenshot. I don’t care about whatever “security” the app developer wants.

Imagine if every online shopping app whether fast food or amazon, just used this to block you from taking a screenshot so you can’t save the records in case of a dispute.

Which android developer thought it was a good idea to let an app disable a function on your phone. Even iPhone doesn’t have this stupid concept.

Sorry for the rant.

Anyone wanna share your stories?

(P.S. I have a cheap secondary phone to take photos of the screen. “This App Does Not Allow Screenshots” my ass lmao, I’m taking the screenshot whether the app wants it or not.

  • smeenz@lemmy.nz
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    10 hours ago

    Probably a nod to the written style of RFC definitions, which have the word entirely in capital letters, as in… the implementation MUST do such and such, and SHOULD do this other thing. In this case, the relevant security standard(s)

      • smeenz@lemmy.nz
        link
        fedilink
        English
        arrow-up
        10
        ·
        9 hours ago

        RFCs were being written back when line printers couldn’t do either.

        • Psythik@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 hours ago

          I misread your comment and thought you said “RFK”. I have no idea what an “RFC” is. Some sort of teletype thing?