-
```
We should improve PeerBlock's ability to block/unblock ports. Currently
only HTTP/HTTPS ports (80/443) can be specifically blocked/unblocked; we
should permit any port to be blocked/unblocked, an…
-
### What we should change and why (this is tech debt)
We need to do some work to un-break the build for an upgrade to cancancan 2.0, to start, and then to catch up to the current version.
###…
-
Block user: https://dev.twitch.tv/docs/api/reference#block-user
Unblock user: https://dev.twitch.tv/docs/api/reference#unblock-user
-
There are a number of pull requests for this (very important) crate that are going unanswered. For example:
https://github.com/sfackler/rust-openssl/pull/1234
https://github.com/sfackler/rust-open…
-
Need to add field "Unblock" & date. Optional.
-
```
We should improve PeerBlock's ability to block/unblock ports. Currently
only HTTP/HTTPS ports (80/443) can be specifically blocked/unblocked; we
should permit any port to be blocked/unblocked, an…
-
```
Currently PeerBlock blocks all protocols and only allows port 80/443 on the
TCP protocol if it is set to allow HTTP. We should allow the user to unblock
certain protocols so all traffic will jus…
-
It seems DNS resolutions are being cached. When updating the hosts file to block or unblock a website, this leads to the effects of the hosts file change being delayed.
We may have to avoid relying s…
-
```
My suggestion is:
When you click on a spawn icon their is currently a add to fpp, it is hard to
currently go through all your blocked models to find the specific prop to
unblock, i think that th…
-
```
We should improve PeerBlock's ability to block/unblock ports. Currently
only HTTP/HTTPS ports (80/443) can be specifically blocked/unblocked; we
should permit any port to be blocked/unblocked, an…