krisrak

I got reply from Instagram that they are aware of issue and working on it.

I'm creator of https://picodash.com, I noticed the same issue about a week ago but did not get any complains from my customers, so debugged it for 8 hours until I found this (I know it will be hard to believe):

I kept getting "Matching code was not found or was already used." when using thru my oauth python code which btw has been working for 6 years now. But when I used curl to do POST, it worked, when I tried Curl again with same oauth code, it failed, So I think this is something that was recently changed by Instagram, the oauth code only works one time, I kind of remember this code could be used more than once before to make POST call, but there was time limit instead, after which using same code was failing.

So with me, this was always failing, but no complains from my customers, I could see logs that new people were signing up.

I started testing on localhost, I added debug logs, I did notice that there was 2 POST calls being made, so it was failing. I could see that 2 POST calls was made and first one did work and get access_token, but there was a second call made and this was error 400 and oauth flow was failing. Almost looked like a retry of POST call, cause my code should only make one.

I started trying different browsers, failed on all firefox,IE, safari, chrome. And then decided to try on my iphone, it worked 100%, so looked for difference, it was on LTE, so I guessed may be my wifi, switched to wifi on iphone and it started failing 100%. So now on my dev system, I connected modem directly to system without router and tried, it passed 100%, so it was my wireless router (I know weird), I tried another 3rd party instagram web app, had same issue but worked without the wireless router. So on Monday I got another wireless router and no issues, it started working. So this could be an isolated incident for me, I came to conclusion that I was using some old router that was dropping POST request and making second attempt and failing.

So I guess if this is affecting all your customer check you code by putting logs that you are making one POST request. Try making a CURL after you receive the code and make sure it is working on first attempt.

Today after reading this, I check my oauth login again, I did notice it fail few times, but when I try again, it is passing, so something changed again I think.

How about just using a gif image of pong in the pull-to-refresh block instead of all the complicated code

Finally there was security guard posted today for Banksy's art

I guess so, both are vandalism, but banksy's vandalism is preferred one if there was a choice

interesting thought

Yep, that's a known implementation gap, there was no simple way to implement it, do skipped it, will work on finding a solution, thanks

Good point, may be I should disable displaying electoral count for historical maps until actual numbers are implemented, thanks

Here is example of a predicted map: http://www.votenight.com/p/1tptn

votenight.com allows people to predict US Electoral map and share shortURL of the Electoral map. You can embed the electoral map prediction on your website / blog. Looking for any kind of feedback on this project that can make it easier and fun for people to use.

Nobody will win, they will be forgotten, just like how everyone forgot about group messaging apps after sxsw 2011

it depends on how big your data is, but every query operation, every fetch, every write operation it charged. http://code.google.com/appengine/docs/billing.html has details on how many read/write datastore API calls are made per operation. if u have to write in a new column for thousands of entries, then it will cost a bit, $0.10/100k operations, one re-write has 7 operations + incoming/outgoing bandwidth cost + instance usage cost will apply, it is hard to estimate actual cost.

1 - gramfeed is paid, http://code.google.com/appengine/docs/billing.html is correct, dont know what the other one is, i think that $9/month in minimun fee, i go past it anyway.

2 - datastore query is expensive but memcache works great, so cache frequently accessed data

3 - i make sure that whenever i put() any data, i immediately set Memcache, and before making any get() from datastore, I try get Memcache first, this should not cause issues.

yeah, one man team.

Yes, it is monetized by Ads and affiliate programs from photo printing companies

Here is how you pin blocked content to Pinterest in simple steps ;) http://blog.initlabs.com/post/18226946517/how-to-pin-blocked...