Shareaza bug with push downloads?

[Lanigiro]

[20:15:25] Host X.Y.Z.W is pushing download "File.ext", accepting.
[20:15:25] Requesting tiger-tree volume for "File.ext" from X.Y.Z.W...
[20:15:25] Download host X.Y.Z.W responded with 404 (File Not Found).

Obviously that shouldn't happen.

1. Unless I've used right click -> Advanced -> Add Source... it should not be possible for me to see 404, since the only sources should be peers that sent query hits for the file. That would mean the same peer first said it did have the file and then a minute later said that it didn't have the same file. Which would mean that a computer was mistaken or lying, when it should be both infallible and honest.

2. If the peer pushed the download itself it certainly has the file. It should not react negatively to a subsequent request for its tiger tree hash!

Since it was Shareaza at both ends on this occasion, the ball's clearly in your court.

[raspopov]

IMHO Gnutella 1 protocol uses "file number" (instead of hash) for pushing files which of course can change at any time.

[Lanigiro]

Wouldn't a Shareaza to Shareaza transfer use G2 protocol?

And why can I no longer seem to stay logged in for more than a very short interval at a time? And why do I again have to input my credentials twice each time I log in, with a bogus message claiming that there have been too many failed login attempts to my account lately? Has someone been trying to break into my account at this forum? If so, shouldn't they be punished rather than their intended victim?