[06:13] <MTecknology> newz2000: are you ignoring me? :P
[06:50] <knome> MTecknology, no, i'm ignoring him.
[06:50] <knome> ermm.. ;)
[06:50] <SiDi> hi hi
[06:51] <SiDi> you ignore me, knome ? :'(
[06:51] <knome> morning SiDi!
[06:51] <knome> nope. i ignore nobody.
[06:51] <SiDi> and why do you ignore him ?
[06:51] <knome> that was a joke.
[06:51] <MTecknology> I have one ignore - 0:51    1 root: MSGS
[06:52] <knome> i have ignores as well, but they are only ignores for different types of messages in channels
[06:52] <knome> eg. joins and parts in boring channels ;P
[06:52] <knome> like ermmmm... #ubuntu-website :P
[06:53] <MTecknology> that's pretty much what mine is for too
[06:53] <MTecknology> bitlbee
[06:53] <SiDi> mine ignores any message
[06:53] <SiDi>  /ignore *
[06:53] <SiDi> yes, i'm ignoring both of you right now !
[06:55] <SiDi> stop ignoring me Q.Q
[06:55] <knome> MTecknology, i have an irssi script that makes the bitlbee root messages more readable (and also so short that they fit a normal terminal window) and modifies their type so that they don't create "activity"
[06:56] <MTecknology> nice
[06:56] <MTecknology> I'll have to grab it sometime :P
[06:56] <MTecknology> irss.org?
[06:56] <knome> http://blog.knome.fi/files/2007/02/fixbbpl.txt
[06:56] <knome> nope, only private use ;)
[06:57] <knome> it might be a bit crappy code, but hey, it works.
[06:57] <MTecknology> I'll try it out sometime, thanks
[06:58] <knome> np.
[06:58]  * MTecknology goes back to coding svg and all the annoying they come with
[06:58] <knome> oh wow, that email is outdated
[06:58] <knome> i don't even have access to it anymore
[14:43] <newz2000> MTecknology: not ignore you, are you trying to reach me?
[19:35] <MTecknology> newz2000: regarding that tarball I sent you a while ago :)
[19:35] <newz2000> oh, no, not ignoring you per se
[19:36] <newz2000> but I am consistently failing to reply
[19:36] <MTecknology> I was just curious if you ever got around to look at it :P
[19:36] <MTecknology> then I was going to ask what you thought
[19:37] <newz2000> I did look at it and I'm still not sure what I'm looking at. I'm not sure what problem it solves and I don't understand the solution.
[19:37] <newz2000> let me open the tarball again, just a min
[19:38] <MTecknology> You're familiar with Drupal. Do you have your own drupal site?
[19:38] <newz2000> yes
[19:38] <MTecknology> It's just text files for each banner option.
[19:38] <newz2000> each text file contains a reference to the js file (a script tag)
[19:39] <MTecknology> I'd prefer it if instead I were able to just grab a tarball of the entire thing, but because you guys control the minute the banner switches to showing as released, it's not really possible
[19:41] <MTecknology> The project is lp:drupal-ubuntu-countdown
[19:41] <newz2000> a tarball of the entire "what"?
[19:42] <MTecknology> all the images and everything needed so there's no need for your servers to get hammered
[19:43] <newz2000> a tarball of the images is certainly possible
[19:43] <newz2000> the only thing that gets tricky is to know when the image "it's here" should show
[19:43] <MTecknology> that's what I was referring to
[19:44] <newz2000> but currently what I do is modify the js file
[19:44] <newz2000> it's not a big deal to modify something else so that your script can detect the change
[19:44] <newz2000> you may have noticed that the js doesn't appear to change for an hour or two after release...
[19:45] <newz2000> this is because of our caching rules changing
[19:45] <MTecknology> ya, I did actually
[19:45] <MTecknology> You could log into the website and clear cache
[19:45] <newz2000> this trigger we're referring to would suffer the same problem
[19:45] <newz2000> we do that
[19:45] <MTecknology> oh
[19:45] <newz2000> well, wait
[19:46] <newz2000> we modify the servers in the day or days before release to prevent shift+reload from working
[19:46] <newz2000> the caches basically get a static copy of the site
[19:46] <newz2000> then we release the caches for a moment when it's time to release
[19:46] <newz2000> and then again shortly after release
[19:47] <newz2000> it's this second tiem that the js and banners change
[19:47] <newz2000> might be 15 min after or 2 hours after, but right in there
[19:47] <newz2000> anyway, your trigger script that detects the change would be subject to the same delay
[19:47] <newz2000> it's really not a big deal
[19:47] <newz2000> but if all you want is a trigger we can do it
[19:48] <MTecknology> would you be willing to host a tarball for it as well?
[19:48] <MTecknology> I don't have the bandwidth to offer for that sort of thing? I get 50mb up but my bandwidth/month is pretty low
[19:48] <newz2000> well, we host it on the wiki currently
[19:48] <MTecknology> where?
[19:49] <newz2000> wiki.ubuntu.com/Website
[19:49] <newz2000> there's a page for the countdown banners and we put it there somewhere
[19:49] <newz2000> what is the purpose of the tarball, is it somehting your script will automatically grab? If so we should not host it on the wiki
[19:49] <MTecknology> ya, that's it purpose
[19:50] <newz2000> so instead we should create a ppa or something similar
[19:50] <newz2000> otherwise someone could stuff the tarball with nasty php or something
[19:50] <newz2000> or we could just agree on a naming scheme for the files
[19:50] <newz2000> and host them on ubuntu.com
[19:51] <newz2000> what we should do is hold off for just a bit
[19:51] <MTecknology> hrm... how hard would it be to pull a ppa w/ php?
[19:51] <newz2000> probably hard. :-)
[19:51] <newz2000> I'm working on a solution to host static content
[19:51] <newz2000> for ubuntu.com and the related websites
[19:51] <newz2000> I'm hoping to have some progress soon
[19:51] <MTecknology> alrighty
[19:51] <newz2000> it would be the ideal place for this stuff
[19:52] <MTecknology> I'll look into the ppa as well, just since that sounds like it could be a fun idea
[19:52] <newz2000> sure
[19:52] <newz2000> we could probably put a redirect in place on ubuntu.com that points to the final location of the files
[19:52] <newz2000> it would only change once each release around the beta period
[19:54] <MTecknology> You should take a peek at the source code sometime, or try out the module :) - I think I did pretty decent work on it
[19:54] <MTecknology> Everything I'm producing I'm going to try to port to D5 when it's all done
[19:55] <newz2000> ok, I will
[19:55] <MTecknology> I'll wait a week or two before I poke you again :)
[19:55] <MTecknology> or more if you prefer... somehow I get the feeling you're a busy person :P
[19:56] <newz2000> well, there's always more to do than I can do, so it just comes down to priorities
[19:56] <newz2000> this will probably increase in priority as it nears time to release banners again
[19:57] <MTecknology> holy crap...
[19:57] <MTecknology> why ppa...
[19:57] <newz2000> yeah, bad idea
[19:57] <newz2000> that's just for debs
[19:57] <MTecknology> but no reason we can't do something like https://edge.launchpad.net/ubuntu-drupal-releases/6.x/6.3.2
[19:58] <MTecknology> We could use a redirect on ubuntu.com to point at w/e
[20:00] <MTecknology> what's your opinion on that?
[20:00] <newz2000> I think we can do better
[20:01] <MTecknology> you don't like the launchpad idea?
[20:01] <newz2000> wait, is this to a .deb file or can we host any file there?
[20:01] <newz2000> oh, any file
[20:01] <newz2000> yes, that's good
[20:01] <MTecknology> yup
[20:01] <newz2000> sure
[20:01] <MTecknology> http://edge.launchpad.net/ubuntu-drupal-releases/6.x/6.3.2/+download/ubuntu-drupal.tgz
[20:03] <MTecknology> It's look something like http://launchpad.net/drupal-ubuntu-countdown/head/jaunty/+download/jaunty-banners.tgz
[20:04] <MTecknology> not only that, but then I can have my group keep owning the code, but I can also add you ~ubuntu-website as maintainers so if I randomly die then you guys can keep it up to date
[20:05] <MTecknology> You think that's a good idea then? Or do you still want to look for better?
[20:06] <newz2000> that'll work
[20:06] <MTecknology> we might still want a file the javascript can scan to see if it's been released or not
[20:09] <MTecknology> I can easily make it so if the pointer is pointing at the same location as before then it won't pull new cache too
[20:11] <MTecknology> newz2000: is there any way you could send me a tarball of all the images and everything else for the current release?
[20:11] <newz2000> they're on that wiki page
[20:11] <newz2000> that's the best place to get them
[20:16] <MTecknology> I love launchpad bugs....
[20:17] <MTecknology> newz2000: Any chance you could make a pointer that points here? http://edge.launchpad.net/drupal-ubuntu-countdown/banners/jaunty/+download/countdown.tgz
[20:18] <MTecknology> I know it'll sit there because I just created it :P
[20:23] <newz2000> MTecknology: I'd rather not
[20:23] <newz2000> the reason is because I want to make sure we have a solid qa process before we put a redirect in from ubuntu.com
[20:24] <MTecknology> good point
[20:25] <MTecknology> what is one redirect that you have setup?
[20:25] <newz2000> MTecknology: what do you mean?
[20:26] <MTecknology> Do you have any redirects currently?
[20:26] <MTecknology> I just wanted to see what curl showed me about them
[20:26] <newz2000> ok, sure
[20:26] <newz2000> let me find one
[20:27] <newz2000> http://www.ubuntu.com/cloud
[20:29] <MTecknology> interesting
[20:31] <MTecknology> So I'll probably pull the redirect and see if it points at a new location fromt eh one saved in the db and if it is different then pull a new copy
[20:31] <MTecknology> Thanks :D