Yep. you are 100%. I dont really understand why that call was made, but its ok. Fixed and updated the app to be able to handle that also. H33T should now be working again
Edit: So I just saw that on H33T "Trusted" members dont need captcha for the torrent upload any more. Sadly I dont have a trusted account there to test, but the app *should* still work just fine
been a bit busy for the past few days. but I do intend on doing a fair bit more work on this before next *real* update.
I have a pretty solid programing background, although mainly webdev and non ui based applications (hence the design for this is pretty meh haha)
There is nothing "Torrent Protocol" here actually.
What I did was inspect the torrent site at hand and see exactly what input it all needs to handle authentication and upload the data/info to the torrent site. dotNET has very lists support when it comes to HTTP get/post (which is primarily what we are dealing with here) so had to write some class to be able to submit the data using HTTP POST requests.
as a matter of fact I wrote (long ago) a script in php that does the exact same as this app and have been using it for month now, took me under an hour to write the php script but since its not really cut out for the "average joe" i thought I would learn how to do a windows desktop app, dotNet seemed like an alright start haha
So to answer the question is short, there is not much "Torrent Protocol" related in this application, only thing I can think of is the application extracts the hash out of the .torrent file for later use.
I just gave it a try and my test was uploaded correctly to the music section: "Categories > Music torrents" without being in a specific genre (as expected)
and like you I tried to edit it shoows up as "Movies->Action" yeah seems like perhaps a bug with extra torrent rather than the app its self. but it down look like initial upload does go into the correct section
Seems I got the error reporting wrong it should say:
"[05:25:59] error: Did not receive 200 code from kat.ph"
I have fixed this wording and updated a few other little things.
seems the reason for that was because bayimg.com was possible unreachable at the time from your location. if it cant communicate with bayimg it will just upload the torrent to TPB without a cover at all.
thanks for all the report thus far JKoop, very helpful!
Thanks again for the on going feedback guys. if you have any other suggestions please do let me know.
Currently I have planned:
- Adding BBcode support with the option on disabling it for some torrent sites (such as TPB)
- Adding support for more popular sites (currently working on ahashare)
- find/fix more bugs :P
@PsYcHaYoGi make sure you get your hash in correctly (without any spaces either)
Also I was not aware there is a captcha on upload?
EDIT: just registered a new account and saw this: "If you want to get upload api access, better search positions (and a cool icon:) just ask us and become a verified uploader! " so yeah only verified uploaders can use the API (sorry didnt know this before) but answers your questions at least (I also eddited the title)
the whole point of any API is to be able to remotely execute commands from one app to another. some API authentication is more complex than this one, which is just passing the credentials through the url POST. for example twitter uses oAuth for their API ( [url]http://oauth.net/about/[/url] )
all the info is coming from basic knowledge and trial/error here on kat :)
Find this hash in your SETTINGS sections under PROFILE
that HTML code sends all the data in the form through a POST method to the "action" url in this case its 'http://kat.ph/torrents/upload/,
to try visuallise it it will be like http://kat.ph/torrents/upload/?name?=Torrent+Name&catagory_name=Movies&userhash=28397y12hekdqh92h
etc etc. KAT api can take those variables, identify the uploader by the hash code and grab all the rest of the data and upload to site under that uploader account.
all auth is done using your account hash, meaning if I gave you my hash string then it measn you can start uploading torrent under my account using this API without ever knowing the password. (thats how api auth works, using a unique hash code)
anyways so I had a wee bit of a play and finally got it to work. here is a short guide how to use it.
For all the people wondering "Why the hell would anyone want to use this?!"
The template I uploaded is just simply an example of how to use the example, it wasnt meant to be pretty :P
Using this example you can help you integrate it into your site (something I persoanlly plan on doing) so all uploads are done automatically and in real time.
AUTOMATION IS BEST!
Anyone? surly someone out there uses it :P
Have a day mate
Thank you for the display picture!!!pretty epic man!