this post was submitted on 19 Jul 2023
55 points (98.2% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54500 readers
360 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

I found out today that I can change my dns to acces 1337.to again. My ISP was blocking it. However, it works on chrome, but not on firefox. Why doesn't it work on firefox?

top 20 comments
sorted by: hot top controversial new old
[–] [email protected] 36 points 1 year ago* (last edited 1 year ago) (4 children)

Chrome has DNS-over-HTTPS enabled by default. Firefox, however, enables that by default in certain regions only.

Cloudflare has a comprehensive guide on how to enable it in various browsers.

P.S. If you dun wanna use Cloudflare as the resolver, quad9 can be an (maybe better) option.

[–] [email protected] 3 points 1 year ago (2 children)

Followup question, prowlarr seems to have the same issue. Do you know if and how I can setup prowlarr to use couldflare dns?

[–] [email protected] 2 points 1 year ago (2 children)

prowlarr does not appear to support customizing DNS. You need to alter your DNS on the OS level. Which OS are you using?

[–] [email protected] 2 points 1 year ago (1 children)

I think it just neede some time to sink in, or just another restart, but today everything just qorks. Thanks for your help anyways, I appriciate it.

[–] [email protected] 1 points 1 year ago

You are welcome and glad that it works eventually.

[–] [email protected] 1 points 1 year ago (1 children)

Linux Ubuntu. What I've done so far is change the nameserver in resolv.conf to 1.1.1.1 and installed resolveconf to make it permanent. Basically these steps

[–] [email protected] 1 points 1 year ago (1 children)

And the issue still persists even after taking those steps?

Does the dig command confirm 1.1.1.1 is in use?

[–] [email protected] 1 points 1 year ago

Yes. Unfortunately prowlarr seems to have stopped working all together. Some issue with sqlite and there not being a "user" table. It is not my day!

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Prowlarr works fine but you need yomething inbetween to solve the CF captcha.
https://github.com/FlareSolverr/FlareSolverr

Edit: Using both in a docker container

[–] [email protected] 3 points 1 year ago
[–] [email protected] 3 points 1 year ago (2 children)

That seems as a weird decision by Firefox considering their relatively privacy focused image.

[–] [email protected] 20 points 1 year ago (1 children)

Not really as hiding dns alone doesn't give you a big increase in privacy. Your isp can see what sites you visit immediately after anyway.

It could be argued that sending all your dns requests to a 3rd party by default is actually a decrease in privacy.

[–] [email protected] 4 points 1 year ago

Yeah hiding DNS queries is just one part of the equation. It has to be coupled with other techs/techniques to really achieve privacy.

[–] [email protected] 1 points 1 year ago

1.https does not mean more private. for regular browsing it does not matter 2. it is always good to have 2 browsers or use containers to seperate personal and regular stuff

[–] [email protected] 2 points 1 year ago

Maybe a little off-topic, but I found this useful to explain difference between DoT and DoH: https://www.cloudflare.com/learning/dns/dns-over-tls/

Turns out I am using DoT instead of DoH. Both are encrypted, but DoT is distinguishable from HTTPS traffic.

[–] [email protected] 19 points 1 year ago

Go into the settings and enable DNS over HTTPS. That should solve the problem, and honestly you should have it enabled anyway for privacy.

[–] [email protected] 9 points 1 year ago* (last edited 1 year ago)
  1. adblocker or any other blocker
  2. DNS on browser
[–] [email protected] -3 points 1 year ago (1 children)

If you're accessing 1337.to without a VPN, I don't think you're going to be having issues with your internet for much longer, lol

[–] [email protected] 8 points 1 year ago (1 children)

Not everyone lives in the US

[–] [email protected] 2 points 1 year ago

US or not accessing the site itself is in no way illegal.

load more comments
view more: next ›