Topic

Minor complaint about auction ordering.

Auctions are ordered by price, then by time with newest coming first within a given price point.

Auction visitors tend to find a quantity and price point they want and then pick the first one.  

This means that an auction for an item at a given pr/qty can get "pushed down the stack" by the addition of other auctions at that very same pr/qty.   While not horribly unfair, it is sorta unfair.  

Eg.  100 cherries at 200c.   Assume I add 5 auctions like that.   someone can come along a few minutes later and add 5 or 10 more auctions for 100 cherries at 200c and their auctions will be the first ones that shoppers see, and probably select.  

Fixing that should make for some interesting SQL.   Thanks for reading this. 

Posted 14 months ago by WalruZ Subscriber! | Permalink

Replies

  • Why shouldn't be new cherries be shown at the top of the list. They are fresher and more delectable than your 12 minute old cherries.
    Posted 14 months ago by Bashere Subscriber! | Permalink
  • Not sure if it's that way by design or not, but I've asked one of our developers to take a look into the design.
    Posted 14 months ago by Beefcake Subscriber! | Permalink
  • This is a little old topic, but I was browsing the auctions today... figured I'd use an old thread rather than start a new one...

    Any newer auction - never mind the price - pushes down the stack.
    My wish is to be able to sort them a little: time, price per each, total offered and total price would be key, glitch name might be nice too, say, if we wanted to buy from a friend.

    Cheers!
    Posted 13 months ago by BlueBetsy Subscriber! | Permalink
  • sorry tho, this isn't really a bug...I should have checked that.
    Posted 13 months ago by BlueBetsy Subscriber! | Permalink