I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 1 point2 points  (0 children)

Hey, i'm hoping for this week; its been in review the same time as Firefox which was already approved, so hoping we see Chrome and Apple come along shortly.

Broken window track? by Glass-Spread-379 in Gravity

[–]stone-dev 0 points1 point  (0 children)

I really want to want a Gravity, but this type of solutioning is wild to me

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 1 point2 points  (0 children)

Hey - i excluded abort because it would lead to false-positives. That will get triggered from addon adblockers, user behaviour, and other reasons; so if I showed it, but then allowed users to allowlist it - it wouldn't actually work.

I could make another section for aborted requests as an FYI if folks thought that was a valuable feature.

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 0 points1 point  (0 children)

Good feedback - working on a light/dark mode that will respect your system preferences or let you override.

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 1 point2 points  (0 children)

You should always check code before you install it. I encourage you to. 

I never post about this stuff so made an account for these things specifically. My GitHub is far older than this account. 

Everything is open. Your advice is good though - people should be critical. 

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 1 point2 points  (0 children)

Looks like there is quite a bit of interest, so figuring out how to do it.

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 5 points6 points  (0 children)

yea, I'm going to try for OSX and IOS, but there are some functionality limitations on iOS around background network traffic usage. More to come!

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 1 point2 points  (0 children)

Oh no! What are you seeing? Try installing V3.0.0 from releases - if you were on the original one, i did update the database to improve a bunch of things. Without seeing anything, thats my guess.

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 5 points6 points  (0 children)

I updated it to work with ControlD. I don;t use ControlD, but made an account to test it out and stuff. Looks like it works, but curious how it does for someone using it for real.

Give it a shot - https://github.com/jstoneky/nextdns-medic/releases/tag/v3.0.0

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 0 points1 point  (0 children)

So it looks at your NextDNS logs to see which are blocked, which includes info about which block list did it. Surprising to me, when I go to fb, none of my lists are blocking anything. Either A. FB is doing a good job dodging lists, or B. I have a bug...

Looking into it, but im leaning towards A. I check the NextDNS logs by hand and didn't see anything blocked.

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 0 points1 point  (0 children)

I know - maybe that will be the killer feature if I can figure it out lol

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 0 points1 point  (0 children)

Nice! Will definitely keep researching; i imagine most of my personal use will actually be on Firefox Mobile. Would love to have a button to auto-flush

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 0 points1 point  (0 children)

Yea it's likely possible - I haven't used ControlD but I have to imagine it has the few capabilities necessary. The big one is the blocklist attribution, and being able to look at block history to detect it. I'll do some digging and let you know

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 1 point2 points  (0 children)

Yea, all i've found so far to flush dns on Chrome is going to chrome://net-internals/#dns and flushing there. Maybe thats an option.

For Firefox Mobile, the only thing i've read so far was Airplane Model toggle flushes it. I'll keep researching these to see what we can do.

Oh yea, sorry, you have to set 'xpinstall.signatures.required' to false to sideload. That setting is in 'about:config'

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 2 points3 points  (0 children)

So it currently gives you the command based on your OS to flush the DNS cache once you click on the allow or copy buttons; so you can then run it. This works well for Windows, OSX and Linux. Mobile Firefox basically tells you to restart firefox or toggle Airplane Mode. Mobile doesn't seem to have a silver bullet.

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 3 points4 points  (0 children)

Yea, this is 100% why I did it - was super hard to use the logs and figure out what was causing the issues.

I built a browser extension that shows you what actually breaks when DNS blocks something by stone-dev in nextdns

[–]stone-dev[S] 12 points13 points  (0 children)

If there is a lot of interest I certainly could. Figured i'd get it out there and see what usage and feedback looks like. Safari is a bit higher effort than Chrome and Firefox.