public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Felipe Bueno <bueno.felipe@gmail.com>
Cc: "kawa@sourceware.org list" <kawa@sourceware.org>
Subject: Re: irc
Date: Fri, 18 Sep 2015 21:14:00 -0000	[thread overview]
Message-ID: <CAF7oHQ6zZF-mE6E9jOP-ZgFidFneWU889xwCDQZYmB8hsOy96w@mail.gmail.com> (raw)

"I'm willing to experiment with IRC again.  I try it out every 6 years or
so and last about 3 days before giving up again"
:)
This pretty much sums up my experience with IRC for the last 10 years
or so... the only difference is that "I try it out every 2 years or so
and last about 1 or 2 days before giving up" heheh. But I really try
very hard to like it and to use it... it's such an useful and fun
tool. I don't know exactly why I give up.

Btw I am on #kawa right now and there's only one more person there
(mario-goulart) but I don't think he is reading the messages.

Felipe Bueno - https://www.keybase.io/felipebueno


2015-09-18 16:44 GMT-03:00 Jamison Hope <jrh@theptrgroup.com>:
>
> On Sep 17, 2015, at 3:42 PM, Per Bothner <per@bothner.com> wrote:
>
> > On 09/17/2015 12:30 PM, David Pirotte wrote:
> >> Hello,
> >> Per,
> >>
> >> Are you not hanging around the #kawa freenode irc channel? just connected and there
> >> is 1 user only, who's not you :), and no other kawa users?
> >
> > I didn't set to the Kawa irc channel, and I never got in the habit of using
> > irc, skype, or similar.  (At one workplace we used text skype, so I would sometimes
> > have that up.)
>
> Same here.  We have a Jabber server at work, but I almost never remember
> to sign on.
>
> >>
> >> I find it quite nice to interact in real time, it makes things more friendly and for
> >> quick quizz, wel, so much quicker! :)  wdyt?
> >
> > No objection in principle, if people were using it.  I do tend to get distracted
> > too easily (ooo - and intersting arcile on the web - must read it now), and
> > it's plausible irc might make that worse ...  But as long as it's not too busy
> > I guess it wouldn't be too bad  and if it gets too busy, that would be a nice problem
> > to have!
>
> I'm willing to experiment with IRC again.  I try it out every 6 years or
> so and last about 3 days before giving up again, mostly because I
> haven't thought of anything to say.
>
> Who originally set up #kawa?  ChanServ says it was registered in 2008.
>
> --
> Jamison Hope
> The PTR Group
> www.theptrgroup.com
>
>
>

             reply	other threads:[~2015-09-18 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 21:14 Felipe Bueno [this message]
2015-09-18 21:23 ` irc Per Bothner
2015-09-18 22:41   ` irc David Pirotte
2015-09-18 22:56     ` irc Per Bothner
2015-09-18 23:51       ` irc David Pirotte
2015-09-19  0:15         ` irc Per Bothner
2015-09-19  5:02           ` irc Matthieu Vachon
2015-09-19  7:42             ` irc Per Bothner
  -- strict thread matches above, loose matches on Subject: below --
2015-09-17 19:30 irc David Pirotte
2015-09-17 19:42 ` irc Per Bothner
2015-09-18 19:44   ` irc Jamison Hope
2015-09-19  2:42     ` irc Damien MATTEI

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=CAF7oHQ6zZF-mE6E9jOP-ZgFidFneWU889xwCDQZYmB8hsOy96w@mail.gmail.com \
    --to=bueno.felipe@gmail.com \
    --cc=kawa@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).