SharpLeech 2: Discussion and ideas topic.

Status
Not open for further replies.
devilahead; A little guide on how to use SL would be good on the application itself. I've noticed that members put the wrong forum ID for each category. For example, Apps is 6. X user puts in 5. The apps are posted in a random section, which is a pain in the arse. Those members who don't know how to use SL shouldn't be using it, but hey, even I didn't know how to use it in the first place. Took me some time figuring it my self /noob. A video embedded on SL won't harm anyone.
 
Also, I'm not sure whether this has been implemented but what about the option to auto-update? The option should be added only if you wish to continue developing SL. I don't see a point in "auto-update" if the creator doesn't update the software. :P

I have been considering releasing both an installer and a portable zip'd version. that is, after the alpha and beta releases. The installer would check for updates each time the program starts.

To be honest, the amount of updates after v2.0.0 will depend on the support I get with 2.0.0. By support I mean amount of users and donations. Considering the amount of time I'm spending on making this it should really be paid/premium software. Keep in mind that I have no use for the program myself. But that's not me. If it's not worth it making it for free it's not worth it to continue making it at all. That's how I see it.

what about an admin program which lists all the users using sharpleech "atm" and the option to disable leeching from the "admin" program. Obviously you will be the only one able to administrate the users. :P A lot of other options could be added to the admin program such as "Global announcement" -- I think this should be done for 4.0 lol. Quite a few members use the program to spam sites and it's annoying. Another thing.. I extremely hate users who leech threads and post 50k threads in 2 weeks. The ability to block the shit would be great (via robots or something) :)

You'll be able to see who's currently using the program by looking at the names listed in the ChatBox. All active users are always in contact with each other trough it. The ChatBox future is one of things I'm personally looking forward to because it'll be fun to see how that plays out.

There will be something similar to the "Global announcement" suggestion. Namely the Feed tab. Actually I'm surprised no one has asked me what the hell it is yet, lol. Anyway, Feed = news feed. It will show the latest news, update and announcements from the site.

I have thought about adding the ability for site owners to block SL via adding a txt file in the root folder or something similar. Only the posting part though. It wont be in 2.0.0 but it has a high priority so it might get added in 2.0.1.

devilahead; A little guide on how to use SL would be good on the application itself. I've noticed that members put the wrong forum ID for each category. For example, Apps is 6. X user puts in 5. The apps are posted in a random section, which is a pain in the arse. Those members who don't know how to use SL shouldn't be using it, but hey, even I didn't know how to use it in the first place. Took me some time figuring it my self /noob. A video embedded on SL won't harm anyone.

When the program is done and someone wants to record a tutorial, feel free. If it's a good one I can sticky it on the site when it's up (after the alpha).
 
Dilemma:

Should I release a Pre-ALPHA before the actual ALPHA? What do you guys think?

The good thing would be early bug spotting and giving you guys an early taste of what is to come. The downside would be some not yet implemented futures (such as the parallel/async posting pipeline, stats tab and the feeds tab etc).

Done:
- Sync Leeching & posting (#Leech 1 method, rewritten / tiny bit faster)
- ChatBox
- Most of the GUI
- Plugins compiler and parser
- Dupe topics prevention
- Radio
- Manual login (ability to login via a browser if all else fails)
- Http request manager
- Site Encoding detection
- Monitor

Not done (planned for the ALPHA):
- Error logging
- Async Leeching & posting (The fast #Leech 2 method)
- Stats tab
- Feed tab
- Some of the non-essential options.
- Cookie and cookie domain manager

Can't make up my mind :(. Right now the current build is working pretty well with the completed futures. A Pre-ALPHA would mean a release in less than a day.
 
I cant see why it wouldn't hurt. It could help you fix more bugs for alpha and even more before the final release. Honestly its totaly up to you though. Wouldnt make a huge difference.
 
Done:
...
- Plugins compiler and parser
...

So yes. The default sites are plugins too now. While making the PornBB plugin I noticed a nice plus point of the plugins too. Because you can easily edit them you can add VIP sections. I know webmaster wont like this though.

Code:
        <!-- If you have an account with VIP access you can un-comment this (:
        <Section title="VIP / Donators Only" id="24" />
        -->

@Deleted:
Reason why I'm not sure about it is that it doesn't reflect the performance the final will get. People tend to think that ALPHA releases are pretty much the same as a final but unstable. In this case it's fairly stable but just not at full speed and missing futures.
 
Hyperz,

Auto Update FTW!!! Dude :| If you need a place too host the updates since it would have too Auto Dload from server lemie know <3

An actual install process would be very nice too :)
 
I was gonna post it yesterday evening but I discovered part of the WebRequest handler was behaving strange in some cases so I just went to bed <_<. It'll be done today though I promise!

Hyperz,

Auto Update FTW!!! Dude :| If you need a place too host the updates since it would have too Auto Dload from server lemie know <3

An actual install process would be very nice too :)

There will be an installer with auto updates when the program is out of beta/alpha. The hosting is not a problem atm and a site will be up once the ALPHA is out (note: alpha, not the pre-alpha).
 
I don't know if this has been asked, or if it's a bad idea, but could you do it so when it gets the download links from a site it checks if they're dead and if they are it doesn't post the thread?
 
Has been asked many times. The answer stays that link checking should be done on the server side. Via a script or cron job.

PS: uploading SL_2.0.0_Pre_ALPHA.zip now.
 
Status
Not open for further replies.
Back
Top