Page 1 of 2

Things needs to be done till 2.5.0.0 release.

PostPosted: 04 Aug 2009 15:38
by raspopov
Shareaza:

1. What to do with MediaPlayer plugin?
2. Languages update with SkinTranslate utility help.
3. Skins update, at least add IRC window and IRC navbutton.
4. Installer update. What to do with RazaWebHook64.dll (for IE 64 support)?
5. Re-style Shareaza icons a-la Windows Vista (or 7?).

Web-site:

1. Fix TorrentAid pages (update screenshots).
2. Add all skins to Addons page (with magnet links), so we can remove them from installer (except default ShareazaOS skin).

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 05 Aug 2009 04:45
by cyko_01

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 06 Aug 2009 20:29
by ocexyz

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 07 Aug 2009 00:21
by kevogod

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 07 Aug 2009 02:54
by zigozag

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 07 Aug 2009 12:50
by cyko_01

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 07 Aug 2009 18:18
by kevogod
There is no such thing as a secure solution for the update system. Adding digital signatures does little to change the security in my opinion. You are just moving the problem from possession of a URL to possession of a key.

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 07 Aug 2009 23:14
by cyko_01
ok, so everyone agrees that it should be disabled for now at least.

moving on

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 08 Aug 2009 06:38
by zigozag

PostPosted: 09 Aug 2009 10:57
by aaron_walkhouse
LimeWire seems to have figured it out. Fake upgrade notices don't happen anymore
so check out how they did it.

Re:

PostPosted: 09 Aug 2009 15:49
by kevogod

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 09 Aug 2009 16:46
by zigozag
Phex, a project managed by volunteers, has also recently implemented a similar feature. See "# Secure signed update checks, so noone can fool your Phex into trusting a false update" on http://www.phex.org/mambo/content/view/89/58/

Re: Re:

PostPosted: 10 Aug 2009 03:54
by aaron_walkhouse

Re: Re:

PostPosted: 10 Aug 2009 23:34
by kevogod

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 11 Aug 2009 15:42
by dataza
The two biggeest issues I see with a new release are:

1. IRC support has not been fixed. This has been a problem for users from the release of 2.4.0.0 where it debuted. It either needs to be fixed, or removed.
2. Search results counts STILL are being added up using actual hits of files present on the network, and old cached sources that can be easily faked. Releasing a version using this source count method is just asking for large amounts of doom. Please fix this before a release!!!

As far a an update notification mechanism, I don't think there needs to be one if there is any question that it could be abused again.

Also, if a new default skin is to be chosen, I'd vote for Tango2 if it is a candidate.

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 11 Aug 2009 19:00
by acerswap

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 15 Aug 2009 10:56
by whizzmoraza
I'd like to add "Stability improvements" to the list. The time it takes the nightlies to go from working app to "(Not Responding)" can be measured in minutes on my machine (quad core, fair amount of memory, only 23 security rules in place). Another post mentioned that this might be due to result sorting code?

/crossing my fingers

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 15 Aug 2009 14:33
by cyko_01

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 15 Aug 2009 22:03
by kathw
I was talking to one of the IRC experienced users who is helping in the channel and using the latest debug build, he said this..

<Cerberus> the chat applet in shareaza is still messed up and full of bugs
<Cerberus> even the " /part " function is broken now
<Cerberus> spanish channel is still called spain and not spanish
<Cerberus> still get 3 join notices of joining a channel
<Cerberus> still get part bug were if one parts 4 users follow for no reason
<Cerberus> multi quits for no reason
<Cerberus> still can not version check raza users
<Cerberus> channel list on page need making longer so all channels appear on it
<Cerberus> basic stuff that needs fixing

Hope this can be looked at before the release, it's one of the main meeting points for users :)

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 20 Aug 2009 11:32
by old_death

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 20 Aug 2009 18:58
by ocexyz

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 20 Aug 2009 21:01
by zigozag

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 20 Aug 2009 23:01
by ocexyz
:roll: NO, even bed (bad?) IRC client is better then none. And it is at the finger tips. We need to have opportunity to keep communication alive. Just because we are frendly group of friends and we have nice global community. This is nice I think. :mrgreen:
And through this client we can say which better client user can use to stay in touch. :mrgreen:

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 21 Aug 2009 00:21
by kevogod

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 21 Aug 2009 06:53
by ocexyz

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 21 Aug 2009 15:45
by old_death

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 21 Aug 2009 17:31
by cerberusstyle

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 22 Aug 2009 01:28
by kevogod

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 22 Aug 2009 01:36
by ocexyz
This is ridiculous: who has observed IRC crashes Shareaza? On 8136? I have seen no report about that in tracker. No ticket, no bugtrap report, no drWatson report, no post reporting, no person reporting... what we are talking about?? IRC is just needed, and is just to be developed further, but not canceled. :o especially when forum work as it works. :|

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 22 Aug 2009 08:40
by andhee
i don't know how developed shareaza last built, but few suggestion from me:

- develop direct link support so it can perform like other download manager (do not treat direct link like other source p2p client)
- connect to dianlei client, so we can have bigger network
- win 7 bug free

that's it for a while :)

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 22 Aug 2009 19:53
by ocexyz

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 23 Aug 2009 09:07
by hamsterkill

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 23 Aug 2009 13:33
by cyko_01

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 23 Aug 2009 20:26
by andhee

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 24 Aug 2009 06:18
by ocexyz
In Librarry, in [folders] view I can rightclick on folder name eg Downloads and in rightclick menu I can select [delete] but I can't do the same there on subfolder eg. subfolder in folder Downloads containing downloaded via torrent folder. Usually torrents are in folders. This should be enabled, or if there is a reason why I can't do it there should be window displaying message explaining why. I have to delete it with system while more logicall seems to do this from Librarry, if there is no any collision or sth like this.

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 24 Aug 2009 20:56
by ocexyz
There is folder "Torrents" where torrents are stored. I have made in this folder several subfolders for several types of torrents like "video" and others. I moved torrents to appropiate subfolders. When I open a torrent for doownloading from any subfolder there is no problem. But when for whatany reason (eg. no sources) I will close that opened torrent then in folder "Torrents" is created this closed torrent, but not in subfolder from where it was opened. I see no reason. So I have a mess in folder "Torrents" again, and second additional copy of torrent. If closed torrent is somehow modified then it should be modified in subfolder from which it was opened. Probable reason - I think Shareaa do not remmber from where, from which folder, the particular torrent has been opened, it should IMHO. But do torrents are subject of modification when I close them? I don't know.

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 27 Aug 2009 21:32
by sshanu
The problem of Shareaza trying to connect to bad G2 hosts I believe is an important one that needs fixing before the next major release.
This can go on for hours and hours sometimes & renders Shareaza totally useless while it's happening.
I know that some people have got so fed up with it happening they no longer use Shareaza :(

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 27 Aug 2009 22:32
by andhee
i remember few my old request from previous forum, i don't know this already implemented or not
this is not major update, only a small fix

- shortcut key
ctrl + home = move to top
ctrl + end = move to bottom
those two already implemented, but only for single file, if i chose 2 or more file, the shortcut key only work for last chosen file..

- ban user menu
right now on right click menu at search tab, we only knew 1 type of ban.. how about break into 3 type of ban under sub menu

ban/block
+ ban ip + urn (block ip + hashcode)
+ ban ip only
+ ban urn only (sometimes i only wanna block the file, not the user)

- stop seeding problem
when we stop seeding torrent file, raza should delete the torrent cache file in incomplete folder. it only works if the torrent is single file, but if the torrent was a multi file or a folder, raza didn't do this <- can you fix it?


that's it for now

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 28 Aug 2009 00:41
by atifox

Re: Things needs to be done till 2.5.0.0 release.

PostPosted: 06 Sep 2009 12:33
by zigozag
Please consider removing "Kademlia Cache" and "BitTorrent Cache" from the GUI of the Host Cache window as these features do not work and may be confusing for users.