The sound of GitHub
choir.io
choir.io
I also couldn't click to change the sound set: the popup thingy disappeared when I tried to click it.
It does, admittedly, feed my desire for pretty realtime data.
A minor bug report though; if you toggle playback on and off quickly you can end up with double/triple notifications for events — http://i.imgur.com/mu6Jr2o.png
Great behind-the-scene thinking. Alarming, sound for issue still made a nice connection in the brain. We have an issue, its software, but its real. 'Houston, we had a problem' feeling. Funny. Should be less alarming 'in production' for sure.
Fantastic project. Themes of sound pollution, ambient sounds, silence, hearing, listening (inside your head included) are much overlooked (!) stuff. And this modality is a very powerful one (as all the others).
Reminded me of http://onesquareinch.org/ and myriads of other projects, people attentive to sounds, recording them, sharing them. Universe in itself.
Apologies for emotional tone, just some quick thoughts.
Aldo and I each wrote a blog post on why we are building this:
http://beachmonks.com/posts/intro/choir.html
http://beachmonks.com/posts/explained/choir-explained.html
We've been slowly onboarding brave alpha users. We want to learn as much as we can from these early adopters, and plan to share our results in the form of short interviews published on our blog.
The first of these - with Ryan Baker of Timely - is up now.
http://beachmonks.com/posts/interviews/timely/that-siren-sou...
And from all software with sound effects, this is the closest to useful. Good job.
Ipad: no sound; Firefox 24 on android: instant browser crash; Chrome on android: finally works.
Our focus in the next 2-3 months is on the desktop clients. We'll release a OSX desktop app next week, then a Windows app after that. Mobile is crucial in the long run but unfortunately we can't do much until the browser vendors provide better support for playing sounds.
I wrote most of our javascript on firefox. My firefox has no add-ons except the Firebug. Could it be one of your extensions? Have you tried refreshing it? Which version/OS?
We use howler.js to play the sounds. I have to say that I was a bit surprised to find Chrome/Safari/IE can play mp3 but Firefox plays ogg. I even had to submit a patch[1] so that howler.js can work on firefox under some weird edge cases.
My gut feeling is that those leaks are the "socket connections" that Firefox hasn't garbage collected yet. The demo you are seeing is using long poll so there might be some good number of socket churns.
FWIW, WebSocket support is high on our priority list. We just need to find the time to implement that.