Conversation started Feb 1, 2014 at 16:44.
hichris123
hichris123
Feb 1, 2014 16:44
That would be way too many API requests...
If there was a hidden websocket for them...
ManishEarth
ManishEarth
I looked
wait, not hard enough
hichris123
hichris123
Meaning there might be one?
ManishEarth
ManishEarth
@hichris123 So, ws://sockets.ny.stackexchange.com works like this: You first send it what you want (in this case "155-questions-active", let's call this the "data type"), and it responds with data corresponding to that.
You can also give it multiple data types (just send them one after the other), and it will return everything it gets for each one, with the results tagged according to which datatype they correspond to. The number "155" is site id, for example, SuperUser is like 3-*-*. (eg 3-questions-new). I guess 155 is for stackexchange.com
Jan Dvorak
Jan Dvorak
so, 155-posts-active?
ManishEarth
ManishEarth
dunno
Jan Dvorak
Jan Dvorak
Feb 1, 2014 16:53
it would be awesome; try it out
ManishEarth
ManishEarth
@JanDvorak you can test with websocket.org/echo.html
[ SmokeDetector ] Possible spam: Abu Dhabi ℯsℭort Serviℂes ∰~(+971551439440)~∰~(+971551439440)~∰
Jan Dvorak
Jan Dvorak
posts doesn't seem to work; nor does answers
it would be nice to have it documented somewhere
155-questions-new doesn't seem to return anything either
hichris123
hichris123
@ManishEarth So basically you could go through that instead of the API?
Jan Dvorak
Jan Dvorak
Feb 1, 2014 17:11
wait, you're using the API to get the question feed? I'm using the websocket
hichris123
hichris123
@JanDvorak No, we're using the websocket. I was saying for retrieving the answers of a question...
 
Conversation ended Feb 1, 2014 at 17:13.