TBR Musings - January 19, 2022 (1.Viewing)

  • Topic Starter Eby
  • Start date
  • Replies: Replies 27
  • Views: Views 755
DomainRecap said:
Is this just an archaic way of MyID telling bidders that they need to bid higher in order to win? Does the first person to place a bid automatically get the $61 bump?

Yeah, since MyID allows multiple bidders at the lowest $60 level, after they've secured the domain, they bump up one of the bidders to $61 just so _someone_ is in the lead. You can't start an auction with a 10-way tie at $60 each because if no one bids, you wouldn't know who to assign the win to. So MyID corrects that scenario by bumping up one bidder to $61. I'm not sure its documented anywhere, and I'm honestly not sure if its the first or last or a random bidder who gets the $61 bump. So its definitely not clear, but I understand the logic behind it. Might not be the best way to handle it, but that's how they've always done it.

I'd think the logical thing to do would be assign the first bidder as being in the lead and NOT change the price at all. But I'm guessing that they way they've coded the software, that would have caused them extra work. So rather than doing it right, they came up with the +$1 kludge.
 
rlm said:
You can't start an auction with a 10-way tie at $60 each because if no one bids, you wouldn't know who to assign the win to.

Actually, that's exactly what Siber does in the event of a tie (happens quite a bit with last-second bids), they display the same bid amount on both accounts, with one winning and one losing - that's one reason I asked about this.

I kinda knew what was going on, and to be honest, I was far more interested in whether I had missed on a "secret method" to input different bid amounts than $60, $75, etc. That would be a real auction trick if you could do it.

I also asked MyID support for clarification and it's pretty well what I surmised in the last part - their system can't handle ties, so the first bidder always gets the $1 bump as a kludge to make the auctions run as intended. While this format won't affect premiums, as prices will go way beyond $60. when you're dealing with mid-range domains, it could be a real advantage to being first bidder.
 
  • Like
Reactions: rlm
Man, I literally have no idea what is going on at MyID and taking part in their auctions is like learning a new language.

I placed a proxy bid at $252, and then I received this email:

You have been outbid.

Current Bid: $252

Your current bid: $241
Your proxy bid: $252


I was busy at the time, and thought it was just an error, as the Current Bid was equal to my Proxy Bid and I decided to wait for another email stating a new price. It never came and by the time I got back to my laptop, the auction was gone.

Now if someone outbid me on any other auction platform the price would go up by the next bid increment, of $11 on MyID I believe, or $263. None of this makes sense, unless MyID doesn't like money and if someone outbids you, they leave it at your old bid... but that doesn't seem to be how it works from me bidding.

I think I need someone to give me a "Primer on MyID Auctions" so I can interpret all this data that seems to be incorrect or incomplete. Thanks.
 
Here's what I've figured out so far:

1) Proxy bids on MyiD do not work correctly.

2) Every bid against your proxy is accompanied by a "You have been Outbid!" email, no matter if you have actually been outbid or not.

3) If the other bidder equals your bid (and you're still in the lead as first bidder) you get the same "You have been Outbid!" email

4) But as it's viewed as a tie in the system (like the $60 to $61 kludge needed to start auctions) nothing further will be emailed when you are officially outbid.

I just realized this when I found 2 other previous "You have been Outbid!" emails at lower bid increments.
 
Dark-Carnival.jpg


Step right up! Prices, prices, who's got TBR prices??
 

Sponsors who contribute to keep dn.ca free for everyone.

Sponsors who contribute to keep dn.ca free.

Members who recently read this topic: 2

Back
Top Bottom