Instant Messaging for Teams
tesla.im
tesla.im
http://davidcel.is/blog/2012/09/06/stop-validating-email-add...
Fix this, and I'll try it out.
I tried: myname+tesla.im@gmail.com I got: 'Enter a valid email'
edit: can I get some commentary to season the down-voting?
The local part may consist of alphabetic and numeric characters, and the following characters: !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } and ~, possibly with dot separators (.), inside, but not at the start, end or next to another dot separator (RFC2822 3.2.4).
More at https://gist.github.com/EHLOVader/4531693 - What sort of encryption is used where?
- How is this encryption ‘enforced’?
- How are messages stored/logged and accessible to whom?
- How highly available are these services?
- How are users authenticated?
- What limitations exist for use on tablets?
- …
Just calling something ‘real geeky’ and throwing out some buzzwords is…well, insufficient to convince me.Edit: added ‘to convince me’
37signals' Campfire doesn't have information about some of the questions you answered on their website, but their app as you is wildly popular.
Hope this helps. Have a nice day.
That's a really great thing to do.
But you almost make it tricky to figure out how to register (by making me go to settings then click edit next to my name).
- Email messages when someone is mentioned but are offline
- Integration with source control, CI, and issue tracking systems being used, targeted by channel/group
- Ability to filter channels by conversation/users (includes some way to attach and track conversation topics on messages in the same channel)
- Web app with desktop notifications and ability to mute those notifications by type
Do the hard work of making these easy to configure and use, and you may be able to compete with hipchat/campfire/etc.
Yes, I'm saying you should use IRC.
My complaint isn't so much against SaaS as a whole as it is against things that violate the Unix philosophy. I'm against things that try to do many complex tasks and don't provide a simple text interface (or RESTful API or whatever).
The tradeoff is you get basic features all at once with little overhead. What you lose is any ability whatsoever to make other things work on top of the service/program/application/whatever you're using.
The reason this is always bad is because you're only a first time user once; you pay the startup/integration/setup/whatever cost once. After that, you're a user and you get to suffer under the poor or non-existent integrations forever. See also: http://xkcd.com/1205/
What is your "different way"? What makes your solution more valuable? There is not enough of a pitch on the front page to get me to try it out.
Have a nice day.