91–100 of 142 posts
The UI feels like a 1 to 1 copy of the Slack client, or is Slacks UI so common now copying it is just using the Chat-UI standard?
Slack borrowed a lot from earlier UIs, too. It's not like Slack is hugely innovative in this department, anyway. You pay for the service, not the UI.
Note that the same team also offer a Trello clone and an Evernote clone. Draw your own conclusions. http://digicoop.io/products
Quite the contrary: Project and knowledge management or so important that you should not have just one (and additionally closed-source) application for that.
It's good to have competitors who focus on different workflows (Evernote was not built to be collaborative, Trello does not offer other display modes such as cards and a basic calendar).
I would not complain if they created another CRM as simple as Highrise or an open source helpdesk that could replace Zendesk (I really like helpful.io for this, btw).
The very first sentence irks me: "[…] for the only standardized chat protocol [XMPP]" Haven't they heard about IRC (RFCs 1459, 2810–2813)?
I deeply appreciate the history and communities available on IRC, but as a protocol, good riddance to it.
A slight tangent, are there public XMPP servers? Are there open source projects that use XMPP for their public channels? I'm a little dismayed by how many Slack accounts I'm acquiring.
Note that the same team also offer a Trello clone and an Evernote clone. Draw your own conclusions. http://digicoop.io/products
They built a kanban board and a collaborative notes application. There is nothing wrong about that. Quite the contrary: Project and knowledge management or so important that you should not have just one (and additionally closed-source) application for that. It's good to have competitors who focus on different workflows (Evernote was not built to be collaborative, Trello does not offer other display modes such as card…
What prevents me from adopting XMPP for my team is the lack of push notifications to my phone. I don't want to have an app constantly maintain a connection and slowly drain my battery.
need to try it out to see how extensible it is.
If you disabled or drastically resized the avatars and put the usernames not in a separate line, the window could hold a lot more content for single-line conversations like that.
In my opinion, it doesn't matter if it looks like Slack. What matters is that I can deploy it on an existing infrastructure and still have control over the service instead of handing over control to a third-party.
I for one welcome slack competitors, self-hostable, open sources ones especially.
The very first sentence irks me: "[…] for the only standardized chat protocol [XMPP]" Haven't they heard about IRC (RFCs 1459, 2810–2813)?