Donate Share

JBidwatcher

Tracker: Feature Requests

3 auto-sniping overage percentage facillity - ID: 1624810
Last Update: Comment added ( sf-robot )

I'll try to explain this as simply as I can - my wife understood what I
meant..:-)

Let's say I'm watching an item that has 5 days to go, and is currently at
$500. Now, there's no way of knowing what proxy bids are in place, so if I
set a snipe of (for example) $650 it may still be below the highest bid as
displayed or the proxy for that bid.

What I'd like to be able to do is to set a snipe with the following
parameters (mu poor attempt at psuedo-code follows);

if current-auction-amount < my-snipe-amount
set snipe-amount to current-auction-amount + minimim-bid
snipe
fi

if current-auction-amount > my-snipe-amount
AND my-snipe-amount-overage = TRUE
set my-snipe-amount = my-snipe-amount * overage-percentage
if my-snipe-amount < current-auction-amount
end
snipe
fi

So that if the current auction amount is > than the amount you are willing
to pay you can set a percentage of your snipe amount (the overage) that the
program is allowed to exceed your snipe amount buy. If this is still less
than the current auction amount, do not snipe.

Make sense ?




Jon ( moldor ) - 2006-12-30 11:11

3

Closed

Wont Fix

Morgan Schweers

Bidding/Sniping

Configurability

Public


Comments ( 3 )




Date: 2007-01-22 03:20
Sender: sf-robotSourceForge.net Site Admin


This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).


Date: 2007-01-07 21:32
Sender: cyberfoxSourceForge.net Subscriber and DonorProject AdminAccepting Donations


Greetings,
I mostly agree with the previous commenter; the best way to bid is to fix
an amount you're willing to pay for an item, and bid it once and late (i.e.
snipe). That's what JBidwatcher aids in doing.

The 'overage percentage' is tricking yourself by saying, 'I'm only bidding
$500', when you could actually be bidding as much as $600 (with a 20%
overage). And what happens that time when you forget the overage
percentage is there, and actually bust your budget?

But the real reason I'm not comfortable implementing it, is that
JBidwatcher does not do a final 'how much is the item' check before placing
the bid at the end of the auction. If it did, that would be an additional
network round-trip, and that would interfere with the accuracy of the snipe
timing, and opens up 'race conditions'.

The simplicity of placing the final bid is the key, in fact, to getting
relatively accurate snipe timings. Older versions of JBidwatcher did a
great many things during the snipe time, which tended to make it less
accurate. Now it's very limited in its behavior, doing most of the work 2
minutes in advance, and just a single-page submission at the end.

Since in most auctions the majority of the activity happens at the end,
anything more complex (like the feature suggestion) might just fail as
often as it succeeds. Mainly when a bid comes in *after* the 'amount
check', but *before* the 'snipe submission' phase, so the program thinks,
'It's okay to submit the base bid', but in fact that amount will lose, but
the program didn't know that because it hadn't seen the bid that came in
right after the amount check. Then you'd get mad at me, because
JBidwatcher didn't bid the overage (which would have won the item), and it
ended up going to someone else...

Just bidding the extra amount that you're comfortable bidding should
usually behave better, and is less potentially error-prone.

-- Morgan Schweers, CyberFOX!



Date: 2007-01-07 17:11
Sender: nobody

Logged In: NO

This doesn't seem to make any sense to me. Why don't you simply start with
the higher snipe-amount from the beginning? Or should that be a
psychological trick to make you give away more money than you could
afford?



Log in to comment.

Attached File

No Files Currently Attached

Changes ( 8 )

Field Old Value Date By
status_id Pending 2007-01-22 03:20 sf-robot
close_date 2007-01-07 21:32 2007-01-22 03:20 sf-robot
artifact_group_id None 2007-01-07 21:32 cyberfox
priority 5 2007-01-07 21:32 cyberfox
status_id Open 2007-01-07 21:32 cyberfox
close_date - 2007-01-07 21:32 cyberfox
summary auto-sniping facillity 2007-01-07 21:32 cyberfox
resolution_id None 2007-01-07 21:32 cyberfox