difference \"HIGH BIDDER\" and \"outbid\&quo

[ramses82]

Hi today on gixen it showed that i won two items.
but on ebay it showed that i was outbid.
latter on gixen it showed "HIGH BIDDER" which i never saw before.
some thing feld special on this loss. ....
( 301729924037 )

can some body maybe explain me the differences?
and why it showed first won, and latter HIGH BIDDER?

Cheers,

[Cupid]

I must admit I have never seen HIGH BIDDER as a status here on Gixen either.

Can we clarify, are we talking about the here on the web interface or in the Gixen Desktop Manager?

I know there is a field called 'High Bid' in the GDM... that is labelled as 'Current' here on the web interface and represents the auction price.

As an aside... It might be a good idea if, at some stage, we sorted out that things are consistently labelled between the web interface and the Gixen Desktop Manager... that might alleviate some of the confusion we sometimes encounter.

Can you give further information about where this HIGH BIDDER was/is displayed, please?

On item 301729924037 was your snipe bid amount 5.31, 6.00 or 6.50 or above or, put another way, do you currently have a 518, 189 or 39 feedback rating?
_________________
Mark

[mario]

There is no difference really - in the database it's recorded the same. I think at some point in some places of the interface I replaced the message with "WON", and to be honest I don't even remember when and why.

[ramses82]

Thanks for the replies,

it was in the "web interface". my rating was 189. Well it is not really a problem. But i never saw it before. And since first the gixen page told me that i won the item, but latter it appeared, that i didnt won the item, so it was a bit disappointing, although i never had expected to win it with this bid* but because i never had any problem with the site like this before i thought it might be something special, worth to mention. It happened twice actually that day. (two similar items)

Maybe its a small bug, and probably it doesnt happen a lot. But if you could find it and fix itso that other people dont have to go trough the lightly emotional disturbance of thinking that you won something, and then, get dissapointed that you didnt.

*In this case used gixen as an extended watch list, by making a low temporary bit, that i will raise later. (if i have the funds, depending on other auctions).

[Gixen]

[Cupid]

Right, so on the auction you mentioned the bid was successfully placed and you were the highest bidder until an later snipe bid was entered on Ebay, at which point you were outbid.

Detection of that scenario has to be made as a separate step after the auction has completed.. if that detection had been successful you should have had a status of 'OUTSNIPED'.. but from what you say it sounds like that last step was not successfully completed in this case.
_________________
Mark

[ramses82]

Hi Sorry to come back on this,

But this issue caused me a problem again today.
I had a grouped snipe on ram.
item 221891167731 my bid 23 euro, It showed high bidder,
so like last time, probably first it showed won, and then it appeared that i didn not win,

now in the same bidding group there was also a snipe on item
item 231691933696 , but it was cancelled for whatever reason, i guess the false and temporary win status.
with my bid i could have had the item, its nothing big just 22 Euro's now.

But similar things could happen on other items, and other people,
could you please try to look, what causes, this funny glitches, in the website. I never had such problems before only since 2-3 weeks now.

Thanks any way for the great website.

[Cupid]

Yes, it does look like this was another undetected 'OUTSNIPED' situation on the first auction 221891167731 ... and I agree when this failure occurs as part of a Group it does affect the outcome of later snipes that are erroneously cancelled, as in your case.

Periodically Mario does check that this feature (Outsniped detection after the auction has completed) is operating as effectively as possible... this might be one of those occasions where it needs checking once again?
_________________
Mark

[ramses82]

I guess it is currently checked it as fast ass possible to, cancel in time other planned bids in time. That is OK, but maybe its possible to also run another check 6 seconds after the first check, just also to catch these exceptions, even if they are only few.

dont get me wrong, i am really happy with the website. It is just a suggestion.

Another unrelated suggestion would be to have AND snipe groups.
so if i would win one trigger snipe that i want other snipes to be excecuted, and other wise not. (but maybe this gets to complicated for the user interface). And of course false final auction status would be annoying here to.

Thanks for the response.

[Cupid]

I can't comment in detail of an implementation of your first suggestion, since I do not know the details of the Gixen implementation... However, I find it hard to believe that it would be efficient (or even possible) if you are suggesting that the first check operates as now but that a second should then re-enable cancelled snipes if it subsequently found you had not won the original auction after all. If you are suggesting the check is just made later, that might increase the reliability of it, I don't know... but I suspect there would still be failures to detect those later winning bids, occasionally.

On you second suggestion please check out what is known as 'Contingency Group Bidding' here on Gixen... it has to be enabled on your Settings page before you can start using it.
_________________
Mark