On Jun 27, 2011, at 5:01 PM, Zachary West wrote: > On Mon, Jun 27, 2011 at 17:44, Evan Schoenberg, M.D. <eva...@dreskin.net> > wrote: > > On Jun 27, 2011, at 12:00 PM, Colin Barrett wrote: > > > While Evan was working on updating the code, he noticed this as well. After > > some digging, it appeared the application we had been using was disabled. > > So we registered it again. > > Further search of my spam folder shows an identical email dated 6/8/2011. I > do recall being randomly (it seemed) forced to change my Facebook password, > though at that time they didn't have an informative message as to why or > pointing me to search for an application-related email. > > > Me too. Was I listed as a developer on that one?
You were. Hadn't had a chance to ping you about it yet; I hadn't added you as a developer yet because they now require it to be a 'fully verified' account, which means either verifying with your cell phone or a credit card. > Another guess: they routinely look for 'phishing'-looking Applications, and > disable them. It's possible that they realize up until this point there isn't > an official Adium implementation using the FB API so they nail them. > Hopefully they respond to your email, if not we can try our usual methods > (blog post, Twitter) to see if we can find a contact inside FB to ease this a > bit. > Yeah... we'll give them their promised 48 hours and then open the PR floodgates (kindly and professionally, of course!) :) -Evan
