We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EnergizedProtection/block#971 EnergizedProtection/block#972 EnergizedProtection/block#973 EnergizedProtection/block#974 EnergizedProtection/block#975 EnergizedProtection/block#976 EnergizedProtection/block#977 nextdns/metadata#1145 nextdns/metadata#1148 https://help.nextdns.io/t/83hsb6l/energized-ultimate-have-0-entries https://help.nextdns.io/t/m1hs207/energized-ultimate-lists-blocking-nextdns https://help.nextdns.io/t/q6hs204/nextdns-io-addresses-added-to-a-blocklist-internet-goes-down please remove Energized Ultimate from your Aggressive Blocklists
The text was updated successfully, but these errors were encountered:
https://www.reddit.com/r/nextdns/comments/z4a7ov/energized_lists_all_hacked_or_another_issue/ https://help.nextdns.io/t/m1hs207/energized-ultimate-lists-blocking-nextdns
their latest commit emptied the README.md file from their official repo. See EnergizedProtection/block@8bc981b
README.md
oh my
Sorry, something went wrong.
yokoffing
Successfully merging a pull request may close this issue.
EnergizedProtection/block#971
EnergizedProtection/block#972
EnergizedProtection/block#973
EnergizedProtection/block#974
EnergizedProtection/block#975
EnergizedProtection/block#976
EnergizedProtection/block#977
nextdns/metadata#1145
nextdns/metadata#1148
https://help.nextdns.io/t/83hsb6l/energized-ultimate-have-0-entries
https://help.nextdns.io/t/m1hs207/energized-ultimate-lists-blocking-nextdns
https://help.nextdns.io/t/q6hs204/nextdns-io-addresses-added-to-a-blocklist-internet-goes-down
please remove Energized Ultimate from your Aggressive Blocklists
The text was updated successfully, but these errors were encountered: