There were some differences between the queries that lit the envelope and those that returned data on the /users/recent page - these have been refactored to use the same code.
Also, we're moving more and more activity into the Stack Exchange Inbox. As we make this transition, the envelope will ...
@TimStone Astraplopia is a serious medical condition, and can only be diagnosed by a medical professional. See your doctor if you find that you're perceiving more than three stars at a time.
For the XMPP interface for the Stack Overflow chat, I am currently taking the HTML of the chat messages and converting to valid XML, and setting that as the html child element of the XMPP message object. In my Mac OS X jabber client this was working great! It meant that when users in the SO chat ...
<img width="32" height="32" src="http://www.gravatar.com/avatar/963a544e10032580fffac1f5379d5e65?s=32&d=identicon&r=PG" alt="Josh's Socks" title="Josh's Socks"> why can't you scrape it from there?
@TheUnhandledException It does not. It only gives you the basic user information as it relates to the the room. It's used to pull gravatars and such of people who aren't currently here, I think.
Hahah, I tried not specifying anything for ids= and it tells me "try commas"
@MarcGravell Haha. But you guys did an awesome job with the UI!
2
In fact XMPP has shown me that even moreso than before, and I was already a giant fan before starting this project
@TimStone This comment sums it up best. I have to say, I personally would hate to run a site which was a community for developers because I would hate people messing with my code like we all do :-)
I'd be like, "Damnit, don't use /users/thumbs for that!!! That's not why I wrote that!!! Grrrrrrrr
Which reminds me now that @balpha and @MarcGravell are here, almost as if @KyleBrandt has some Nagios rule to alert them when users are hacking the chat... is there a better JSON interface which gives me a user's gravatar email hash as well as "about me", or is /users/thumbs ok...?
@MarcGravell and @balpha: You're welcome to come mess around with my code to return the favour, but I imagine you wouldn't find it as fun or useful, heh. :P
The /users/thumbs route should work, but kindly add showUsage=false on the query-string. however, please don't interpret that as carte-blanche "go crazy" - if any route is (ab)used to the point it causes any system harm, you should expect that route to start changing. Hourly.
@TimStone Yeah, I'm very scared that @MarcGravell or @balpha get bored and decide to peek through the userscripts in my repository. Would probably take them 30 seconds to rip it apart. <_<
@MarcGravell and @balpha I will certainly use &showUsage=false. And I am not trying to abuse anything and if you see any activity from my IP addresses (I'm sure you know what they are :-) that is suspicious, looks malicious, causes excessive load or you don't like for any reason, please just email me and ask me to stop, and I will. Instantly. (I'm sure you know my email too :-)
@TheUnhandledException are you going to cache it like once a day or anything and check against an internal stack/db so that if they join multiple rooms you're not hitting the rooms overly hard?
@drachenstern Heh. I tried earlier to have one SOXMPP_User object per bridge instead of one per room... if failed. Miserably. So until I can see why, each room has it's own list of SOXMPP_Users, each one having an SOChatUser, each one will try one time to fetch the user's gravitar
Actually there is probably a lower-impact route you could use... the one @TimStone noted earlier is cheaper (when compared to multiple calls to thumbs).
@rchern Plus, this is one bridge for multiple users, being run from a backbone connected server. Should cause less load than 15 users in the chat room :-)
@TimStone haha, no problem, take your time. @rchern you could probably weigh in too, C# is OOP right?
@TheUnhandledException if you have anything else in life you want to do, don't do Angry Birds.
it's all about estimating trig in your head, which angle at which acceleration and deceleration and what's going to smash through what... don't even install the trial-freebie
There were some differences between the queries that lit the envelope and those that returned data on the /users/recent page - these have been refactored to use the same code.
Also, we're moving more and more activity into the Stack Exchange Inbox. As we make this transition, the envelope will ...
