API Changes for May 11, 2009

[Doug Williams]

Hi All,

Blocking now gets more fun:

• Feature (REST): Added methods to retrieve blocking information
  

See also: Google Code Issue 9: http://code.google.com/p/twitter-api/issues/detail?id=9
See also: blocks/exists => http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-blocks-exists
See also: blocks/blocking => http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-blocks-blocking
See also: blocks/blocking/ids =>http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-blocks-blocking-ids

We are going to be moving some things around:

• Deprecation Announced (REST): <following> and <notification> elements will be moved to their own method in the near future.

See announcement: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/42ba883b9f8e3c6e?tvc=2

Thanks,
Doug
--

Doug Williams
Twitter Platform Support
http://twitter.com/dougw

[Carlos]

Any particular reason the blocks/exist function returns the
information for the user requested if the block exist and a hash error
response if not? I would think following the same kind of format as
the friendship exist function would make more sense; something like:
<blocking>true/false<blocking>

An error response should only be returned if the user name doesn't
exist. Just my 2 cents.

On May 11, 8:58 pm, Doug Williams <d...@twitter.com> wrote:
> Hi All,
>
> Blocking now gets more fun:
>

>    - Feature (REST): Added methods to retrieve blocking information

>
> See also: Google Code Issue 9:http://code.google.com/p/twitter-api/issues/detail?id=9
> See also: blocks/exists =>http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-blocks-exists
> See also: blocks/blocking =>http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-blocks-blocking

> See also: blocks/blocking/ids =>http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-blocks-blocking...

>
> We are going to be moving some things around:
>

>    - Deprecation Announced (REST): <following> and <notification> elements

>    will be moved to their own method in the near future.
>

> See announcement:http://groups.google.com/group/twitter-development-talk/browse_thread...

[rlamfink]

Using the blocks/blocking API, the page parameter has no effect. I
always get the first page, no matter what page number is in the URL
parameter. Also I don't get just 20 users in the list as the
documentation says. I get more.

[Doug Williams]

Can you open an issue for this so we can track it? I'll take a look today.

Thanks,

Doug