Twitter Development Talk to become read-only this Friday, August 12th

[Jason Costa]

Hi everyone,

With our move over to the new dev.twitter.com, we've shifted our
attention toward answering questions in the developer discussions
taking place at:

https://dev.twitter.com/discussions

If you have questions, please post them there and we'll continue to do
our best to answer them, and we hope the community will continue to
jump in and help there too.

In the meantime, we'll be closing the ability to post new threads in
the Google Groups starting this Friday, August 12th. We'll leave the
Groups open as read-only, so the archive of threads will remain
available.

Developing for Twitter is never a one-off event, and it's really
important that we continue to maintain a few channels for
disseminating critical announcements. If you're not already, please
start following along at:

1) Follow @twitterapi
- https://twitter.com/intent/user?screen_name=twitterapi
2) Subscribe to email notifications for blog posts for announcements
- https://dev.twitter.com/blog/category/announcements (click
"Subscribe to category")
3) Subscribe to the RSS feed of the blog
- https://dev.twitter.com/blog/feed


Thanks,

--Jason

[Dossy Shiobara]

How do I subscribe to the discussion forum via email?

On 8/10/11 3:27 PM, Jason Costa wrote:
> With our move over to the new dev.twitter.com, we've shifted our
> attention toward answering questions in the developer discussions
> taking place at:
>
> https://dev.twitter.com/discussions

--
Dossy Shiobara | "He realized the fastest way to change
do...@panoptic.com | is to laugh at your own folly -- then you
http://panoptic.com/ | can let go and quickly move on." (p. 70)
* WordPress * jQuery * MySQL * Security * Business Continuity *

[Dean Collins]

And better still why aren't they just "forumising" the existing mailing
list....whats the point of having two locations for dev discussions.

Jason sorry mate but I'm calling you out on this and suggesting you
remove the forum and keep the information in a single location source.

Cheers,
Dean

--
Have you visited the Developer Discussions feature on
https://dev.twitter.com/discussions yet?

Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi

Unsubscribe or change your group membership settings:
http://groups.google.com/group/twitter-development-talk/subscribe

[Taylor Singletary]

Hi Dossy & Dean,

Email subscription options are configurable either from specific forum category pages or more universally at https://dev.twitter.com/user -- unfortunately you can't reply directly to emails yet, but it's a feature we're hoping to provide in the future.

We are moving to a single dev discussion location: https://dev.twitter.com/discussions 

Announcements will be made on the developer blog: https://dev.twitter.com/blog/category/announcements and @twitterapi. As we've done with announcements for some time, we'll tend to directly link an announcement with a discussion thread -- now on dev.twitter.com/discussions instead of these older google groups.

@episod - Taylor Singletary

[Dean Collins]

Taylor when will twitter-deve...@googlegroups.com be switched off and archived so no future messages can be posted to it?

 

 

 

 

Cheers,

Dean

 

 

---

From: twitter-deve...@googlegroups.com [mailto:twitter-deve...@googlegroups.com] On Behalf Of Taylor Singletary
Sent: Wednesday, August 10, 2011 4:23 PM
To: twitter-deve...@googlegroups.com
Cc: Jason Costa
Subject: Re: [twitter-dev] Twitter Development Talk to become read-only this Friday, August 12th

 

Hi Dossy & Dean,

[Jason Costa]

Hi Dean,

We will turn off the ability to create new posts for the Google Group
this Friday, August 12th. From then on, all new posts should be
created over at: https://dev.twitter.com/discussions

Thanks,

--Jason

On Aug 10, 2:29 pm, "Dean Collins" <D...@cognation.net> wrote:
> Taylor when will twitter-deve...@googlegroups.com be switched
> off and archived so no future messages can be posted to it?
>
> Cheers,
>
> Dean
>
> ________________________________
>
> From: twitter-deve...@googlegroups.com
> [mailto:twitter-deve...@googlegroups.com] On Behalf Of Taylor
> Singletary
> Sent: Wednesday, August 10, 2011 4:23 PM
> To: twitter-deve...@googlegroups.com
> Cc: Jason Costa
> Subject: Re: [twitter-dev] Twitter Development Talk to become read-only
> this Friday, August 12th
>
> Hi Dossy & Dean,
>
> Email subscription options are configurable either from specific forum
> category pages or more universally athttps://dev.twitter.com/user--
> unfortunately you can't reply directly to emails yet, but it's a feature
> we're hoping to provide in the future.
>
> We are moving to a single dev discussion location:https://dev.twitter.com/discussions
>

> Announcements will be made on the developer blog:https://dev.twitter.com/blog/category/announcementsand @twitterapi. As

> we've done with announcements for some time, we'll tend to directly link
> an announcement with a discussion thread -- now on
> dev.twitter.com/discussions instead of these older google groups.
>

> @episod <http://twitter.com/intent/user?screen_name=episod>  - Taylor

> Singletary
>
> On Wed, Aug 10, 2011 at 1:05 PM, Dossy Shiobara <do...@panoptic.com>
> wrote:
>
> How do I subscribe to the discussion forum via email?
>
> On 8/10/11 3:27 PM, Jason Costa wrote:
>
> With our move over to the new dev.twitter.com, we've shifted our
> attention toward answering questions in the developer discussions
> taking place at:
>
> https://dev.twitter.com/discussions
>
> --
> Dossy Shiobara         |      "He realized the fastest way to change

> do...@panoptic.com     |   is to laugh at your own folly -- then youhttp://panoptic.com/  |   can let go and quickly move on." (p. 70)

[Dossy Shiobara]

Thanks. Looking forward to being able to reply via email.

On 8/10/11 4:23 PM, Taylor Singletary wrote:
> Email subscription options are configurable either from specific forum
> category pages or more universally at https://dev.twitter.com/user --
> unfortunately you can't reply directly to emails yet, but it's a
> feature we're hoping to provide in the future.

--