Air Jordan Retro 5 "Doernbecher" release!! 9/14/13 No BOT TALK/SELLING/BUYING/TRADING

Something interesting I noticed about the DB5 product page link that @nikestore originally tweeted on release date.

So, this is the original tweet: . You'll notice that they used a URL shortener to shorten the URL of the DB5 product page that they linked to—no big deal here; most companies already use a URL shortener when they share links on Twitter and Nike's been doing that for a while now for releases.

As you can see in the tweet, the shortened URL is this: "swoo.sh/15qHRPN". Currently, if you click on that shortened URL it brings to you this page: "http://store.nike.com/us/en_us/pw/n/1j7?sl=page-not-found&cp=usns_twit_091413_doernbecher", which is a "No Matches Found" page.

However, on the release date, this was the original DB5 product page that you landed on when you clicked on the shortened URL from their tweet: "http://store.nike.com/us/en_us/pd/i...1/pgid-870387?cp=usns_twit_091413_doernbecher". However, if you now go to that link, it will redirect you to the same "No Matches Found" page: "http://store.nike.com/us/en_us/pw/n/1j7?sl=page-not-found&cp=usns_twit_091413_doernbecher". This isn't a surprise since the original URL is the link that was shortened, therefore, if the shortened URL (which is currently on the tweet) redirects, then the original URL also must redirect.

It's interesting that they would even redirect the original link to a "No Matches Found" page at all. Any idea as to why they would do that?
 
Last edited:
Something interesting I noticed about the DB5 product page link that @nikestore originally tweeted on release date.

So, this is the original tweet: . You'll notice that they used a URL shortener to shorten the URL of the DB5 product page that they linked to—no big deal here; most companies already use a URL shortener when they share links on Twitter and Nike's been doing that for a while now for releases.

As you can see in the tweet, the shortened URL is this: "swoo.sh/15qHRPN". Currently, if you click on that shortened URL it brings to you this page: "http://store.nike.com/us/en_us/pw/n/1j7?sl=page-not-found&cp=usns_twit_091413_doernbecher", which is a "No Matches Found" page.

However, on the release date, this was the original DB5 product page that you landed on when you clicked on the shortened URL from their tweet: "http://store.nike.com/us/en_us/pd/i...1/pgid-870387?cp=usns_twit_091413_doernbecher". However, if you now go to that link, it will redirect you to the same "No Matches Found" page: "http://store.nike.com/us/en_us/pw/n/1j7?sl=page-not-found&cp=usns_twit_091413_doernbecher". This isn't a surprise since the original URL is the link that was shortened, therefore, if the shortened URL (which is currently on the tweet) redirects, then the original URL also must redirect.

It's interesting that they would even redirect the original link to a "No Matches Found" page at all. Any idea as to why they would do that?


noticed this yesterday morning too even before the restock: the original twitter link redirects to a page that says "no matches found." so i'm curious to know how j23 or whoever discovered it first found the new link for the db5 restock because it's different from what was originally tweeted on release day.
 
Last edited:
Just got shipping conf 
happy.gif
 
Something interesting I noticed about the DB5 product page link that @nikestore originally tweeted on release date.

So, this is the original tweet: . You'll notice that they used a URL shortener to shorten the URL of the DB5 product page that they linked to—no big deal here; most companies already use a URL shortener when they share links on Twitter and Nike's been doing that for a while now for releases.

As you can see in the tweet, the shortened URL is this: "swoo.sh/15qHRPN". Currently, if you click on that shortened URL it brings to you this page: "http://store.nike.com/us/en_us/pw/n/1j7?sl=page-not-found&cp=usns_twit_091413_doernbecher", which is a "No Matches Found" page.

However, on the release date, this was the original DB5 product page that you landed on when you clicked on the shortened URL from their tweet: "http://store.nike.com/us/en_us/pd/i...1/pgid-870387?cp=usns_twit_091413_doernbecher". However, if you now go to that link, it will redirect you to the same "No Matches Found" page: "http://store.nike.com/us/en_us/pw/n/1j7?sl=page-not-found&cp=usns_twit_091413_doernbecher". This isn't a surprise since the original URL is the link that was shortened, therefore, if the shortened URL (which is currently on the tweet) redirects, then the original URL also must redirect.

It's interesting that they would even redirect the original link to a "No Matches Found" page at all. Any idea as to why they would do that?


noticed this yesterday morning too even before the restock: the original twitter link redirects to a page that says "no matches found." so i'm curious to know how j23 or whoever discovered it first found the new link for the db5 restock because it's different from what was originally tweeted on release day.

Was the URL that was active yesterday the same URL used for the DBV page on Monday?
 
My restock b%# keeps a file of the links. So here you go.
 
http://store.nike.com/us/en_us/pd/free-flyknit-running-shoe/pid-726167/pgid-831869
http://store.nike.com/us/en_us/pd/fuelband/pid-691776/pgid-670534
http://store.nike.com/us/en_us/pd/kd-vi-basketball-shoe/pid-745954/pgid-745955
http://store.nike.com/us/en_us/pd/air-jordan-3-retro-shoe/pid-725626/pgid-725627
http://store.nike.com/us/en_us/pd/air-jordan-3-retro-shoe/pid-881819/pgid-881872
http://store.nike.com/us/en_us/pd/air-jordan-4-retro-shoe/pid-725635/pgid-854426
http://store.nike.com/us/en_us/pd/air-jordan-4-retro-shoe/pid-725634/pgid-879500
http://store.nike.com/us/en_us/pd/air-jordan-4-retro-shoe/pid-881779/pgid-881874
http://store.nike.com/us/en_us/pd/air-jordan-5-retro-shoe/pid-725625/pgid-884515
http://store.nike.com/us/en_us/pd/air-jordan-retro-8-shoe/pid-153399/pgid-836574
http://store.nike.com/us/en_us/pd/air-jordan-retro-11-low-shoe/pid-684123/pgid-729562
http://store.nike.com/us/en_us/pd/air-jordan-1-retro-high-og-shoe/pid-725916/pgid-854427
http://store.nike.com/us/en_us/pd/kd-vi-basketball-shoe/pid-755648/pgid-859647
http://store.nike.com/us/en_us/pd/kobe-8-system-basketball-shoe/pid-689903/pgid-725602
http://store.nike.com/us/en_us/pd/lebron-x-celebration-pack-basketball-shoes/pid-858127/pgid-858139
 
 
http://store.nike.com/us/en_us/pd/free-flyknit-running-shoe/pid-726167/pgid-831869
http://store.nike.com/us/en_us/pd/fuelband/pid-691776/pgid-670534
http://store.nike.com/us/en_us/pd/kd-vi-basketball-shoe/pid-745954/pgid-745955
http://store.nike.com/us/en_us/pd/air-foamposite-1-premium-shoe/pid-721974/pgid-884483
http://store.nike.com/us/en_us/pd/air-foamposite-one-shoe/pid-721745/pgid-836575
http://store.nike.com/us/en_us/pd/air-foamposite-pro-premium-le-shoe/pid-810308/pgid-810385
http://store.nike.com/us/en_us/pd/lebron-x-ext-qs-shoe/pid-846698/pgid-846699
http://store.nike.com/us/en_us/pd/lebron-x-ext-qs-shoe/pid-854863/pgid-856783
http://store.nike.com/us/en_us/pd/mikes-air-max-95-le-shoe/pid-154713/pgid-848598
http://store.nike.com/us/en_us/pd/lances-doernbecher-dunk-low-le-shoe/pid-119588/pgid-884453
http://store.nike.com/us/en_us/pd/air-trainer-sc-high-shoe/pid-856840/pgid-809195
Was the DB3 link in here? I didn't see it. Thanks.
 
U guys think this is the last we will see of the db5 for retail?

damn close to it. Everyone that got the restock was all legit. Unless there's some hardheaded that order two pairs. They over sold their stock so I don't there's anymore. They said they only had what? 20 pairs. In that one guy video when he was talking to the manager.
 
IF THEY ONLY HAD 20 PAIRS THEN NIKE EMPLOYEES ATE THE REST UP BEHIND THE SCENES :lol:

THERE WERE A LOT MORE CANCELLED PAIRS THAN THAT. 100% FACT.
 
Just talk to nike on the chat and they said that these did restock and it wasn't a mistake on their part. Hopefully my pair goes through
 
What I dont get is if all the original db5 links didnt work, how did j23 stumble on a working one yesterday?
 
What I dont get is if all the original db5 links didnt work, how did j23 stumble on a working one yesterday?
 
What I dont get is if all the original db5 links didnt work, how did j23 stumble on a working one yesterday?
 
Back
Top Bottom