search

appdotnet / api-spec

App.net API Documentation is on the web at https://developers.app.net. Source for these docs is in the new-docs branch here. Please use the issue tracker and submit pull requests! Help us build the real-time social service where users and developers come first, not advertisers.
https://developers.app.net
950 stars 98 forks source link

Allow more non-authorized endpoints #278

Open duerig opened 11 years ago

duerig commented 11 years ago

The following endpoints should be available without an authorization token:

Retrieve multiple Users GET /stream/0/users Any Search for Users GET /stream/0/users/search Any

Retrieve multiple Posts GET /stream/0/posts Any Retrieve replies to a Post GET /stream/0/posts/[post_id]/replies Any

These would be useful for clients which want to support a 'viewer' mode in addition to a 'logged in' mode. None of these reveal any private information which cannot be found by other means. For instance, Vidcast needs the /replies endpoint to show the conversation to viewers.

kosso commented 11 years ago

One way I use to get data for a 'public view' is create a read only token for a spare account and use that as the access token until someone logs in to use theirs.

On 24 January 2013 19:09, duerig notifications@github.com wrote:

The following endpoints should be available without an authorization token:

Retrieve multiple Users GET /stream/0/users Any Search for Users GET /stream/0/users/search Any

Retrieve multiple Posts GET /stream/0/posts Any Retrieve replies to a Post GET /stream/0/posts/[post_id]/replies Any

These would be useful for clients which want to support a 'viewer' mode in addition to a 'logged in' mode. None of these reveal any private information which cannot be found by other means. For instance, Vidcast needs the /replies endpoint to show the conversation to viewers.

— Reply to this email directly or view it on GitHubhttps://github.com/appdotnet/api-spec/issues/278.

duerig commented 11 years ago

I thought that the way they implemented tokens this didn't work well. If you are authenticated, your rate limits are per-token and if you are not authenticated it is per-IP. So if many people are reading with the same user token, they will see the rate limits even if none of them is individually polling that frequently. I may have misunderstood the docs.

kosso commented 11 years ago

good point about the rate limits. I hadn't thought about that. ;)

On 24 January 2013 19:21, duerig notifications@github.com wrote:

I thought that the way they implemented tokens this didn't work well. If you are authenticated, your rate limits are per-token and if you are not authenticated it is per-IP. So if many people are reading with the same user token, they will see the rate limits even if none of them is individually polling that frequently. I may have misunderstood the docs.

— Reply to this email directly or view it on GitHubhttps://github.com/appdotnet/api-spec/issues/278#issuecomment-12668252.