Timeline for How do the Stack Exchange WebSockets work? What are all the options you can send to them?
Current License: CC BY-SA 4.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 18, 2021 at 11:34 | history | edited | CommunityBot |
replaced http://chat.stackexchange.com with https://chat.stackexchange.com
|
|
| Dec 2, 2018 at 17:28 | comment | added | This_is_NOT_a_forum | The example is not so easy to get running with Firefox (v. 63.0.3) and NoScript. (In Firefox, the browser console is started by menu Tools → Web Developer → Web Console.) | |
| S Jul 23, 2016 at 11:22 | history | suggested | J F | CC BY-SA 3.0 |
Updated code to pretty-print the data
|
| Jul 23, 2016 at 11:09 | review | Suggested edits | |||
| S Jul 23, 2016 at 11:22 | |||||
| S Feb 12, 2016 at 5:27 | history | suggested | ert | CC BY-SA 3.0 |
Make the code actually readable :)
|
| Feb 12, 2016 at 3:56 | review | Suggested edits | |||
| S Feb 12, 2016 at 5:27 | |||||
| Dec 12, 2015 at 21:12 | answer | added | user152261 | timeline score: 7 | |
| Jul 4, 2015 at 11:59 | history | edited | Doorknob | CC BY-SA 3.0 |
edited body
|
| May 25, 2014 at 21:06 | answer | added | Jeroen Vannevel | timeline score: 20 | |
| Feb 24, 2014 at 22:08 | answer | added | Doorknob | timeline score: 28 | |
| Feb 3, 2014 at 2:19 | answer | added | Doorknob | timeline score: 14 | |
| Feb 2, 2014 at 19:18 | history | edited | ɥʇǝS | CC BY-SA 3.0 |
made it one line so it works
|
| Feb 2, 2014 at 19:16 | comment | added | ɥʇǝS | Ahhh. That makes much more sense. | |
| Feb 2, 2014 at 19:11 | comment | added | Doorknob | @ɥʇǝS You have to paste it all in; not line by line. | |
| Feb 2, 2014 at 18:48 | comment | added | ɥʇǝS | Now I got something i.imgur.com/2Z29Xk5.png but it doesn't look right. | |
| Feb 2, 2014 at 18:44 | comment | added | ɥʇǝS | @DoorknobofSnow Nothing happens.. I don't know what I might have done wrong.. | |
| Feb 2, 2014 at 4:03 | comment | added | ɥʇǝS | I tried it in Chromium and Firefox. | |
| Feb 2, 2014 at 4:03 | comment | added | Doorknob | @ɥʇǝS You've got to wait 15 seconds or so for questions to pop up. What browser are you using? | |
| Feb 2, 2014 at 3:59 | comment | added | ɥʇǝS | Nothing happens when I put those lines in my console.. I must be doing it wrong.. | |
| Feb 2, 2014 at 3:42 | history | edited | Doorknob | CC BY-SA 3.0 |
added 33 characters in body
|
| Feb 1, 2014 at 19:54 | answer | added | Manishearth | timeline score: 82 | |
| Feb 1, 2014 at 18:55 | comment | added | John Dvorak | in other words, we don't mind the order of arguments being changed once per six to eight weeks, but it would be nice if we are told about it nevertheless. | |
| Feb 1, 2014 at 18:46 | comment | added | Undo | @MartijnPieters All we really need is to know the websocket call for active network posts - it would really help in fighting spam, etc. Basically, we either let the small communities take care of themselves (which we don't want to do), we pound the API (expensive for both parties), or we get the websocket API call. We're not making a consumer-facing app, we'd just like to make a thing to help the network. So it doesn't need to be stable, just stable enough for us to be able to react to it. I hope I'm making sense ;) | |
| Feb 1, 2014 at 18:42 | comment | added | John Dvorak | @MartijnPieters in which case we are left with two other options: scrape every site (even if through the API) periodically (very expensive) or let the smaller communities drown in spam (undesirable) | |
| Feb 1, 2014 at 18:33 | comment | added | Martijn Pieters | I don't think you can count on the websockets API to be stable. There is a public API that is documented and supported, which also means that changes to the API take longer to manage. It could well be that it's not in the devs interest to document the websockets for public use. | |
| Feb 1, 2014 at 18:30 | comment | added | John Dvorak | Or we could just scrape the website or batch up to 100 requests per api call | |
| Feb 1, 2014 at 18:25 | comment | added | Undo | I hope the devs realize that if they don't tell us, we'll just write scripts to try things :P | |
| Feb 1, 2014 at 18:21 | comment | added | John Dvorak | I guess we could find out the IDs by experimentation, but experimentation has already failed us. | |
| Feb 1, 2014 at 18:18 | history | asked | Doorknob | CC BY-SA 3.0 |
