[01:40] <rww> Flannel is a landlubber.
[01:40] <Flannel> rww: Don't make me keel-haul you
[01:44] <rww> So, now that all of the "lol freenode is going SASL only" spam stopped, I guess we'll be removing that link and putting all the silly goo.gl redirects back to real URLS? O:D
[02:13] <tomreyn> hi
[02:13] <Flannel> Hi tomreyn, how can we help you today?
[02:13] <tomreyn> i was actually looking for a channel related to system administration for the ubuntu.com related infrastructure
[02:14] <tonyyarusso> tomreyn: #canonical-sysadmins may be what you're looking for.
[02:14] <tomreyn> ah this sounds good, thanls
[02:14] <tomreyn> thanKs
[02:16] <tomreyn> tonyyarusso: actually that channel does not exist (anymore)?
[02:16] <tomreyn> it seems like all canoncical channels moved to a different network or something
[02:16] <tonyyarusso> o rly?
[02:17] <tonyyarusso> Good to know...
[02:17] <tonyyarusso> I know they were thinking about that at one point, but wasn't aware it had actually happened.
[02:17] <tsimpson> #canoncial-sysadmin, not -sysadmins
[02:17] <tonyyarusso> oh, or that
[02:18] <tomreyn> just as empty as the other
[02:18] <tsimpson> it's dead at this time of day/night/whatever
[02:18] <tomreyn> but:
[02:18] <tomreyn> -alis- #canonical                                           1 :CHANNEL HAS MOVED - https://wiki.canonical.com/MessagingSystems/InternalIRC
[02:18] <tonyyarusso> It helps if tsimpson can spell.
[02:18] <tonyyarusso> #canonical-sysadmin
[02:19] <tsimpson> it's 2:19, I don't bother trying :)
[02:19] <tomreyn> heh, thanks
[02:19] <tomreyn> it helps if i can read, too
[02:19] <tsimpson> that's probably something internal to canonical ^
[02:20] <tomreyn> sounds like it
[02:20] <tomreyn> thanks again and bye again
[02:43]  * rww pokes tsimpson in the direction of jack___ 
[02:44] <jrib> why are we banning jack?
[02:44] <jrib> gpc: ?
[02:44] <rww> I always knew gpc was secretly tsimpson.
[02:44] <gpc> he was banned for swearing first time
[02:44] <gpc> now ban evading
[02:44] <gpc> unless the ban was removed and I missed it
[02:44] <jrib> but he said "fuck" instead of "fsck" once, or did it happen before?
[02:45] <rww> jrib: he's been problematic for a few hours now
[02:45] <gpc> ^^
[02:45] <tsimpson> he compared one of our ops to a nazi, swore, and swore again
[02:45] <rww> repeated offtopic, and his reaction to being told to stop is discussing his ability to use /ignore.
[02:46]  * rww wandered off for a while, missed the nazi comment
[02:46] <tsimpson> also links to a graph of swear words in the linux kernel source when you ask him not to swear
[02:46] <gpc> basically thinks that he can do what he wants cuz he is 1337
[02:47] <jrib> ok
[02:47] <jrib> just appeared to me that the fsck mess up could have been unintentional but I wasn't aware of the previous issues
[02:48] <gpc> was a combination of attitude,cursing and repeating the cursing
[03:02] <rww> !gnash =~ s/^.*It/Gnash is an open-source Flash replacement. It/
[03:18] <rww> Is there a "this is how you suggest factoids" factoid I don't know about?
[03:18] <gpc> none I know of
[03:18] <persia> I don't think there ought be one.
[03:20] <persia> Oh, but there is:
[03:20] <persia> !factoid
[03:20] <rww> yeah, that's what I usually go with. Was wondering if there was a more specific alternative.
[03:22] <persia> http://ubottu.com/devel/wiki/Plugins goes into great detail about it.
[03:23] <persia> How frequently are there factoid change requests that are useful?  I see a lot of accidental recommendations, but only a few real changes a week.
[03:24] <rww> Not many. I swear there used to be more, but that's possibly because I was noticing me submitting them :<
[03:26] <persia> Or one could claim that the number of new things commonly explained is reduced, because the common issues have all been encoded.
[03:26] <persia> Then again, today seems a banner day :)
[03:27] <rww> !mysql
[03:27] <bazhang> gah
[03:28] <bazhang> wish people could learn scroll up
[03:28] <rww> s/8.04/10.04/ and it works for me.
[03:28] <rww> although could be less wordy.
[03:28] <persia> And it leads down an ugly path
[03:29] <persia> !info mysql
[03:29] <bazhang> !find sql
[03:29] <gpc> rww: cut out " It is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software."
[03:29] <persia> !info mysql-server
[03:29] <rww> !info mysql-server
[03:29] <persia> Could we have something akin to !info that provided the long description?
[03:29] <bazhang> truepurple is consistently asking this fat16 question for some many hours now
[03:30] <persia> That ought work for arbitrary packages, and avoids a slippery slope with people trying to get 30,000 new factoids: one for each of their favorite packages.
[03:31] <rww> ubottu used to translate !foo to !info foo if a 'foo' factoid didn't exist and it was a package. I forget why it stopped doing that.
[03:32] <persia> e.g. !describe mysql-server would reply with " This is an empty package that depends on the current "best" version of mysql-server (currently mysql-server-5.1), as determined by the MySQL maintainers. Install this package if in doubt about which MySQL version you need. That will install the version recommended by the package maintainers.
[03:32] <persia>  MySQL is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of MySQL are speed, robustness and ease of use."
[03:32] <gpc> we don't want that in #ubuntu
[03:33] <rww> one would hope that the only in-channel output would be "foo, please see my private message" ;)
[03:33] <gpc> ^^
[03:33] <gpc> +1
[03:34] <persia> The key is that having per-package factoids or per-software fatoids ends up becoming unmanageable, and allows claims of discrimintation against specific packages.
[03:34] <gpc> We will NEVER make everyone happy. So why worry about it.
[03:34] <rww> hasn't happened yet despite the per-software factoids we have *shrug*
[03:36] <persia> Likely hasn't become unmanageable because of self-selecting population of folks adding factoids and scaling issues with #ubuntu.
[03:36] <persia> It has resulted in claims of discrimination, but not in a very visible way yet.
[03:37] <rww> "scaling issues" isn't automatically a valid argument against anything in #ubuntu, you know ;P
[03:38] <rww> The channel population isn't exactly going up quickly, and it's working thusfar.
[03:38] <persia> I've had the impression the channel population had been mostly static for the past 18-24 months.  Am I mistaken?
[03:39] <rww> no
[03:39] <rww> that's my point. you don't have to worry about scaling if you're not getting bigger.
[03:40] <rww> ( http://status.nullcortex.com/other/other/irccount2.html shows about the last 11 months, for anyone else who likes shiny graphs)
[03:40] <persia> From that, combined with increasing complaints about finding #ubuntu hard, I've developed the opinion that #ubuntu has gotten as large as it can, and is increasingly serving a self-selected audience.
[03:40]  * persia likes shiny things
[03:42] <rww> for what it's worth, the only discussion I've seen on #ubuntu's size started in 2009 and died early in 2010.
[03:42] <rww> perhaps there are others going on I haven't seen.
[03:43] <persia> I haven't seen any others.  I believe that #ubuntu was painfully overflowing from early 2009, but no real solution was identified to address this.
[03:44] <persia> The impression I have from other sources is that there is a general shift away from recommending IRC as a primary support mechanism.  I'm unsure if this is a good thing.
[03:45] <rww> We have more support options in general now (Ask Ubuntu being the new shiny one, for example). Personally, despite my misgivings about AskUbuntu, I think that having a variety of options so people can use the format that suits them best is a good thing.
[03:46] <rww> If there's an additional "don't use IRC, it has $problem" impetus on top of that, then that would be something to address, but as you say (and I agree), nobody's identified a decent solution.
[03:47] <persia> I think I'd be happier if all the options were coordinated by some central knowledge repository for use by the support team through all the interfaces, but that's just me preferring that people don't have to engage multiple teams because the answers may differ.
[03:48] <rww> By "central knowledge repository", do you mean a source containing definitive information that the different support media could use?
[03:48] <bazhang> truepurple seems to be just trying to prove Gnea wrong on the fat32/fat16 issue, he/she has not even installed ubuntu or done the suggested fixes.
[03:48] <rww> because help.ubuntu.com could do that, if it were actually maintained well :\
[03:49] <persia> rww, The disconnect between the docs team and the support teams doesn't help, precisely, but yes, that could be the resource.
[03:50] <persia> I suspect that the docs team would be happier to have more people helping maintain docs, and I suspect the support teams would be happier having a central place to find the answers, but it requires cooperation and coordination and collaboration and collusion.
[03:51] <rww> Yeah, I've looked into getting involved in docs myself in the past. I forget whether it ended up being a hassle or I got busy, but I didn't end up doing much of anything.
[03:52] <rww> but ultimately, making more excellent and accessible documentation would decrease the number of people needing support, and the people offering support in various places know enough to write documentation (and tend to have at least enough English skills to communicate), so it'd be a useful match if it happened.
[03:54] <persia> I suspect the big obstacle to making it happen is a lack of leadership in the support teams.  There's lots of stellar individuals, but most tend to be focused on things like "forums" or "IRC" or "mailing list" or similar, and not on "support".
[03:55] <persia> so when folk interact with the support teams, they often find there's nobody there that can coordinate, and nobody with whom to collude.
[03:55] <persia> That said, the support teams do *great* work in collaboration and cooperation, for the most part.
[03:56] <rww> IRC support doesn't tend to coordinate well. #ubuntu-irc-helpers tried to address that, and the channel didn't end up talking about much other than "so why does this channel exist?"
[03:57] <rww> There's a core group of people that stick around, but the majority of helpers in #ubuntu are people who get helped with a support question, stick around for a couple of weeks, and then wander out again.
[03:57] <gpc> and the crazies like us who stay for life
[03:58] <persia> Essentially providing support to the value of the support received.  I think that's common, and a good thing.
[03:58] <rww> Indeed. I've done the same thing in other places.
[03:58] <persia> But there may be benefit to closer coordination between the different support fora, and some way for those who stay involved to help gain recognition and make more of a difference.
[03:59] <bazhang> truepurple insists on polling.
[03:59] <rww> gpc: The difference between them and us would be an interesting sociological study, methinks.
[04:00] <gpc> bazhang: :/
[04:00] <gpc> I tried
[04:00] <rww> People who stay involved in IRC get informal recognition from other channel members and can get Ubuntu Membership eventually for IRC contributions (has anyone done that through IRC Council yet? I haven't been paying attention). Roughly the same as other areas of the project, I think.
[04:01] <gpc> rww: I believe that is exactly what I did before this new way of getting membership
[04:01] <gpc> my contributions were almost 100% irc related
[04:01] <rww> gpc: My membership is partially due to #ubuntu too, and I know some other people are the same way, yeah.
[04:01] <persia> Sure, but what happens is that people get membership for their work in IRC, not for their work in support, which fractures the support team.
[04:02] <persia> Some folk do support in multiple places, and get endorsements from multiple groups when applying for membership.
[04:02] <bazhang> gpc, yep. he seems to want us to paste the entire FAQs from each available one into the channel and comment on them
[04:02] <persia> To look at another area: there's a lot of infrastructure to support the advocacy folk, in a variety of places (LoCos, design, branding, etc.).
[04:02] <persia> There's not much like that for support.
[04:02] <gpc> bazhang: I suppose you could quiet him and ask him to join here and then spend an hour explaining why we think he is polling
[04:03] <bazhang> gpc, nah. he seems to be getting the message after 5 or6 people have told him not to poll
[04:04] <rww> persia: I don't understand the distinction here. As someone who did LoCo stuff and does IRC stuff, the number of times I interacted with the design/branding side of things is about equal to the number of times I link to the forums :\
[04:04] <persia> rww, You never used an Ubuntu logo, or handed out an Ubuntu business card, or similar?
[04:05] <rww> persia: Sure. I also use information from the Forums on occasion.
[04:06] <persia> Ah, hrm.
[04:07] <persia> I have the impression that the LoCo team structure has folk who are actively working with the branding and marketing folk to ensure common communication in advocacy.
[04:07] <persia> I don't have the impression that there are IRC support folk who are coordinating with forums support folk to ensure common solutions.
[04:07] <persia> That's the distinction I see.  I may be completely mistaken.
[04:08] <persia> (in fact, I hope I'm mistaken).
[04:08] <rww> I may be too, but I don't remember ever actively working with branding or marketing folk. The LoCo ecosystem is... complicated, though. So my experiences and the experiences of someone in a different LoCo are liable to be very different.
[04:09] <persia> "complicated" is a good word :)
[04:10] <rww> Given that the various support media are very, very different, I think the best way to coordinate on common solutions is by using help.ubuntu.com (or another similar hypertext, editable-by-anyone resource), and thus coordinating with the docs team.
[04:11] <rww> It'd be an interesting attempt, especially since IRC (factoids) and the forums (walkthroughs? faqs? i forget what they call them) already have their own knowledge silos.
[04:11] <persia> I think you're right.  I think it would work best to have a couple folk from IRC support, a couple folk from forums support, a couple folk from askubuntu and a couple folk from the docteam meet regularly and make sure everything is going smoothly.
[04:11] <bazhang> threads
[04:12] <rww> and the whole point of askubuntu is that questions only get asked once and then in the future the answers are already available on askubuntu, so that whole site is its own silo ;)
[04:12] <rww> bazhang: I mean the subforum I vaguely remember seeing at some point where they put particularly useful and often-used guides
[04:12] <persia> won't reliably work that way, any more than the forums do.
[04:13] <bazhang> sticky?
[04:13] <rww> persia: well yeah, but they can dream I guess
[04:13] <persia> rww, I guess, although if someone wanted to fix this, I suspect they'd be just as happy to help with general coordination.  Takes a while to build the silo, after all.
[04:14] <rww> *nod* I'm not claiming that they'd be a problem, just that they also have their own thing going on, just like the rest of us.
[04:14] <rww> bazhang: if I could find the dang thing, I'd let you know >.>
[04:15] <rww> oh, there it is
[04:15] <rww> http://ubuntuforums.org/forumdisplay.php?f=100
[04:17] <persia> Speaking from a development perspective, it would be useful for such a group to exist and to ensure developers were aware of particularly awkward solutions, in the hopes these could be targeted for improvement.
[04:20] <rww> (oh joy, robertzaccour and jack_ both in #ubuntu-offtopic. I get the feeling this might turn into a long night.)
[04:22] <rww> persia: Good point.
[04:22] <persia> rww, Maybe someone will have time to organise and lead that team :)
[04:23] <rww> hrm, perhaps I should look into ubuntu-docs again anyway. especially because my "stuff I do in Ubuntu" list is stagnating
[04:24] <rww> persia: Yeah, I was thinking the other day that I need to order a time-turner from Harry Potter -land...
[04:25] <persia> Doesn't help that much: if you have more time than everyone else, you still only have so much time.
[04:27] <rww> on a related note to this and the original topic... #ubuntu-meeting doesn't scale :<
[04:28] <rww> s/original/once-removed-from-original/
[04:30] <persia> Indeed.  That failed badly, and in the manner of the failure, helped fragment the Ubuntu community.
[04:30] <persia> It's a different issue than #ubuntu: not the too-many-people problem, but the too-hard-to-schedule problem.
[04:31] <persia> It would be trivial to fix by having multiple meeting rooms (perhaps based on the names of moons, so #ubuntu-meeting-phobos and #ubuntu-meeting-titan, etc.)
[04:31] <persia> And a common scheduling system.
[04:31] <persia> The current model means more and more folk have meetings in their own private spaces, and nobody sees the results.
[04:32] <rww> I was thinking of the same solution. I haven't looked into it too much, though, so I don't know enough to evaluate ideas about it.
[04:33] <persia> Main issue is that it's more channels in which to idle, and hard to schedule.
[04:34] <rww> and people getting confused/forgetting about which channel they're supposed to go to.
[04:35] <persia> -meeting would have to have a bot with redirection, but getting a bot that can talk to Google Calendar about repeating meetings is hard, and everyone seems to prefer using google calendar to schedule meetings than something else.
[04:37] <rww> As someone who tends to complain about channel logging, I have to admit that most team channels being logged turns people having meetings in their own channels from "impossible to read up on" to "inconvenient to read up on".
[04:37] <rww> especially now that the LoCos switched logbots so everyone's on the same server
[04:38] <persia> I'm concerned about the inconvenience, but moreso, about the disconnect.
[04:39] <persia> Lots of folk idle in -meeting, and if their name is mentioned, or they happen to be around for a meeting that interests them, they can get involved.
[04:39] <persia> If the meeting is somewhere else, they never know about it.
[04:48] <rww> Indeed. Team reports mitigate the "stuff is happening and nobody hears about it" aspect, but real-time communication is hindered by everyone being in their own space.
[04:48] <rww> (and I'm very aware that team reporting has its own set of issues)
[05:08] <rww> bazhang: #ubuntu-trivia is still broken ;)
[05:08] <bazhang> rww, on and off.
[05:09] <rww> the bot hasn't worked any time I've been in there in months :\
[05:09] <rww> might be fun to get something working in time for the next Ubuntu release, come to think of it
[05:14] <bazhang> 'directly download netinstall'?
[05:14] <bazhang> too bad there is not a #unetbootin channel
[05:29] <bazhang> !google | test
[05:29] <culb> Results for | test on Google:
[05:29] <culb> --
[05:29] <bazhang> culb, please disable that script
[05:29] <maco> uh thats interesting
[05:29] <rww> !google puppies
[05:29] <culb> Results for puppies on Google:
[05:30] <culb> --
[05:30] <maco> the script seems to work poorly though
[05:30] <bazhang> just a spambot
[05:30] <rww> :(
[06:00] <rww> !asl =~ s/english/English/
[06:14] <rww> maco: oops, sorry, didn't notice you there. I saw all the faily comments in red and pounced
[06:14] <maco> its ok
[06:15] <maco> what was the first fail you saw?
[06:16] <rww> maco: he set off an orientation-related highlight
[06:16] <rww> they **
[06:17] <rww> I keep assuming trolls are male. I should not :(
[06:17] <maco> given the "unstable like a woman" slam, i suspect it'd be accurate in this case
[06:17] <rww> well yeah, but still
[06:17] <tonyyarusso> Should have used "unstable like an Arch box"
[06:18]  * rww laughs out loud
[06:23] <rww> Arch isn't particularly unstable in and of itself. The whole rolling release model, with new major versions of packages popping up and breaking stuff is the issue.
[06:25] <persia> That's not even an issue if well-managed.
[06:26] <persia> The issue comes when one needs to adjust ABI, or worse APIs, and has to do everything at once: it tends to be poorly tested (or, worse, hacked about in an attempt to avoid it)
[07:09] <bazhang> thats got to be several times markskilbeck has been using the 'nazi'
[07:41] <elky> persia, well-managed is fine for setting a best-world scenario. The people who are going to adopt the rolling release model aren't the kind to allow themselves to be limited by management ;)
[07:42]  * persia mumbles vaguely about Android and ChromeOS
[07:49] <KB1JWQ> Ten minute tempquiet since it was disrupting the channel.
[07:49] <Tm_T> thanks, was about to revove him but hopefully that'll sort it too
[07:49] <KB1JWQ> Yeah, I tend to start small.
[07:50] <KB1JWQ> Sorry if I overstepped. :-)
[07:50] <Tm_T> you didn't (:
[07:50] <Tm_T> I don't think you can
[08:25] <KB1JWQ> Same user, obviously.
[08:25] <rww> he was USA!ing about a week or so ago
[11:47] <jussi> Quick reminder that the IRCC meeting is in 15 mins.
[11:49] <knome> #ubuntu-meeting?
[11:49] <tsimpson> yeah
[11:50]  * knome will join and lurk you all
[13:16] <ikonia> hello dejvid
[13:17] <dejvid> čus
[13:17] <ikonia> dejvid: hello
[13:19] <dejvid> hello :D
[13:20] <ikonia> dejvid: you're in the #ubuntu-ops channels, how can we help you today ?
[13:22] <dejvid> as a dam on ubuntu games?
[13:22] <ikonia> pardon ?
[13:23] <dejvid> prepač ja som zo slovenska a neviem velmi hovorit po anglicky
[13:23] <dejvid> sorry I am from Slovakia and I can not speak English very
[13:23] <ikonia> dejvid: I'm sorry, I don't understand, do you speak English
[13:23] <ikonia> dejvid: ok, what do you need from this channel ?
[13:28] <topyli> hm, there's no Slovakian channel. -sv forwards to -cz
[15:00] <gpc> is ubottu supposed to be returning bug info in #ubuntu?
[15:02] <charlie-tca> yup
[15:03] <charlie-tca> didn't they just turn it back on
[15:03] <ikonia> I personally think posting bug information in #ubuntu is not a good idea.
[15:03] <charlie-tca> IRCC decided to try it again
[15:04] <ikonia>  Sepuku ?
[15:04] <gpc> Why try it again, it adds scroll to the channel and confusion
[15:05] <Tm_T> I think this is not the time and place to raise concerns, should have been before/during the meeting and/or should be done after some period
[15:05] <ikonia> Tm_T: they have been raised before
[15:06] <Tm_T> bah, not exactly the words I was looking for but you get the point, I hope
[15:06] <Tm_T> ikonia: good (:
[15:06] <ikonia> however all's that matters is the council +1/-1
[15:07] <ikonia> why is ubottu spitting out natty bugs in #ubuntu
[15:07] <gpc> I wonder why this isn't the time or place
[15:07] <gpc> the bot is making noise in the channel.
[15:08] <ikonia> pointless noise with natty bug reports
[15:08] <gpc> but whatever
[15:08] <ikonia> there is a bug in launchpad that says #ubuntu is too noisy to be useful with compelling arguments on both side of the coin, so we start the bot spitting out more stuff,
[15:10] <Tm_T> gpc: ikonia: I said "this is not the time or place" as I hadn't seen any bug reports been said in #ubuntu
[15:10] <ikonia> the only place I see it as valid is #ubuntu+1 as that is a channel being used to develop/progress a development release (outside pure dev channels)
[15:11] <Tm_T> I'm not against testing, so we have hard proof of how much it causes extra noise there
[15:11] <gpc> Tm_T: I understand now what you meant. I also feel that anytime someone has a concern they should feel comfortable to raise the issue and discuss it.
[15:12] <charlie-tca> Tm_T: +1
[15:12] <gpc> anyway, the bot "saw" 1 bug number and spit out info on two in the channel.
[15:13] <gpc> my vote doesn't mean much but -1
[15:13] <charlie-tca> As long as the extra noise in #ubuntu doesn't mean the quieter channels lose the bot. Not sure the reasoning was valid, but I missed the meeting, too.
[15:16] <gpc> the extra noise in #ubuntu is not useful and confusing.
[15:18] <gpc> How many bug numbers will the bot parse and return info from in one post to the channel. What I mean is if someone comes in and pastes a list of 20 bug numbers what happens?
[15:26] <jrib> I agree with ikonia, -1 on ubottu making more noise in #ubuntu
[15:31] <Pici> Respond to the email to the mailing list then,
[15:43] <topyli> it's been in testing in #kubuntu and #xubuntu for months now. there it adds about 1 line per day. well see how much it is in a much bigger channel and evaluate its usefulness vs noise
[15:45] <gpc> topyli: is there a way to disable the bot also adding info when it sees "dup-of: XXXXX"
[15:46] <topyli> no idea
[15:46] <gpc> tsimpson: ^^
[15:47] <gpc> least in #ubuntu
[16:46] <nixternal> to bad freenode can't do ssl worth a darn. every netsplit i have someone telling me to ident with nickserv. only on freenode
[16:46] <Tm_T> nixternal: sounds weird
[16:47] <nixternal> i am actually going to blame on the sasl script i think, because AndIRC on the Android doesn't have that issue now that I think about it with sasl
[16:48] <Tm_T> nixternal: I haven't noticed any issue with irssi
[19:45] <tonyyarusso> nixternal: seconding Tm_T - fine here with irssi.
[19:46]  * tonyyarusso also adds a -1 to bugspam in #ubuntu - it's not generally useful for that audience, unlike in devel channels where people are likely to actually care
[19:51] <rww> I don't think it's useful. I also think three invocations in the last three hours means it won't be very spammy. If it starts being spammy, I'll start caring :\
[19:51] <rww> ( grep "Ubuntu bug" * | grep "ubottu>" )
[20:19] <tsimpson> we are tracking the usage in #ubuntu
[20:20] <tsimpson> we have been tracking it in #kubuntu and #xubuntu for a while, where it averages somewhere around 1 per day
[20:20] <tsimpson> we'll see how (over)used it is in #ubuntu and make a decision
[20:34] <Pici> meh
[21:28] <gpc> rww: PM?
[21:28] <rww> gpc: sure
[21:36] <maco> the fact that it spits out the link does give people a chance to click the "me too" button though
[21:37] <ikonia> yeah "me too" is not useful though, it's almost "like" on facebook
[21:38] <Jordan_U> I expect it's usually triggered by people posting a link to a bug report though, rather than saying "bug #12345".
[23:36] <Pici> ...
[23:40] <Madpilot> ...
[23:41] <Pici> messaged.
[23:42] <Madpilot> I just called them out in #u
[23:42] <Pici> That works too
[23:53] <Pici> maco: That discussion with kieppie in #ubuntu looks like it probably belongs in -offtopic or pm.
[23:53] <Pici> but /me shrugs
[23:54] <maco> fair enough