openbullet / openbullet/OpenBullet2

[REQUEST]: add check only non-working proxies and a regex pattern check in the target section of the proxy checker

Open
#1,102 1 comment 0 reactions 1 assignee View on GitHub

@openbullet is already working on this.

Since Sep 6, 2024.

area:backend area:frontend client:native enhancement lib:rurilib low priority
Dominant language
C#
Stars
2.4k
Forks
602
PR merge metrics
No merged PRs in 30d

Description

This feature request respects the following points:
  • This is a feature request, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow OpenBullet's Code of Conduct.
  • This report addresses only a single feature request; If you have multiple feature request, kindly create separate reports for each one.
Description of the feature request

in the proxy check section add check only non-working proxies instead of checking all proxies each time (even the working ones, which doesn't make sense) also it would be useful to have a regex pattern check in the target section

Is your feature request related to a problem

every time I have to check all proxies instead of being able to check only the broken proxies as it would be logical to do, also it is not possible to use regex in the target section when I check proxies

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Relevant screenshots or videos

No response

Additional information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.