In reply to: SCC.torrent.tracker.and.their.source.ftp.site.called.AR.README-4CLEANERSCENE
The only proof provided by that bullshit nfo is that the author is an insecure p2p user.
Not only he risked the site and its users by including ips/affils which was unnecessary,
but he also seems to actively monitor torrent sites and their pretimes.
Regarding the proof, few releases with similar complete times isnt a proof, many other sites had
similar complete times on the same releases (when 0byte/slowfile hits one site, it hits many
others as well). Its commonly known that sites complete times are similar to each other and dependent
on couriers chains.
Anyway, Im just going to use one of the proof pictures to prove that this nfo is complete nonsense.
Proof.jpg (attached):
The.Green.Hornet.PROPER.REPACK.720p.BluRay.x264-TWiZTED
AR: 4m 15s SCC: 1m 33s
10.O.Clock.Live.S01E12.720p.HDTV.x264-SATV
10.O.Clock.Live.S01E13.720p.HDTV.x264-SATV
MiniSquadron_v2_EUR_PSN_PSP-ABSTRAKT
Not shown on that trace website, yet complete on AR.
Users/affils safety were always in the highest priority. It was stated in the nfo that
SCC uses OVH boxes to upload scene releases, OVH ranges were blocked from the site since day one,
which makes it very unlikely that the leak came directly from any of the site users.
Nevertheless, Ive searched the logs for all the ip ranges listed in the nfo, but couldnt find anything.
Measures taken: site IPs were changed, udb was massivly cleaned and all ip ranges listed in the nfo were
blocked.
Bookmarks