Grove.io: Hosted, Searchable IRC Chat For Teams
readwriteweb.com
readwriteweb.com
Also, since it appears to be a new & custom irc server, i'd not really be willing to trust corporate communication on a platform known for attracting hackers.
Thanks for reporting these specific issues. We'll work on getting them fixed.
This may shock and surprise you, but I've been using IRC on servers without NickServ and ChanServ for decades. No services != not IRC.
Also, since it appears to be a new & custom irc server, i'd not really be willing to trust corporate communication on a platform known for attracting hackers.
Obvious troll.
I wonder why did the popular media portray IRC as a hacker hangout, when yahoo messenger rooms and other group chats are implementation of the same concept.
Rewriting an irc daemon from scratch is a bad idea. The multitude of existing irc daemons and their hybrids are proof that the technology's complex enough to take years to stabilize, much less secure. If it does actually succeed they'll run into the growing pains of scaling that (assuming they add standard irc cluster topology) will bring on netsplits and other potential issues. If I were a hacker i'd look at a from-scratch not-quite-complete alpha-release IRC daemon as a fun toy to mess with. And if I owned a company I wouldn't want to risk my private communications on such shaky ground.
I'm not saying it isn't a cool idea... it just needs a few years to cook before i'd put my money or business into it (or at least a reputable, secure codebase)
Disclaimer: I've been brainwashed by working in "enterprise" environments. I understand that is not necessarily your target audience.
Logging scares me when it is a hosted solution like this. I signed up for the trial (for personal use) and didn't see that configuration option. Maildrops are lots of fun, but dumps of your dev IRC chats? Most regulated environments have retention periods, and after that most communication is considered to be a liability and storage concern (IANL, TINLA). I would say that dev chats are useful for about a few months, max.
A non-hosted solution would be nice, but certainly takes a huge amount of effort to layer on something like that to what you already have.
Is there any open community (i.e. a grove.io instance) to join and chat about your product, get a feel for it? Sounds like a bit of maintenance headache, but probably worth it. I can't really demo it well by myself.
Also, I can't imagine talking to my coworkers like I am accustomed to chatting on IRC <ahem>. That's just a random thought.
Edit: spelling errours
Every company I've ever worked for has needed this.
If anybody wants a channel on freenode logged publicly, feel free to contact me.
(The search facility currently sucks, I'm working on a very different search backend these days).
Sure, IRC's protocol is simpler, but it's also not designed to support authentication or security natively, or to be federated in a "cross-network" way like XMPP is. It seems that XMPP is more modern, more flexible, and supports real user authentication natively - a win in every respect.
Plus most of the clients people these days use for IRC (Adium, irssi, Pidgin, XChat) support Jabber anyway.
* passwords required to connect to the IRC server,
* passwords required to use given nickname (enforced via NickServ),
* SSL.
At any rate, my original comment came off a bit the wrong way. I'm not trying to say that IRC isn't a workable solution for this kind of group chat system, as it clearly is. I just don't see why using IRC over Jabber (which seems more technically suited to this domain) is a selling point, especially in a marketplace crowded with group chat solutions.
That said, there's definitely room for both protocols and I could see supporting XMPP as well at some point.
Edit: Also XMPP supports UTF-8 for everyhting out of the box and as far as I know it's not really possible with IRC (or did that change over the last years?). E.g. nicks with non-ascii chars are no problem to have..
Why do you think it's not fun?
There is a size restriction, though, which I've run up against more times than I can count, since I never seem to be able to remember that it's there.
Setting up open source IRC servers is a pain. They are almost completely void of documentation. And as the article points out, IRC doesn't usually have the traditional username/passwords or access controls you really need for business group chat.
I realize this is an MVP. Here are somethings I think should be included:
* Groups. It makes it way easier to manage access controls.
* A way to invite outsiders. The specific use case is inviting customers to join a chat, without the customer taking up a user/license seat.
* You've probably done these but I can't tell from the website; persistent chat rooms and varying admin privileges (ops in some rooms, not others, ability to create rooms, etc.).
EDIT: Why was my comment down voted?
Back in 1999 - I used IRC to manage my IT org. We had two IT channels: one for IT staff, which we were all required to be logged into when on the clock - and another that was company wide, where users could jump on IRC to ask the IT/dev/support teams questions.
We used bots to train IT FAQ and system info...
So for example, we would type "DNS Server" and the bot would reply with the IP of the DNS server.
We could type in a hostname and the bot would reply with the system details we put in there.
So, i this had the capability of learning and storing data that was retrievable in this way, rather than simple search, I think it could be very useful.
User:"Whats the current version of ProductX"
Bot:"Product X current version is 1.1.2"
If you're interested, here's my client so far:
Look how meebo developed over the last years. First it integrated web and traditional chat media like ICQ, MSN and then they already moved on to integrate their chat services into other peoples web-businessmodels as a b2b service.
When you take that sort of investment, the rules of the game change a lot I think. It's no longer sufficient to make a few million profit a month.
And yet lots of shops pay 37signals for Campfire
Is there any way to integrate a file-uploading facility (drag'n'drop in the web client, ideally, like Campfire) to the IRC concept, or is that an impedance mismatch?
I'd say that means it'll likely be a paid for service. Maybe with a small free option.
I've been working on an open source version of what you're purporting to provide as a service.
I could charge instance-hours for a prefabbed EC2 instance image too.
But Grove intrigues me for the ability to hook up useful bots to IRC.
If Groupme had an API available now, I'm not sure Grove would offer any benefits for my purposes. But I love how this space is exploding with all sorts of cool services.
Update: I've made a few tweaks and it should be better now. fingers crossed
Currently, I am doing that (not with IRC, but with Jabber/XMPP) via my side-project http://TwoToReal.com (beta): You ask questions (or raise topics) for which automatically determined experts are then pulled in via IM into a real-time web chat (most of the knobs/switches are tuned by machine learning).
What are your pricing plans?
The nature of IRC's channel-level organization¹ obviates the need to set up independent servers for a given team group.
What advantage does something like this offer me over just opening a new channel on freenode?
¹I.e., access lists (ops, voice) and modes like +psk (p[rivate], s[ecret], and k[eyed]).
We used Convore in the past, and Grove has definitely encapsulated the best parts of Convore along with laser-focused features and great performance. We actually can't wait to be a (or the first?) paying customer.
For example, can you edit the searchable logs to remove spam?
Easy hosted custom plugins/bots would be awesome.
You can run your own IRC bot, of course, but then you have to worry about finding a server to run it on, keep it running, etc.
Eventually you could add a way to define custom plugins that are properly sandboxed.
Facebook.