"Block" API endpoints?

[katanacrimson]

As on tin. Blocking seems to be available on web, but nothing related to it available in the API. Will blocked users (on the site) be blocked as well in API responses? Will applications be responsible for managing block lists themselves?

[caseym]

Added block / unblock API endpoints. Any blocking done via API or Web share the same data set, therefore any blocking of a user done via the API will result in a block via the website. Additionally any blocking done via one application will result in blocks across all applications.

[caseym]

See:

https://developer.heello.com/docs/1/POST/users/block
https://developer.heello.com/docs/1/DELETE/users/block

[katanacrimson]

Will provide support ASAP within node-heello. Thanks for the addition.

Will this modify returned data when looking up a user profile so that an application can determine (if looking up a user) that they are blocked? I see no attached metadata on GET/users/show currently.

[caseym]

We are evaluating ways to provide this information via the API. Will post
updates when it is available.

On Wednesday, June 12, 2013, Damian Bushong wrote:

Will provide support ASAP within node-heello. Thanks for the support.

Will this modify returned data when looking up a user profile so that an
application can determine (if looking up a user) that they are blocked? I
see no attached metadata on GET/users/show currently.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-19363633
.

[katanacrimson]

Apparently there's more endpoints:

https://developer.heello.com/docs/1/GET/users/blocking

[caseym]

Still fleshing them out before I note it in the issue related to block
endpoints.

On Monday, June 17, 2013, Damian Bushong wrote:

Apparently there's more endpoints:

https://developer.heello.com/docs/1/GET/users/blocking

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-19563048
.

[katanacrimson]

Alright then, I'd just noticed it popped up in the list of endpoints

[caseym]

There is a new API endpoint to allow an authenticated user access to the list of users they are blocking.

See:
https://developer.heello.com/docs/1/GET/users/blocking

You will only be able to see the users whom you block. You will not be able to see users who block you.

[katanacrimson]

Will there be a property in a user's entry as well to indicate if they're currently being blocked?

Also - a minor question involving pedantry (I'm sorry). Due to twitter's...evolution of "blocking" (bastards changed how it worked), it's hard to know what this will affect. Will this just ignore the other user's content in any API requests, or will it also actively block the other (blocked) user from seeing our own content?

[caseym]

There will be no way for a user to now who has blocked them. You will not be able to know if any other user is blocking you. It's just a one way flow of information, you can see who you block, but not who blocks you.

In terms of what happens when you block someone. We will filter any activity from the blocked user from your timeline and notifications in both the API and Web data.

[liclac]

Will attempts to follow an user who is blocking you simply give an HTTP 403
then?

[caseym]

No, you can follow a user who blocks you. Blocking a user does not block a user from seeing your Pings or activity that is public, it just blocks you from seeing their activity in your Timeline and Notifications.

On Wednesday, June 19, 2013 at 10:37 AM, uppfinnarn wrote:

Will attempts to follow an user who is blocking you simply give an HTTP 403
then?

2013/6/19 Casey Mees <notifications@github.com (mailto:notifications@github.com)>

There will be no way for a user to now who has blocked them. You will not
be able to know if any other user is blocking you. It's just a one way flow
of information, you can see who you block, but not who blocks you.

In terms of what happens when you block someone. We will filter any
activity from the blocked user from your timeline and notifications in both
the API and Web data.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-19690820
.

Johannes Ekberg

—
Reply to this email directly or view it on GitHub (#22 (comment)).

[katanacrimson]

Alright, so it's just shutting them out from being visible. Good to know then.

I'll have to see within my own implementations about how to pull off timed/temporary blocking. Will have to be client-side I guess.

[liclac]

What about protected accounts? On Twitter, blocking (and then optionally unblocking) is the only way to revoke follow permissions, will you have some other way to do this?