We have plans to add this.
We're very much listening. We're currently designing and implementing a few things that will eventually lead to this type of feature. It's still planned, but we unfortunately can't give an ETA at this point.
Unfortunately, we do not have an ETA. We're still hard at work improving the new UI (http://blog.flowdock.com/2014/07/09/the-next-flowdock-now-in-beta/), but we will get to this at some point. Aaron's neat workaround should help until then.
Jeff K is right: using this (or a similar) feature should be very simple, but it requires quite a few changes throughout Flowdock, so implementing it is not trivial. This is an important feature for us, and something that we plan on adding when we overhaul our notifications (flow-based settings, etc.) in the upcoming months.
One thing I want to clarify: we follow all votes and comments that are added here, and greatly appreciate the input from our (fantastic) users. We've failed to communicate that we do follow what goes on here, and will try to work on that in the future.
Many of the suggested features/fixes are things that we'd love to implement straight away. Unfortunately, we have limited design and development resources, meaning we have to prioritize features and implement the most critical ones first. This means that even though a feature idea is great, it might take some time before we can start tackling it. Votes and comments here do influence our prioritization.
Right now, for example, we're putting a lot of effort into building an iPad app, improving our Android app, and redesigning the whole UI in order to support a sidebar of flows (instead of the tab bar).
The Flowdock team has been working hard on infrastructure changes to make this possible. Once we finish that work, we’ll be able to start work on this feature.
We're going to be releasing a few things in the coming weeks that required us to mostly rewrite threading. Because of this, we had to hold off on working on this feature. But now that the thread rewriting is mostly done, we can start working on this again.
We're sorry this has taken such a long time. We understand how this is an extremely important feature, and will be solving it in one way or another.
Unfortunately, we can't promise any release date. We've come up with a few solutions, but none of them worked well enough. We do realize that this is an important issue, and will be working on a fix.
You can switch the thread view to the right side in the new UI by selecting "Flip side" from the thread menu in the top right (or by hitting Esc-s if you have keyboard shortcuts enabled).
Flows can be open to the whole organization or invite-only, the latter allowing you to have private group conversations.
This is useful and will be added, but it’s not currently our top priority. Basically when we know what avatar size(s) is/are necessary with the New Flowdock we’ll add this.
Flowdock looks for an avatar for the from_address email address from Gravatar. This can be used to display an avatar with team inbox items.
36 votesVille Saarinen responded
You can place a userstyle.css file in your ~/Library/Application Support/Flowdock folder to override the CSS of the OS X app.
We’re working on a big notifications redesign.
@everybody, @everyone, @anyone and @all do the same thing – hilight all users in the flow. It depends on users’ personal settings whether or not they are notified on the desktop. These tags don’t send push notifications to mobile apps.
@everyone, @all, @everybody and @all currently don't send push notifications to the mobile apps. We plan on making this configurable in the future.
You can try using this plugin to integrate TeamCity with your flow: http://netwolfuk.wordpress.com/2014/04/02/new-tcwebhooks-release-proper-support-for-teamcity-nested-projects/