You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(This issue was not originally suggested by me, I am just copying it from the wiki)
Where supported, suggesting that an Endpoint accept name, category, and description optionally. This would take the form of a form encoded submission only. I do not want to suggest complicated properties being sent to photos.
The practical reason is that naming photos allows them to be retrieved.
Tagging would allow a query for images that matched a tag for a possible suggested image library search if someone wanted to implement that into a client.
The text was updated successfully, but these errors were encountered:
This sounds like something to turn the media endpoint into a full media library. The idea could be spun out to a semi-public library exposed on the website - for example, like photo albums in VKontakte (basically THE Russian social network) - not all of the photos posted to albums end up on the user's "wall" (feed) as posts.
(This issue was not originally suggested by me, I am just copying it from the wiki)
Where supported, suggesting that an Endpoint accept name, category, and description optionally. This would take the form of a form encoded submission only. I do not want to suggest complicated properties being sent to photos.
The practical reason is that naming photos allows them to be retrieved.
Tagging would allow a query for images that matched a tag for a possible suggested image library search if someone wanted to implement that into a client.
The text was updated successfully, but these errors were encountered: