Bit Che > Scripts & Development

Possibility of using HTTPS as default for https enabled sites and proxies

(1/1)

ID101:
Bit CheTM has https support, why don't we use it by default in scripts?

We can change all piratenpartij.nl search links to scrips to https
or at least adding aditional https line for each supported site

https://proxy.piratenpartij.nl/site url here

Reasons:

* privacy concerns

* legal defense
* weak -  better than none - protection against mitm with "cooked" torrents

ID101:
New!

full encryption:

kickass.to


--- Code: ---[home]
1=https://kickass.to
2=http://kickass.to
3=http://kickasstorrents.com
4=http://kickasstorrents.com.proxy.piratenpartij.nl
4=http://kat.ph.proxy.piratenpartij.nl
5=http://www.kickassunblock.info/
6=http://katunblock.com/
6=http://kickass.pw/
7=http://kickassproxy.info/
8=http://katproxy.pw/
9=http://katproxy.me/
10=http://kickassunblock.com/
11=http://katproxy.com/
12=http://kat.dashitz.com/
13=http://kat.kleisauke.nl/
14=http://kat.ph.proxy.piratenpartij.nl/
15=http://www.katmirror.com/
16= http://kat.5gg.biz/
17=https://proxy.piratenpartij.nl/kickass.to
--- End code ---

yify-torrents.com

--- Code: ---[home]
1=https://yts.re
2=http://yts.re
2=https://proxy.piratenpartij.nl/yts.re
3=http://proxy.piratenpartij.nl/yts.re
--- End code ---

partial encryption:

rarbg.com


--- Code: ---[home]
1=https://www.rarbg.com
2=http://www.rarbg.com
3=https://proxy.piratenpartij.nl/rarbg.com
4=http://www.rarbg.com.proxy.piratenpartij.nl
--- End code ---

1337x.to/


--- Code: ---[home]
1=https://1337x.to/
2=http://1337x.to
3=https://proxy.piratenpartij.nl/1337x.to
4=https://proxy.piratenpartij.nl/1337x.to
--- End code ---

ID101:
I've noticed something strange with proxy.piratenpartij.nl in bit che 3.0 build b14(contrary to web browsers)

only two working:


--- Code: ---http://thepiratebay.se.proxy.piratenpartij.nl
https://thepiratebay.se.proxy.piratenpartij.nl

--- End code ---

not working(always return ./0/1 results)

--- Code: ---http://proxy.piratenpartij.nl/thepiratebay.se
https://proxy.piratenpartij.nl/thepiratebay.se

http://anyothersite.proxy.piratenpartij.nl
https://anyothersite.proxy.piratenpartij.nl
http://proxy.piratenpartij.nl/anyothersite
https://proxy.piratenpartij.nl/anyothersite
--- End code ---

chip!:
i see what you're saying.. it fails by design because we are 'merging' the urls not 'appending'..

so in your example:

http://proxy.piratenpartij.nl/thepiratebay.se

+

/search/%SEARCH%/%PAGENUM%/99/0

results in the 'proper' url merge of:

http://proxy.piratenpartij.nl/search/%SEARCH%/%PAGENUM%/99/0

except its not the search url you want...


but if you change to this:

http://proxy.piratenpartij.nl/thepiratebay.se/

+

search/%SEARCH%/%PAGENUM%/99/0

then you'll get this url merge, which is what you want..

http://proxy.piratenpartij.nl/thepiratebay.se/search/%SEARCH%/%PAGENUM%/99/0


we can update the scripts.. with that format change

EDIT::  DONE for that script

Navigation

[0] Message Index