In my scenario it's so I can just have the dashboard open while I'm waiting for the build to finish (my use case might also be handled by sending real time notifications over Aphlict and updating build pages like that, but the dashboard works best for multiple commits).

buildable.branch is actually probably not trivial to implement given that in a DVCS like Git you can have multiple branches pointing to the one commit, and there's a question about how to represent multiple branches in that case.

You can probably use the diffusion.resolverefs Conduit call to resolve the commit into a list of branches and tags.

Yeah that'd solve the issue as well (I was just of the perception that exceptions were going to be used for STATUS_ERROR and setting the status would be for STATUS_FAILED).

In my scenario I'm performing a build on Bamboo and pulling the logs and build status across. If I throw an exception just to fail the target, then I get an additional exception log appearing, even though there's no useful information to gain from having it there (it failed because Bamboo indicates it failed, and the actual reason can be found in the logs that are automatically pulled from Bamboo).

It's not that I don't want to fail build targets, it's that the only way to fail a build target is by throwing an exception. Setting the build target status to STATUS_FAILED doesn't result get used because of this line:

Closed by commit rP5013969a54b0.

Guessing this is just bad routes allowing people to hit the controller without an ID.

My guess is that Apple devices are reasonably immune from this issue; I'd expect they have far high specifications. For reference, I have this phone: http://wiki.cyanogenmod.org/w/P700_Info

Slack does this and GMail / Google+ does it as well for their chat system. With the hangouts Chrome extension, hangouts pop up in a chat window, which not only shows you the new message but history as well. The polite thing to do as a coworker is to not read it :)

A bit more detail on my thoughts:

I'd just probably put the joined rooms above the private message Conpherences thread list. It seems to make the most sense.

Confirmed D9511 fixes the issue.

That won't work; rpcdn.com.au points to a different IP address because of HTTPS (and the notification server ports are not bound to that IP). The correct fix is to serve Aphlict off the primary domain.

Yup, it's CORS alright.

The only thing I can think of is that Aphlict is being served from the file domain (https://rpcdn.com.au) and not the main domain (https://code.redpointsoftware.com.au). I don't know whether CORS is preventing Flash from even running the applet.

No error popup.

(Notifications are working on secure.phabricator.com though)

(Started the server in debug mode again)

Looks like the server stopped for a moment, going to start it again and see what happens.

I turned on developer mode, I don't see any notifications or messages and there's nothing in the DarkConsole.

notification.debug is already set to true.

Aweeee yeeeaaahh. Real time notifications :D

I could maybe imagine binding Conpherence threads to projects, and then pulling in project events or something like that.

The use case tends to be when you're communicating with someone on a topic about work you're doing, usually something like:

Most of the uses I've seen in the wild ... are either more granular (trigger on certain files/text)

Oh, I already reported this. Oops.

Also feedback in T5180.