Skip to content

[FR] Allow to disable prohibition on video downloading and screenshots in sensitive channels #454

@revonateB0T

Description

@revonateB0T

Hello Forkgram team 👋

I’d like to request a feature that adds a switch to disable the built‑in prohibition on video downloading and screenshots in sensitive channels (e.g., channels with “Restrict Saving Content” enabled).

I fully understand that complete prevention is impossible — if a user can view a video, they can always record it with another device. But adding an option to remove the artificial client‑side blocking would be convenient for power users who want to save content from channels that forbid it.

Why this matters

  • Telegram (and Forkgram) already respects the channel’s “restrict saving content” flag, which disables download buttons and blocks native screenshots.
  • However, in many cases users still want to save media for legitimate offline use (e.g., reference, study, personal archives) — and the restriction is only client‑side anyway.
  • Adding a simple opt‑in switch to override that restriction makes the app more flexible and honest about the limits of DRM.

Proposed behavior

  • Add a global or per‑chat setting: “Ignore ‘restrict saving’ flag” or “Allow download & screenshots in sensitive channels”
  • When enabled:
    • Download buttons become available even in restricted channels.
    • Native screenshot blocking (e.g., FLAG_SECURE) is disabled, so users can take screenshots normally.
  • The feature should be disabled by default (respect the channel’s original restriction) and clearly marked as “advanced / power user option”.
  • Optionally show a warning: “Bypassing content restrictions may violate the channel’s rules. Use responsibly.”

Benefits

  • Gives users full control over their own device.
  • Acknowledges that client‑side blocks are trivial to bypass (screen recording, external camera, etc.) — so why inconvenience the user?
  • Useful for archiving, accessibility, or offline viewing.
  • Simple to implement (reversing the existing FLAG_SECURE / download button logic).

A note on limitations

I know that bypassing the restriction doesn’t make it “right” for every channel owner, and some users may disagree. But since the protection is already not real security — just a gentle barrier — offering an optional way to turn it off aligns with Forkgram’s philosophy of giving users choices.

Thank you for your amazing work and for considering this request 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions