Never able to connect to hxxp://trackerX.istole.it. How come?

hi,

needless to say that like almost everybody here i am a huge fan of eztv. thank
you for all your great work!
i have been enjoying this site for a while now but have recently run into
problems with your trackers. it seems you now mainly or solely use the tracker1/
2/4.istole.it and for some reason i can never connect to them.

i have used you backup trackers and they work fine but of course seem very slow
and manually adding the trackers everytime kind of beats the purpose of this
site.

do you have nay idea as to why i cannot connect to these trackers? i have no
problems with other trackers and my client seems to be working flawlessly ☹️

i am using bitcomet as azureus keeps crashing my pc and i like bitcomet. it has
a bad reputation which has long been reabilitated but still some frown upon
bitcomet.

thank you!

as much as i appreciate this overly helpfull reply, i would prefer one that
actually helps me with this.

e.g. if you knew for a fact that trackerx.istole.it blocks all bitcomet clients.

and if not, then maybe something else might be helpfull.

thank you.

stfu you useless hack. let me know if this helps. kthx.

with currently really bad trackers and people as polite and helpfull as you, i
guess there is little point in using these torrents and contributing anything.

hope people stop seeding here and people like you finally learn that some
politeness goes a long way.

okay bye now =)

i'll continue to seed with my fios line.

ok. would a mod please remove this thread? no point in keeping it given the
lack of usefull help available here. sorry for disturbing your peace and quiet.

well, i don't know about you, but "yuck barfcomet! get utorrent and live
happily ever after." is not really a usefull answer. it would be if it were
more along the lines of " bitcomet is not very good and causes too many
problems. try switching to utorrent." or alternatively if it were the case "use
utorrent instead of bitcomet. bitcomet does not work with this tracker".

but obviously it has nothing to do with bitcomet. so just saying fuck bitcomet
is really no help at all.


thank you, that's more helpfull.
i have been able to add trackers manually in bitcomet and i have been adding a
whole list of trackers, but it does of course kill the purpose of eztv if so
many torrents actually will not work without you adding th trackers manually.

so, we now know it's due to bad trackers and not bitcomet and that for now one
has to manually add trackers.

given the current tracker state, is there a reason why the trackers are not
automatically added and instead all the torrents here only have one tracker
listed?


the dht network is a good thing but for some reason sometimes works and
sometimes does not. i guess it might be my provider as my firewall should not
be blocking it and neither should my router. and bitcomet supports dht also.
so unfortunately, dht alone is not really much help.
i will add trackers manually and i hope the trackers will be working properly
again soon.

you assume others are obligated to assist you. remember.. forums are a
privelege, not a right.

so is posting to a forum. it's a privilege, not a right. (never thought i'd be
giving spelling lessons to god) if i were a mod, your ass would be warned and
then banned. i can't even begin to think of why i would want to share files with
people who act like you. even your nickname smacks of an arrogant little twat.

oops my bad.. privilege.

as far as your comment on posting on forums.. i don't see how that pertains to
what i said. posting on forums is a privilege.. that's a given.

it's encouraging to see you get all flustered though.. maybe i should make more
spelling typos to incite said idiocy. i await your inevitable pedestrian
response.

i have a similar problem. it looks like one of the packet clearing houses isn\'t
routing traffic to this domain:

traceroute to tracker2.istole.it (91.196.170.241), 30 hops max, 40 byte packets
1 router (xxx.xxx.xxx.xxx) 49.084 ms 51.546 ms 52.057 ms
2 212.104.130.193 (212.104.130.193) 54.942 ms 57.318 ms 57.754 ms
3 81.5.191.181 (81.5.191.181) 59.170 ms 62.949 ms 63.383 ms
4 251.ge-1-2-3.mpr1.lhr3.uk.above.net (213.161.78.85) 66.965 ms 68.950 ms
69.404 ms
5 so-7-0-0.mpr1.ams5.nl.above.net (64.125.27.178) 84.795 ms 86.783 ms 88.766 ms
6 grafix.ams4.nl.above.net (82.98.253.68) 90.749 ms 95.822 ms 103.540 ms
7 ae-2-1.cap-grfx.net.technotop.nl (91.196.169.177) 96.988 ms 50.367 ms
55.604 ms
8 technotop.interxionams3.nl-ix.net (193.239.116.137) 57.855 ms 58.441 ms
59.561 ms
9 * * *
10 * * *

you need to connect a microwave into your computer and use your cell phone on
the tv. then you need to dial 666. after that, open the notepad on your computer
and click on the "i'm-an-idiot" link that appeared.
the devil will come and solve your issue.

thank you aydin.

@god: i think you don't know what a forum is for and how to behave in one. a
forum is usually a place were people can ask questions on a subject and either
receive and answer to their question or not, depending on whether someone can
and wants to help.
if jerks like you troll forums just to piss off others, then usually they are
banned by mods for their destructive behaviour.
don't know about you, but i wasn't raised in a barn and see no reason to behave
like a moron.

@tvfan: i tried utorrent on a different occasion, not with the nw situation.
might try it, though.
however, the reputation of bitcomet is based on fools who do not know what they
are talking about.
some fools dissed bitcomet because it used protocolls in unusal ways which some
saw as a violation of the code. in reality they were simply too stupid to
program it right.
bitcomet then removed this feature and never recivered from morons dissing
bitcomet simply out of ignorance.

and so my predictions came true once again.

the word protocol means you don't deviate from published specifications, and you
sure as hell don't try to subvert them for your users' benefit. besides being
miserable adware, bitcomet-made torrents sport those godawful padding files
which, conveniently enough, are invisible to bitcomet users. for the other 95%
of bittorrent users, they're incredibly frustrating, and while not actually a
violation of the spec, it shows the lack of respect that bitcomet's developers
have for the rest of the torrent ecosystem. then you have their dht "bug" where
it didn't respect the private flag, which took them forever to fix, as well as
the well-known fact that bitcomet is programmed to behave in "selfish" and
"deceptive" ways, gaming the system in ways similar to that other jerkoff
client, bittyrant. bittorrent is a pretty awesome protocol, but it's still
possible to fuck with the internals, and that's a problem for everyone. the
fact that you resort to calling the programmers of other bittorrent clients
fools and stupid says a lot about you, unless i'm speaking with bram cohen. the
reputation of bitcomet is well-deserved, and the only fools are its users.