hueniverse covers a wide range of topics, usually with enough detail to help developers dive right in and start using the technologies described. But there are often times when the target is moving too fast or there are too many targets to cover. When that happens, there isn’t always a place to post a comment and ask a question.
If you have a question about any of the technologies or projects covered, and you can’t find a place to ask it, please consider this an open invitation to engage. In order to make this useful to others, please ask one question at a time and only use this space for questions (not comments or answers to other people).
Hi. We have built a twitter app. We’ve figured out how to use OAUth to authenticate a user and allow the app to access his or her account. The app is a simple update status application. The app updates the status of the twitter user from our website. But we can’t figure out how to update the status of ALL the users who have added the app at once? We need to be able to do this from the website form located at http://gnosisarts.com/home/confirm.php (This is just a test page to figure out how to get the damned thing working; it’s not the final home of the app)
Thanks,
Eric Bryant, Director
Gnosis Arts
You should ask this question on the Twitter API support group. I don’t know if Twitter offers special APIs for client management. Fire Eagle, a location service, offers such APIs.
http://www.oasis-open.org/committees/download.php/35678/xrd-1.0-wd11.html#xrd.sequence
The XRDS element schema says minOccurs=”0″ and maxOccurs=”unbounded”. As per the NOTE in the spec, there has to be minimum 2 elements. I think corresponding xml schema should be updated to have minOccurs=”2″ instead of “0″. Thus, applications can depend on XML Schema validator to ensure this is true instead of writing custom logic for correctness of XRD documents.
I think xml schema should show as below. I hope the correction will be done before the final XRD spec.
====
The specification does not mandate a cardinality of 2, only recommends it. That note is there to help people understand what the XRDS element is for, unlike previous versions. Since this is only a recommendation, the schema must allow 0 to many.
Hi,
I am new to Social Networking and oAuth. I like to create a sample application which work on all Social Network Sites ? Where should i start ? I want to do mainly three things
1. Get/Set status updates
2. Send messages
3. Make friends
I searched many. I found each Social Network uses different oAuth methods. Why its like that ? Since oAuth is a global standard.
I am expecting that if i implemented for one Social Network rest all must work with only difference in the request URLs and Consumer details. The rest mechanism must same. Where am i wrong ?
Please some one guide me. Is there any sample code that works for all the Social Networks. I have developed for Social Network twitter and linkedIn. This work with almost same code. But still have some difference.
Regards
Akeeq
Can you give examples of the social networks you are trying to use? How are they different? For the most part, most OAuth implementation are very similar. The libraries posted on the OAuth site are a good place to start. Also, OAuth does not say how the API itself works so sending updated and making friends will most likely be different on each site. OAuth has nothing to do with that part, only the security part.