IOS is forced to implement the Douban API of social media.

ContentsMark: UseUser Authentication and text sharing.

 

Douban is the source of the pain point of the synchronization sdk I wrote this time. Do not follow the standard oauth. Sometimes I really want to throw the guy who writes API interfaces.

 

Seven major weaknesses of Douban API:

 

1. The Authentication Mode only supports the header mode. You must separate the authentication string and place it in the authorization field of the HTTP header. Otherwise, no auth access is returned.

 

2. The Pin is not required. After the user authenticates in the second step, the pin is not returned, and the access token obtained in the third step is not required.

 

3. Poor stability. If the authentication fails, it may not be your problem.

 

4. Post is not in the normal query string format. This bird uses an entry format. You need to input XML similar to this:

@ "<? XML version = \ '1. 0 \ 'Encoding = \ 'utf-8 \'?> \

<Entry xmlns: ns0 = \ "http://www.w3.org/2005/atom\" xmlns: DB = \ "http://www.douban.com/xmlns/\"> \

<Content> .. </Content> \

</Entry>"

 

5. There is no API for uploading images.

 

6. The document is poorly written, confusing, and rough. It is worse than everyone's documents.

 

7. There is no official ios sdk (no third-party links ). .