Quote:
Originally Posted by dorrcoq
"tracker was fine, fast and flawless" Yeah...once you were able to upload your torrent it was fine. I see you have never uploaded a torrent, so you would have no idea what a pain in the ass it was. I think my "record" was 23 times trying to get the torrent file attached to an upload. But routinely over 10 times. I have a long history with this site going back to day one, but I was sorely tempted to take my uploads elsewhere.
|
Correct, am a musician and do not at all find a performance worthwhile when operating recording equipment to my standards alas. The production is too mesmerizing. Maybe someday, though there are super few acts I care to witness firsthand anymore and they certainly about never come around my remote mountain location. The shows I have recorded are uploaded and seeded elsewhere prior to my arrival here.
That does sound a hassle, but loads of sites aren't and do not use cloudflare, or if they do is entirely transparent. So my point of course was to suggest those jokers take the simple effort to determine what syntax aspect of their whack code is at fault here on the double and for the Den to assess if there's a viable fix or workaround.
The bottom line is the address of a server seed is not being communicated with accuracy to clients and or vice versa. Look up the crap they put Tor through. That's who we're dealing with. If it were my man-in-the-middle code I could--and would--hone in on it pronto.
For a true coder, the hunt is the fun.
No members have liked this post.