From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] {OT} open-source: chat, tasks, resources, code
Date: Thu, 20 Dec 2012 13:02:46 -0800 [thread overview]
Message-ID: <CAN0CFw0YgpzYkpPqPyZ7xi4AfT6BLR3yh5o3h4xW+aMgPqECQQ@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiDWg90du8X=k4e0p5_-q6CnDthdi+N=iChbnmfhNx7WSg@mail.gmail.com>
>> I should have specified that the people in the organization are spread out
>> in different locations.
>>
>> It sounds like it is difficult/dangerous to run an internet-facing IRC
>> server and ejabberd is unstable?
>
> This is what VPNs are for. I haven't really heard anything seriously
> problematic about ejabberd outside of some folks dislike of adding
> another language runtime.
>
> Whatever you decide to run internally, you're going to need to become
> knowledgeable in its administration. This is why a fair amount of
> folks are outsourcing communications infrastructure. Few believe they
> have the time to learn to manage the thing properly.
Is ejabberd difficult to run over the internet safely?
- Grant
next prev parent reply other threads:[~2012-12-20 21:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 7:26 [gentoo-user] {OT} open-source: chat, tasks, resources, code Grant
2012-12-17 16:13 ` Michael Orlitzky
2012-12-17 17:05 ` Michele Beltrame
2012-12-17 23:48 ` Michael Orlitzky
2012-12-18 0:56 ` Grant
2012-12-18 1:06 ` Michael Mol
2012-12-18 2:10 ` Kevin Brandstatter
2012-12-18 2:33 ` Grant
2012-12-18 2:52 ` Kevin Brandstatter
2012-12-18 1:11 ` Alan McKinnon
2012-12-18 2:04 ` Grant
2012-12-18 11:30 ` Marc Joliet
2012-12-18 11:46 ` Michael Mol
2012-12-18 12:50 ` Alan McKinnon
2012-12-18 14:57 ` Marc Joliet
2012-12-19 20:14 ` Grant
2012-12-19 20:29 ` Michael Mol
2012-12-20 21:02 ` Grant [this message]
2012-12-20 21:27 ` Alan McKinnon
2012-12-20 21:28 ` Michael Mol
2012-12-20 21:32 ` Grant
2012-12-20 21:42 ` Michael Mol
2012-12-18 1:12 ` Michael Orlitzky
2012-12-18 1:59 ` Grant
2012-12-18 2:21 ` Michael Orlitzky
2012-12-17 17:08 ` Kevin Brandstatter
2012-12-18 1:02 ` Grant
2012-12-18 11:21 ` Ciprian Dorin Craciun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN0CFw0YgpzYkpPqPyZ7xi4AfT6BLR3yh5o3h4xW+aMgPqECQQ@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox