New Developer Alert for Adium

[Evan Schoenberg]

_____________________________
From: Facebook <notification+***@facebookmail.com>
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
To: Evan Schoenberg <***@gmail.com>





Facebook






Hi Evan, This is a follow up to the Dev Alert sent on February 25th. It looks like your app “Adium” (164063256994618) is actively using the XMPP Chat API. As we announced a year ago on April 30, 2014 the XMPP Chat API will be deprecated starting on April 30, 2015. After that date, this app will not be able to send or receive Facebook Messages via chat.facebook.com , and the xmpp_login permission will be removed for all new and existing users. To prevent broken experiences for people, we recommend you remove Facebook Chat functionality from your app before April 30, 2015. For more information about this as well as the other API changes which come into effect on April 30, 2015 please read the changelog You can view this and other Developer Notifications related to your app, Adium, in the App Dashboard . Thanks, The Facebook Team



facebook DEVELOPERS


















Hi Evan,








This is a follow up to the Dev Alert sent on February 25th. It looks like your app “Adium” (164063256994618) is actively using the XMPP Chat API.


As we announced a year ago on April 30, 2014 the XMPP Chat API will be deprecated starting on April 30, 2015. After that date, this app will not be able to send or receive Facebook Messages via chat.facebook.com, and the xmpp_login permission will be removed for all new and existing users.


To prevent broken experiences for people, we recommend you remove Facebook Chat functionality from your app before April 30, 2015.


For more information about this as well as the other API changes which come into effect on April 30, 2015 please read the changelog





You can view this and other Developer Notifications related to your app, Adium, in the App Dashboard.


Thanks,
The Facebook Team

























This message was sent to ***@gmail.com. You are receiving this email because you have chosen to receive developer updates from Facebook. Want to control which developer updates you receive? Go to: https://developers.facebook.com/settings/
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303

[Christopher Forsythe]

13:23 -!- Irssi: Join to #adium-devl was synced in 0 secs
13:24 < The_Tick> heyo
13:24 < xnyhps> Hi The_Tick
13:25 < The_Tick> hey how have you been?
13:25 < xnyhps> Really busy, hardly any time for Adium left. How are you?
13:26 < The_Tick> the same
13:26 < The_Tick> but life is good now
13:26 < The_Tick> the facebook xmpp thing
13:26 < The_Tick> is anyone working on whatever replaces it?
13:26 < xnyhps> Nope
13:27 < xnyhps> Well, maybe one of the Pidgin guys, but I doubt it.
13:28 -!- notjosh [~***@cable-89-216-22-24.static.sbb.rs] has quit [Quit:
<sleeping>]
13:28 < The_Tick> who is left to write code?
13:29 < xnyhps> wixardy and me
13:29 < The_Tick> and that's it?
13:29 < xnyhps> Yeah
13:29 < The_Tick> oh man
13:29 < The_Tick> has any work been done on this yet?
13:30 < xnyhps> Not by me, and I doubt wixardy has.
13:30 < The_Tick> mind if I paste this chat to the mailing list?
13:30 < xnyhps> Go ahead :)


So what else do we know?

Post by Evan Schoenberg
_____________________________
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
Hi Evan, This is a follow up to the Dev Alert sent on February 25th.
It looks like your app “Adium” (164063256994618) is actively using the XMPP
Chat API. As we announced a year ago on April 30, 2014 the XMPP Chat API
will be deprecated starting on April 30, 2015. After that date, this app
will not be able to send or receive Facebook Messages via
chat.facebook.com , and the xmpp_login permission will be removed for all
new and existing users. To prevent broken experiences for people, we
recommend you remove Facebook Chat functionality from your app before April
30, 2015. For more information about this as well as the other API changes
which come into effect on April 30, 2015 please read the changelog You can
view this and other Developer Notifications related to your app, Adium, in
the App Dashboard . Thanks, The Facebook Team facebook DEVELOPERS
<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047> Hi
Evan,
This is a follow up to the Dev Alert sent on February 25th. It looks like
your app “Adium” (164063256994618) is actively using the XMPP Chat API.
As we announced a year ago on April 30, 2014 the XMPP Chat API will be
deprecated starting on April 30, 2015. After that date, this app will not
be able to send or receive Facebook Messages via chat.facebook.com, and
the xmpp_login permission will be removed for all new and existing users.
To prevent broken experiences for people, we recommend you remove Facebook
Chat functionality from your app before April 30, 2015.
For more information about this as well as the other API changes which
come into effect on April 30, 2015 please read the changelog
<https://developers.facebook.com/docs/apps/changelog>
You can view this and other Developer Notifications related to your
app, Adium, in the App Dashboard
<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047>
. Thanks,
You are receiving this email because you have chosen to receive developer
updates from Facebook. Want to control which developer updates you receive?
Go to: https://developers.facebook.com/settings/
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303

[Christopher Forsythe]

13:23 -!- Irssi: Join to #adium-devl was synced in 0 secs
13:24 < The_Tick> heyo
13:24 < xnyhps> Hi The_Tick
13:25 < The_Tick> hey how have you been?
13:25 < xnyhps> Really busy, hardly any time for Adium left. How are you?
13:26 < The_Tick> the same
13:26 < The_Tick> but life is good now
13:26 < The_Tick> the facebook xmpp thing
13:26 < The_Tick> is anyone working on whatever replaces it?
13:26 < xnyhps> Nope
13:27 < xnyhps> Well, maybe one of the Pidgin guys, but I doubt it.
13:28 -!- notjosh [~***@cable-89-216-22-24.static.sbb.rs] has quit [Quit:
<sleeping>]
13:28 < The_Tick> who is left to write code?
13:29 < xnyhps> wixardy and me
13:29 < The_Tick> and that's it?
13:29 < xnyhps> Yeah
13:29 < The_Tick> oh man
13:29 < The_Tick> has any work been done on this yet?
13:30 < xnyhps> Not by me, and I doubt wixardy has.
13:30 < The_Tick> mind if I paste this chat to the mailing list?
13:30 < xnyhps> Go ahead :)


So what else do we know?

Post by Evan Schoenberg
_____________________________
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
Hi Evan, This is a follow up to the Dev Alert sent on February 25th.
It looks like your app “Adium” (164063256994618) is actively using the XMPP
Chat API. As we announced a year ago on April 30, 2014 the XMPP Chat API
will be deprecated starting on April 30, 2015. After that date, this app
will not be able to send or receive Facebook Messages via
chat.facebook.com , and the xmpp_login permission will be removed for all
new and existing users. To prevent broken experiences for people, we
recommend you remove Facebook Chat functionality from your app before April
30, 2015. For more information about this as well as the other API changes
which come into effect on April 30, 2015 please read the changelog You can
view this and other Developer Notifications related to your app, Adium, in
the App Dashboard . Thanks, The Facebook Team facebook DEVELOPERS
<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047> Hi
Evan,
This is a follow up to the Dev Alert sent on February 25th. It looks like
your app “Adium” (164063256994618) is actively using the XMPP Chat API.
As we announced a year ago on April 30, 2014 the XMPP Chat API will be
deprecated starting on April 30, 2015. After that date, this app will not
be able to send or receive Facebook Messages via chat.facebook.com, and
the xmpp_login permission will be removed for all new and existing users.
To prevent broken experiences for people, we recommend you remove Facebook
Chat functionality from your app before April 30, 2015.
For more information about this as well as the other API changes which
come into effect on April 30, 2015 please read the changelog
<https://developers.facebook.com/docs/apps/changelog>
You can view this and other Developer Notifications related to your
app, Adium, in the App Dashboard
<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047>
. Thanks,
You are receiving this email because you have chosen to receive developer
updates from Facebook. Want to control which developer updates you receive?
Go to: https://developers.facebook.com/settings/
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303

[Colin Barrett]

There's nothing TO do afaik, other than remove it. There is no replacement API.

-Colin (via thumbs)

Post by Christopher Forsythe
13:23 -!- Irssi: Join to #adium-devl was synced in 0 secs
13:24 < The_Tick> heyo
13:24 < xnyhps> Hi The_Tick
13:25 < The_Tick> hey how have you been?
13:25 < xnyhps> Really busy, hardly any time for Adium left. How are you?
13:26 < The_Tick> the same
13:26 < The_Tick> but life is good now
13:26 < The_Tick> the facebook xmpp thing
13:26 < The_Tick> is anyone working on whatever replaces it?
13:26 < xnyhps> Nope
13:27 < xnyhps> Well, maybe one of the Pidgin guys, but I doubt it.
<sleeping>]
13:28 < The_Tick> who is left to write code?
13:29 < xnyhps> wixardy and me
13:29 < The_Tick> and that's it?
13:29 < xnyhps> Yeah
13:29 < The_Tick> oh man
13:29 < The_Tick> has any work been done on this yet?
13:30 < xnyhps> Not by me, and I doubt wixardy has.
13:30 < The_Tick> mind if I paste this chat to the mailing list?
13:30 < xnyhps> Go ahead :)
So what else do we know?

Post by Evan Schoenberg
_____________________________
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
facebook DEVELOPERS
Hi Evan,
This is a follow up to the Dev Alert sent on February 25th. It looks like your app gAdiumh (164063256994618) is actively using the XMPP Chat API.
As we announced a year ago on April 30, 2014 the XMPP Chat API will be deprecated starting on April 30, 2015. After that date, this app will not be able to send or receive Facebook Messages via chat.facebook.com, and the xmpp_login permission will be removed for all new and existing users.
To prevent broken experiences for people, we recommend you remove Facebook Chat functionality from your app before April 30, 2015.
For more information about this as well as the other API changes which come into effect on April 30, 2015 please read the changelog
You can view this and other Developer Notifications related to your app, Adium, in the App Dashboard.
Thanks,
The Facebook Team
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303

--
Chris Forsythe

[Evan Kinney]

Yep. Once the v1 API is deprecated, there is no developer access to chat anymore.

/ek

From: Colin Barrett
Reply-To: Adium Development List
Date: Thursday, April 16, 2015 at 12:42 PM
To: Adium Development List
Subject: Re: New Developer Alert for Adium

There's nothing TO do afaik, other than remove it. There is no replacement API.

-Colin (via thumbs)

On Apr 16, 2015, at 9:38 AM, Christopher Forsythe <***@growl.info<mailto:***@growl.info>> wrote:

13:23 -!- Irssi: Join to #adium-devl was synced in 0 secs
13:24 < The_Tick> heyo
13:24 < xnyhps> Hi The_Tick
13:25 < The_Tick> hey how have you been?
13:25 < xnyhps> Really busy, hardly any time for Adium left. How are you?
13:26 < The_Tick> the same
13:26 < The_Tick> but life is good now
13:26 < The_Tick> the facebook xmpp thing
13:26 < The_Tick> is anyone working on whatever replaces it?
13:26 < xnyhps> Nope
13:27 < xnyhps> Well, maybe one of the Pidgin guys, but I doubt it.
13:28 -!- notjosh [~***@cable-89-216-22-24.static.sbb.rs<mailto:***@cable-89-216-22-24.static.sbb.rs>] has quit [Quit:
<sleeping>]
13:28 < The_Tick> who is left to write code?
13:29 < xnyhps> wixardy and me
13:29 < The_Tick> and that's it?
13:29 < xnyhps> Yeah
13:29 < The_Tick> oh man
13:29 < The_Tick> has any work been done on this yet?
13:30 < xnyhps> Not by me, and I doubt wixardy has.
13:30 < The_Tick> mind if I paste this chat to the mailing list?
13:30 < xnyhps> Go ahead :)


So what else do we know?

On Wed, Apr 15, 2015 at 5:28 PM, Evan Schoenberg <***@gmail.com<mailto:***@gmail.com>> wrote:



_____________________________
From: Facebook <notification+***@facebookmail.com<mailto:notification%***@facebookmail.com>>
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
To: Evan Schoenberg <***@gmail.com<mailto:***@gmail.com>>


Hi Evan, This is a follow up to the Dev Alert sent on February 25th. It looks like your app “Adium” (164063256994618) is actively using the XMPP Chat API. As we announced a year ago on April 30, 2014 the XMPP Chat API will be deprecated starting on April 30, 2015. After that date, this app will not be able to send or receive Facebook Messages via chat.facebook.com<http://chat.facebook.com> , and the xmpp_login permission will be removed for all new and existing users. To prevent broken experiences for people, we recommend you remove Facebook Chat functionality from your app before April 30, 2015. For more information about this as well as the other API changes which come into effect on April 30, 2015 please read the changelog You can view this and other Developer Notifications related to your app, Adium, in the App Dashboard . Thanks, The Facebook Team
facebook DEVELOPERS<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047>
Hi Evan,

This is a follow up to the Dev Alert sent on February 25th. It looks like your app “Adium” (164063256994618) is actively using the XMPP Chat API.

As we announced a year ago on April 30, 2014 the XMPP Chat API will be deprecated starting on April 30, 2015. After that date, this app will not be able to send or receive Facebook Messages via chat.facebook.com<http://chat.facebook.com>, and the xmpp_login permission will be removed for all new and existing users.

To prevent broken experiences for people, we recommend you remove Facebook Chat functionality from your app before April 30, 2015.

For more information about this as well as the other API changes which come into effect on April 30, 2015 please read the changelog<https://developers.facebook.com/docs/apps/changelog>


You can view this and other Developer Notifications related to your app, Adium, in the App Dashboard<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047>.
Thanks,
The Facebook Team





This message was sent to ***@gmail.com<mailto:***@gmail.com>. You are receiving this email because you have chosen to receive developer updates from Facebook. Want to control which developer updates you receive? Go to: https://developers.facebook.com/settings/
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303
[https://www.facebook.com/email_open_log_pic.php?mid=b98bcb7G47bba8G513c8921aa546G191Gc732&pid=164063256994618]

[Thijs Alkemade]

Content preview: I thought they were switching to a MQTT based API, but apparently
that’s just for internal use by their own chat app. It’s still possible
to reverse engineer that, but meh… Thijs [...]

Content analysis details: (-2.2 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust
[74.125.82.42 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(thijsalkemade[at]gmail.com)
-0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3)
[74.125.82.42 listed in wl.mailspike.net]
0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
domains are different
-0.0 SPF_PASS SPF: sender matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.0 RCVD_IN_MSPIKE_WL Mailspike good senders
0.2 FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and EnvelopeFrom
freemail headers are different
0.2 AWL AWL: Adjusted score from AWL reputation of From: address
X-Spam-Flag: NO
X-BeenThere: ***@adium.im
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Adium Development List <devel.adium.im>
List-Unsubscribe: <http://adium.im/mailman/options/devel_adium.im>,
<mailto:devel-***@adium.im?subject=unsubscribe>
List-Archive: <http://adium.im/pipermail/devel_adium.im/>
List-Post: <mailto:***@adium.im>
List-Help: <mailto:devel-***@adium.im?subject=help>
List-Subscribe: <http://adium.im/mailman/listinfo/devel_adium.im>,
<mailto:devel-***@adium.im?subject=subscribe>
Reply-To: Adium Development List <***@adium.im>
Errors-To: devel-***@adium.im
Sender: "devel" <devel-***@adium.im>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - duck.adiumx.com
X-AntiAbuse: Original Domain - ml-in.narkive.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - adium.im
X-Get-Message-Sender-Via: duck.adiumx.com: acl_c_authenticated_local_user: mailman/mailman
X-Source:
X-Source-Args:
X-Source-Dir:

I thought they were switching to a MQTT based API, but apparently that’s just for internal use by their own chat app.

It’s still possible to reverse engineer that, but meh…

Thijs

Post by Evan Kinney
Yep. Once the v1 API is deprecated, there is no developer access to chat anymore.
/ek
From: Colin Barrett
Reply-To: Adium Development List
Date: Thursday, April 16, 2015 at 12:42 PM
To: Adium Development List
Subject: Re: New Developer Alert for Adium

Post by Colin Barrett
There's nothing TO do afaik, other than remove it. There is no replacement API.
-Colin (via thumbs)

Post by Christopher Forsythe
13:23 -!- Irssi: Join to #adium-devl was synced in 0 secs
13:24 < The_Tick> heyo
13:24 < xnyhps> Hi The_Tick
13:25 < The_Tick> hey how have you been?
13:25 < xnyhps> Really busy, hardly any time for Adium left. How are you?
13:26 < The_Tick> the same
13:26 < The_Tick> but life is good now
13:26 < The_Tick> the facebook xmpp thing
13:26 < The_Tick> is anyone working on whatever replaces it?
13:26 < xnyhps> Nope
13:27 < xnyhps> Well, maybe one of the Pidgin guys, but I doubt it.
<sleeping>]
13:28 < The_Tick> who is left to write code?
13:29 < xnyhps> wixardy and me
13:29 < The_Tick> and that's it?
13:29 < xnyhps> Yeah
13:29 < The_Tick> oh man
13:29 < The_Tick> has any work been done on this yet?
13:30 < xnyhps> Not by me, and I doubt wixardy has.
13:30 < The_Tick> mind if I paste this chat to the mailing list?
13:30 < xnyhps> Go ahead :)
So what else do we know?

Post by Evan Schoenberg
_____________________________
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
facebook DEVELOPERS
Hi Evan,
This is a follow up to the Dev Alert sent on February 25th. It looks like your app “Adium” (164063256994618) is actively using the XMPP Chat API.
As we announced a year ago on April 30, 2014 the XMPP Chat API will be deprecated starting on April 30, 2015. After that date, this app will not be able to send or receive Facebook Messages via chat.facebook.com, and the xmpp_login permission will be removed for all new and existing users.
To prevent broken experiences for people, we recommend you remove Facebook Chat functionality from your app before April 30, 2015.
For more information about this as well as the other API changes which come into effect on April 30, 2015 please read the changelog
You can view this and other Developer Notifications related to your app, Adium, in the App Dashboard.
Thanks,
The Facebook Team
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303

--
Chris Forsythe

[Augie Fackler]

I thought they were switching to a MQTT based API, but apparently that’s just for internal use by their own chat app.
It’s still possible to reverse engineer that, but meh…

I think the only thing you could do to support it would be to reverse engineer the likely-unstable json API the webapp uses.

It’s been a dark couple of years for open chat protocols. Sigh.

Thijs

Post by Evan Kinney
Yep. Once the v1 API is deprecated, there is no developer access to chat anymore.
/ek
From: Colin Barrett
Reply-To: Adium Development List
Date: Thursday, April 16, 2015 at 12:42 PM
To: Adium Development List
Subject: Re: New Developer Alert for Adium

Post by Colin Barrett
There's nothing TO do afaik, other than remove it. There is no replacement API.
-Colin (via thumbs)

Post by Christopher Forsythe
13:23 -!- Irssi: Join to #adium-devl was synced in 0 secs
13:24 < The_Tick> heyo
13:24 < xnyhps> Hi The_Tick
13:25 < The_Tick> hey how have you been?
13:25 < xnyhps> Really busy, hardly any time for Adium left. How are you?
13:26 < The_Tick> the same
13:26 < The_Tick> but life is good now
13:26 < The_Tick> the facebook xmpp thing
13:26 < The_Tick> is anyone working on whatever replaces it?
13:26 < xnyhps> Nope
13:27 < xnyhps> Well, maybe one of the Pidgin guys, but I doubt it.
<sleeping>]
13:28 < The_Tick> who is left to write code?
13:29 < xnyhps> wixardy and me
13:29 < The_Tick> and that's it?
13:29 < xnyhps> Yeah
13:29 < The_Tick> oh man
13:29 < The_Tick> has any work been done on this yet?
13:30 < xnyhps> Not by me, and I doubt wixardy has.
13:30 < The_Tick> mind if I paste this chat to the mailing list?
13:30 < xnyhps> Go ahead :)
So what else do we know?

Post by Evan Schoenberg
_____________________________
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
facebook DEVELOPERS
Hi Evan,
This is a follow up to the Dev Alert sent on February 25th. It looks like your app “Adium” (164063256994618) is actively using the XMPP Chat API.
As we announced a year ago on April 30, 2014 the XMPP Chat API will be deprecated starting on April 30, 2015. After that date, this app will not be able to send or receive Facebook Messages via chat.facebook.com, and the xmpp_login permission will be removed for all new and existing users.
To prevent broken experiences for people, we recommend you remove Facebook Chat functionality from your app before April 30, 2015.
For more information about this as well as the other API changes which come into effect on April 30, 2015 please read the changelog
You can view this and other Developer Notifications related to your app, Adium, in the App Dashboard.
Thanks,
The Facebook Team
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303

--
Chris Forsythe

[Christopher Forsythe]

The problem is that there are things to do:

1) Provide notice to existing users. - Blog post/twitter?

2) Update the app to disable connecting, keep logs for posterity.

3) Notify people who do have the account enabled on update. Maybe an
nswindow? Maybe something else?

4) Other things?

At the end of the month they turn this off, then the 2500-3000 people
actively using it per sparkle are going to start filing tickets and hitting
up the support channels, things like that. It'd be nice to get ahead of
that is all.

Does this sound reasonable or am I out on a limb here?

Post by Colin Barrett
There's nothing TO do afaik, other than remove it. There is no replacement API.
-Colin (via thumbs)
13:23 -!- Irssi: Join to #adium-devl was synced in 0 secs
13:24 < The_Tick> heyo
13:24 < xnyhps> Hi The_Tick
13:25 < The_Tick> hey how have you been?
13:25 < xnyhps> Really busy, hardly any time for Adium left. How are you?
13:26 < The_Tick> the same
13:26 < The_Tick> but life is good now
13:26 < The_Tick> the facebook xmpp thing
13:26 < The_Tick> is anyone working on whatever replaces it?
13:26 < xnyhps> Nope
13:27 < xnyhps> Well, maybe one of the Pidgin guys, but I doubt it.
<sleeping>]
13:28 < The_Tick> who is left to write code?
13:29 < xnyhps> wixardy and me
13:29 < The_Tick> and that's it?
13:29 < xnyhps> Yeah
13:29 < The_Tick> oh man
13:29 < The_Tick> has any work been done on this yet?
13:30 < xnyhps> Not by me, and I doubt wixardy has.
13:30 < The_Tick> mind if I paste this chat to the mailing list?
13:30 < xnyhps> Go ahead :)
So what else do we know?
On Wed, Apr 15, 2015 at 5:28 PM, Evan Schoenberg <

Post by Evan Schoenberg
_____________________________
Sent: Wednesday, April 15, 2015 3:44 PM
Subject: New Developer Alert for Adium
Hi Evan, This is a follow up to the Dev Alert sent on February 25th.
It looks like your app “Adium” (164063256994618) is actively using the XMPP
Chat API. As we announced a year ago on April 30, 2014 the XMPP Chat API
will be deprecated starting on April 30, 2015. After that date, this app
will not be able to send or receive Facebook Messages via
chat.facebook.com , and the xmpp_login permission will be removed for
all new and existing users. To prevent broken experiences for people, we
recommend you remove Facebook Chat functionality from your app before April
30, 2015. For more information about this as well as the other API changes
which come into effect on April 30, 2015 please read the changelog You can
view this and other Developer Notifications related to your app, Adium, in
the App Dashboard . Thanks, The Facebook Team facebook DEVELOPERS
<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047> Hi
Evan,
This is a follow up to the Dev Alert sent on February 25th. It looks like
your app “Adium” (164063256994618) is actively using the XMPP Chat API.
As we announced a year ago on April 30, 2014 the XMPP Chat API will be
deprecated starting on April 30, 2015. After that date, this app will not
be able to send or receive Facebook Messages via chat.facebook.com, and
the xmpp_login permission will be removed for all new and existing users.
To prevent broken experiences for people, we recommend you remove
Facebook Chat functionality from your app before April 30, 2015.
For more information about this as well as the other API changes which
come into effect on April 30, 2015 please read the changelog
<https://developers.facebook.com/docs/apps/changelog>
You can view this and other Developer Notifications related to your
app, Adium, in the App Dashboard
<https://developers.facebook.com/apps/164063256994618?ref=email&alert_id=1436476546653047>
. Thanks,
You are receiving this email because you have chosen to receive developer
updates from Facebook. Want to control which developer updates you receive?
Go to: https://developers.facebook.com/settings/
Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA 94303

--
Chris Forsythe

[Robert Vehse]

Post by Christopher Forsythe
1) Provide notice to existing users. - Blog post/twitter?

I can do that.

Post by Christopher Forsythe
[…] At the end of the month they turn this off, then the 2500-3000 people actively using it per sparkle are going to start filing tickets and hitting up the support channels, things like that. It'd be nice to get ahead of that is all.

Right.

Post by Christopher Forsythe
Does this sound reasonable or am I out on a limb here?

Nah, sounds fine.