[GH-ISSUE #1241] [Feature Request] Do not automatically check for updates in metered networks #3315

New issue

Open

opened 2026-03-01 19:09:57 +03:00 by kerem · 0 comments

kerem commented 2026-03-01 19:09:57 +03:00

Owner

Copy link

Originally created by @DeepChirp on GitHub (Oct 8, 2023).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1241

Originally assigned to: @NickeManarin on GitHub.

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Use API to detect whether the current network is billing by traffic, and if so, do not automatically check for updates. However, a switch can be added to allow users to automatically check for updates under a metered network.

At the same time, I believe that when checking for updates in a metered network, users should be reminded that this may incur additional fees.

Describe alternatives you've considered
None

Additional context
None

Originally created by @DeepChirp on GitHub (Oct 8, 2023). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1241 Originally assigned to: @NickeManarin on GitHub. **Is your feature request related to a problem? Please describe.** _No_ **Describe the solution you'd like** Use API to detect whether the current network is billing by traffic, and if so, do not automatically check for updates. However, a switch can be added to allow users to automatically check for updates under a metered network. At the same time, I believe that when checking for updates in a metered network, users should be reminded that this may incur additional fees. **Describe alternatives you've considered** _None_ **Additional context** _None_

kerem added the

🔷Enhancement

⬜ Pending

labels 2026-03-01 19:09:57 +03:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dev

v2.40

2.43.1

2.43

2.42.1

2.42

2.41.5

2.41.4

2.41.3

2.41.2

2.41.1

2.41

2.40.1

2.40

2.39

2.38.1

2.38

2.37.2

2.37.1

2.37

2.36

2.35.4

2.35.3

2.35.2

2.35.1

2.35

2.34.1

2.34

2.33.1

2.33

2.32.1

2.32

2.31

2.30.1

2.30

2.29.1

2.29

2.28.2

2.28.1

2.28

2.27.3

2.27.2

2.27.1

2.27

2.26.1

2.26

2.25

2.24.2

2.24.1

2.24

2.23.2

2.23.1

2.23

2.22.1

2.22

2.21.2

2.21.1

2.21

2.20.4

2.20.3

2.20.2

2.20.1

2.20

2.19.3

2.19.2

2.19.1

2.19

2.18

2.17.1

2.17

2.16

2.15.2

2.15.1

2.15

2.14.1

2.14

2.13.3

2.13.2

2.13.1

2.13

2.12.1

2.12

2.11

2.10

2.9

2.8.1

2.8

2.7.3

2.7.2

2.7.1

2.7

2.6

2.5

2.4

2.3.2

2.3.1

2.3

2.2

2.1

Labels

Clear labels   

copy cats

  

duplicated

  

future feature

  

pull-request

Mirrored from GitHub Pull Request

  

⬜ Accepted

  

⬜ Completed

  

⬜ Help Wanted 💪

  

⬜ In Progress

  

⬜ Missing Details

  

⬜ Pending

  

⬜ Waiting For Answer ⏳

  

🆕 feature preview

  

🔷 Bug 🐛

  

🔷 Out Of Scope

  

🔷 Out Of Scope

  

🔷 Question

  

🔷Enhancement

  

🔷Enhancement

  

🔷Invalid / External

  

🔷Knowledge Base

  

🔷Won't Fix

  

🕑 High

  

🕑 High

  

🕑 High

  

🕕 Medium

  

🕙 Low

  

🕛 Critical

No labels

copy cats

duplicated

future feature

pull-request

⬜ Accepted

⬜ Completed

⬜ Help Wanted 💪

⬜ In Progress

⬜ Missing Details

⬜ Pending

⬜ Waiting For Answer ⏳

🆕 feature preview

🔷 Bug 🐛

🔷 Out Of Scope

🔷 Out Of Scope

🔷 Question

🔷Enhancement

🔷Enhancement

🔷Invalid / External

🔷Knowledge Base

🔷Won't Fix

🕑 High

🕑 High

🕑 High

🕕 Medium

🕙 Low

🕛 Critical

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ScreenToGif#3315

No description provided.