Thoughts on having Rejaw implemented? Apparently it's got a similar full API to Twitter (or did I read that incorrectly somewhere) so it shouldn't be too bad to pull in and post updates.
We want to hear what kind of features that you want to see in the API.
Go ahead and reply to this and tell us what feature you think our API couldn't do without. Anything that you see from another user that makes sense, or you just plain like...go ahead and vote that up.
I'm unable to add last.fm. It keeps giving an error: "There was an error adding your account." Any ideas? This has been going on since I signed up days ago.
I like how socialthing aggregates everything into one place, and i like the idea of posting a facebook status from here, or a twitter status from here, but i'd like the option to be able to post multiple media types to pownce without going to their site.
I think a good way to get into this would be to bring up a box with 30px x 30px icons, or maybe smaller, when you click "post", you can then select the services you wish to post to (or just select an option that says 'all') and the posting box adjusts accordingly. Therefore if you JUST click pownce you get options to post a link, file or event, but if you click multiple, you just get a normal post box. This option of being able to select the services you want to post to BEFORE you reach the text input reduces the number of clicks needed to change the services you're posting to later on. Of course maybe it would be wise to be able to select the old method in the settings pane.
What would be interesting to think about implementing, if I were doing this, is a way to notify users when a third-party site causes a socialthing! service interruption. Especially if st is aware of an external issue, as with the Flickr API (mentioned in the reply to the problem I reported yesterday).
This would have been useful to me yesterday @Twhirl when it suddenly dropped avatars b/c the Twitter API changed twice in a few hours. Other users complained about Twhirl, not realizing it wasn't the product's fault. It'd be unfortunate for people to leave st b/c of something that isn't your site. Generally, some users also complain about "features" of third party Twitter clients that are actually attributed to the API (like that max # of tweet requests you can make in an hour).
A possible downside to this may be notifying users that something is temporarily effed if they aren't already noticing it, although it might be worth it to users who are noticing errors to know it's not st.
You've probably thought about this already, it's probably a buttload of feedback mediation work but you guys do such a stellar job already, I can't help but think the idea may be useful and possible.
It would be nice if socialthing! had an API, so we could integrate our data elsewhere as well :) (Our friend stream and, hopefully also, our OWN stream)...