JOAL 1.0.3 / A new RatioMaster (command line and multi-os)

[CoreCore]

I don't use java on my system anymore. I will make to make a integrated portable one to test with lol

[anthony-joal]

I don't use java on my system anymore. I will make to make a integrated portable one to test with lol

:o Why in any world would you like to uninstall Java?

[kokoro]

This is really useful, now I can move all my BitTorrent related stuff to my Linux box.

I have a feature request for the 2.0 update:

I want to use JOAL to "fake-seed" torrents on my tracker (seed without uploading anything) for bonus points; since these torrents already have many seeders (10-20) it would be near impossible to get caught (as leechers will connect to the real seeders).

Would it be possible to add options so that JOAL can seed all torrents continuously at 0 KB/s? Currently JOAL only seeds one torrent for a set amount of time, and refuses to seed torrents if there are no leechers, making it useless for what I want to do.

I understand you are skeptical about adding options to disable these "safety" features since you don't want anyone to get banned. Maybe you could add a warning for people who try to disable them in the readme.md on the GitHub repo, and omit these options in the config.json by default.

[anthony-joal]

Yeah, the fact is, i heard about this "behavior" way to late. It is not a common practice in france, we did not have this feature on the main tracker.
But i will support at a time (maybe 2.0.0 maybe 2.0.1)

---------- Post Merged on 12.07.17 at 00:06 ---------- Previous Post was on 11.07.17 at 19:57 ----------

Here are a sample of the desktop app Joal desktop demo [2017.07.10] (will be beta-testable in few weeks)

Works to do before beta starts:

• Embed JOAL in the desktop app (currently working from IDE)
• Implement drag and drop torrents
• Display alerts for all errors and warnings
• Add auto-updater

[anthony-joal]

Some news about v2 development:

• Desktop app: Drag and Drop for desktop app is now working.
• Command line tool: Clients format and generation have been refactored. It emulate perfectly a variety of clients see supported client table here.
• Command line tool: All clients files have been updated to last version.

For those interested, a new beta build for command line application is available. It should now be completly undetectable (for the most advanced users you can check the clients files here to make your own opinions).

If you want to access beta builds and chat with other testers send me a private message or a email at : joal.contact@gmail.com. I'll send you a Slack invite.


And one last thing, thanks to all of you for your support :) i really apreciate. Be sure that you'll be firsts to know when V2.0 will be released (after beta testers of course).

[Blocker]

looking forward to try v2

[gnome9er]

yup me too. im amazed to see only 10 installs on this, since its at the top of the list. the simplicity is amazing. i will email about beta testing.

[anthony-joal]

Thanks for your support :)
I think most people don't wan't to bother with Command Line Applications, it should increase with the incomming GUI.

[anthony-joal]

Hi, i got a question and i dont know where to ask so... I'll ask here.

I've seen that most of the client file available on this forum are encrypted (or at least obfuscated) why is that so?
I was going to post a topic about bittorrent client file format, where i could share my knowledge about :
- key generation
- peerid generation
- announce format
And so on for each bittorrent clients.

@anon Before to do so i would be sure there are not problem to post such a topic.

[Cr@zYiNsEiN]

I've seen that most of the client file available on this forum are encrypted (or at least obfuscated) why is that so?

Encrypted as in? Please be more specific! If you've noticed client files in the mRatio, RatioMaster+, VEM sections, these client files aren't encrypted. They were made using the same algorithm of the original Torrent Client to support the ratio tool it is assigned to.

i.e., Let us consider we are talking about a recent client file http://www.sb-innovation.de/showthre...threadid=33421 client file will contain all the perquisites that the original torrent clients contain.
The spheres it will cover are:
1) Qb client's name.
2) The number of reserved bytes the qB saves.
3) The Prefix of qB PeerID it generates.
4) The length, charset, encryption, of the PeerID and Key for qB. Whether or not it is recursive (repeating in the single instance).
5) The way it reports the info-hash of the torrent file.
6) Parameters, protocols used by qB such as uploaded, downloaded, IPV6 (if present), scrape parameters, etc. I'm sure you've got my point. This information when combined into a client file helps the assigned tool to simulate the Orginal Torrent Client.

If you were talking about something else, please specify it.

I was going to post a topic about bittorrent client file format, where i could share my knowledge about :
- key generation
- peerid generation
- announce format
And so on for each bittorrent clients.

Help is always appreciated in all forms, after all, we are a free community. i.e., providing services to the general public for free.
Many client file makers will appreciate your work as it saves them the time to capture announces to create a client file.

Before doing so, I would like to be sure that there is no problem to post such a topic.

Good idea! I don't know of a current section which can benefit from the information you will share. Perhaps you can request for one section for this purpose specifically. It will help members build client files and clear the doubts when something seems dubious.

~cloud99

[anthony-joal]

@cloud99 thanks for your detailed answer.

Indeed encrypted wasn't the correct word, it was actually "encoded", looking at the file you linked, on first glance it looks like BEncoding for those ones. And it makes sense to do so since these kind of app have a BEncoding library anyway.
I shouldn't have my mind clear when i was looking at that ^^.

New section query is available here.

Thanks for your answer.

[anon]

I've seen that most of the client file available on this forum are encrypted (or at least obfuscated) why is that so?

The authors of mR and RM+ decided it was a better idea to limit the creation of client files to a restricted group of people, who were/are given access to a private program for this task, to eliminate the chances of faulty or fake clients from reaching the public. Naturally, since client files are essentially text, some sort of obfuscation had to be added, or else there would be no difference.

This is not a requirement or "the right answer" by any means. VEM and the original RM don't do it; in the former case ghostfucker actually found it desirable that anyone could create clients, so that they'd do it themselves and wouldn't bother him with requests!

I was going to post a topic about bittorrent client file format, where i could share my knowledge about :
- key generation
- peerid generation
- announce format
And so on for each bittorrent clients.

@anon Before to do so i would be sure there are not problem to post such a topic.

Everyone is allowed to start threads about things they find relevant, no express permission is required for this

As for a new section dedicated to this matter, I've posted my thoughts on your request.

[anthony-joal]

Thanks for the subsection anon. Now let's hope people take some time to contribute on these topics.

[anthony-joal]

Hi there, i have some good news.

The WebUi (WebUi only, desktop app will come soon but not yet) is almost ready to be alpha-testable (a matter of days). If you are interested in becoming a beta-tester let me know.


You can take a look at how it looks here.

[klown23]

Thats looks awesome!
I have used the command-line version and it was great. I would be happy to become a beta-tester.