Hey Ni9ce Progy Bro i like it when 2.0 will be released?
I can't put a date on it. It depends on how much I feel like working on it per day - if at all - as wall as other factors such as unexpected bugs both in my code or in .NET 4.0 (since that is still in a pre-release stage as well atm).
In other words: when it's done.
- Support for other big porn forums (other than pornbb).
- History check. A full log of the urls leeched so #Leech skips already posted threads.
- A plugin/template system so people can add other forums.
- Username/Password history (or a save login option).
- Automated stop/pause after X time and/or after X leeched threads.
As I've said a few posts back, 2.0.0 is future locked. A plugin system is one of the main things I want to have in there. And one not limited to site plugins but a system that allows other parts of #Leech to be extended as well. For example, adding extra tabs/functionality to the program itself.
There will be no history future. In fact, unlike 1.x.x, passwords won't get saved at all. This is not to annoy users but to prevent your login info from being stolen by
stealers. In addition to that, the passwords are encrypted while in-memory so that they can't be logged by other dodgy apps.
There will be one way of controlling how long #Leech should leech in one go and that is trough setting the maximum number of pages it can leech from a site.
Hyperz said hopefully by the end of the month If I remember correctly. Read through the thread.
I said in a best case scenario it would be done in about a month, not the end of the month
.
Regarding the possible plugin system for adding sites, y'all need to keep in mind that this can't be done in a Multi-Poster way where the templates are simple xml files. Multi-Poster posts, a leecher does leeching AND posting. Since #Leech doesn't need templates or plugins for the posting plugins will obviously be for the leeching part.
That's a big difference. Posting can be done by simply calling 1 url and sending variables. Leeching on the other hand involves parsing pages to extract the data needed for the posting part. What this means is that for a good amount of sites a simple xml file will not be enough. Coding will be required to tell the program how to get that needed data. This is because most sites have a unique DOM (html structure). So I'd guess creating a plugin won't be THAT easy for most.
Having said that, don't worry, if there is gonna be a plugin system it isn't gonna use .dll's. I'm thinking about using xml with embedded javascript and compile that at runtime to in-memory CIL bytecode or cache it to .dll's.
Pseudo code/xml:
PHP:
<Plugin version="2.0.0.0">
<Config>
<Name>Warez-BB</Name>
<BaseUrl>http://www.warez-bb.org</BaseUrl>
<LoginUrl>/login.php</LoginUrl>
<!-- More tags ... -->
<!-- Etc. -->
</Config>
<JScript>
import System;
import System.Data;
import System.Net;
import Hyperz.SharpLeech.Engine;
package Hyperz.SharpLeech.Plugins
{
public class Warez_BB implements SiteReader
{
public override function GetTopic(topicId : Int32) : SiteTopic
{
// Do some shizzle
var result : SiteTopic = new SiteTopic("bleh", "bleh");
return result;
}
public override function ToString() : String
{
return this.Name;
}
}
}
</JScript>
</Plugin>
Just an example to paint the picture. Not as hard as having to write a .dll but not that easy either (if the target site would require you to override default functions that is).
It really shows what kind of a person you are
