|Anonymous | Login | Signup for a new account||2013-05-21 18:17 PDT|
|Main | My View | View Issues | Change Log | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000452||Friendica||API (statusnet/twitter)||public||2012-06-13 12:54||2012-06-13 15:56|
|Fixed in Version|
|Summary||0000452: api/statuses/user_timeline returns wrong user records|
|Description||When issuing a request to the api method "api/statuses/user_timeline" with a user_id specified, all returned posts have the user specified by user_id as their user object returned, even when they were posted by another user.|
|Steps To Reproduce||Issue a GET request to /api/statuses/user_timeline?user_id=XX, where XX should be the user_id of a group so it gets more obvious|
Example: http://frnd.tk/api/statuses/user_timeline?user_id=7 [^]
Result: All statuses have Friendica Support as their author returned, but Friendica Support is only the user who owns the wall, but not the author of the post.
Expectation: The real authors should be returned in user, not the owner of the wall.
|Additional Information||If the posts are queried seperately via /api/statuses/show/:id, the correct author is returned.|
|Tags||No tags attached.|
|Attached Files|| eb032aef5403a364d90749000acaed5a-1.jpg_f=&_u=120613075454 [^] (160,775 bytes) 2012-06-13 12:54|
eb032aef5403a364d90749000acaed5a-0.jpg [^] (281,033 bytes) 2012-06-13 12:55
...I wanted to attach this image, it's a screenshot of my Friendica For Android app I'm developing, where I encountered the bug:
...but the bug tracker only offers the uploaded file to download, not to view
This is where the differences between network models starts to cause issues with the API.
In this case user_id=7 may live on another system. The site from which you are making the query does not know who the friends are of user_id=7 and what their ids are, and even if it did, they could have duplicate ids from users on this system.
Then the real killer is that user_id=7 could be an Email contact or RSS feed or Facebook member. We may not have any way to query who their friends are, or even be assured that their friends have anything resembling "ids".
In our standard feeds we provide the author name, url, and photo. I'm not certain how this has been mapped to the API. The author URL is the closest thing we have to an ID, but one must usually take into account subtle differences such as http/https and the presence or lack of 'www.'
I don't have a good resolution, just enumerating the issues for anybody who wishes to take this on. Perhaps we should extend the concept of "user_id" to accept a URL; though this could cause confusion and create bugs for normal Twitter client apps.
Viewing streams of others should probably be done by opening a web browser and visiting the URL, since API applications aren't likely to be able to negotiate authentication protocols for all the networks that Friendica may be able to internally. In the case of email, this will probably fail completely; though I believe the profile URL in this case goes to the top of their email domain and could be duplicated.
|2012-06-13 12:54||max.weller||New Issue|
|2012-06-13 12:54||max.weller||File Added: eb032aef5403a364d90749000acaed5a-1.jpg_f=&_u=120613075454|
|2012-06-13 12:55||max.weller||File Added: eb032aef5403a364d90749000acaed5a-0.jpg|
|2012-06-13 12:57||max.weller||Note Added: 0000688|
|2012-06-13 15:56||macgirvin||Note Added: 0000689|
|Copyright © 2000 - 2010 MantisBT Group|