I'm too paranoid about a rogue hacker to store any sensitive information on BQB
While I have no plans to store any sensitive information on BQB, I am looking into a security upgrade and have been speaking to a company which specializes in making websites "hacker unfriendly".
There is currently a lot of damage a rogue hacker or user could cause -- eg. Clicking BIN on all domains which are BIN enabled and then opting not to pay for any of them or even just bidding on everything and then not paying for anything.
I will try to implement a system like on Sedo where a user is only allowed to have a certain number of existing bids at one time. The number will be high enough that it's likely to not cause anyone any trouble, but low enough to prevent someone from ruining everyone's auctions by sending out 1500 bids.
That sounds good to me Rich
Will bounce that off the developers. Hoping to make a few changes in coming weeks, such as your suggested login box near the top. Developers are working hard on a bulk lister at the moment and fixing the login box will be the next priority -- I might as well get them to implement this "Remember Me" feature at the same time.
I'm not sure what's causing the slow speed -- BQB is running on an 8x 2.66ghz dedicated Xeon server with RAID 10 SA-SCSI config, so I don't think it's the server's specs causing the problem and it's likely a problem in the code which is causing far too much load on the server for the amount of traffic being received.
I'll be hiring a company to take care of server upkeep shortly.
Bulk listing capabilities should hopefully be up within 1 week -- undergoing bug testing as we speak
There's a lot to look into and consider to make sure the escrow service is implemented correctly. It will only be offered for transactions under $500 once implemented (escrow.com being the recommended choice for larger transactions).
