[15:51] <sense> good afternoon
[16:40] <devildante> is it normal that the datetime indicator doesn't show?
[16:41] <gambs> devildante: Apparently.
[16:42] <gambs> Several people have mentioned that it's been stripped out.
[16:42] <gambs> (But, as I use indicator-complete, I hadn't noticed XD)
[16:43] <devildante> but I liked it :(
[16:43] <gambs> You can get it back.
[16:53] <devildante> gambs: installing -complete made it return! thanks :)
[16:54]  * devildante wonders why -complete is not default - they wouldn't have to bother with *two* indicator applets
[16:54] <gambs> Complete isn't default because the network indicator and datetime are ready fro primetime last I heard.
[16:55] <gambs> So, desktop will use the old clock applet still.
[16:57] <gambs> (For instance, my datetime indicator doesn't update what day it is on the calendar unless I restart my computer... So, it still says it's Saturday)
[16:59] <devildante> mmm... thanks gambs :)
[17:00] <gambs> No problem!
[20:20] <meebey> kenvandine: do you know if twitter finds it acceptable to ship the api key in source but not regular binary distribution (as hidden in binary content)
[20:21] <meebey> or dont they like if "forks" or different distros will use the same key
[20:21] <kenvandine> meebey, the compromise i came to them was separating the key from the source
[20:21] <kenvandine> by putting the key in packaging
[20:21] <meebey> kenvandine: even if the source is not the regular distribution? as its not python...
[20:22] <kenvandine> however, if anyone abuses it they will shut it down
[20:22] <meebey> hrmpf
[20:22] <kenvandine> they just don't want it to be very discovera ble
[20:22] <meebey> kenvandine: source isnt, it needs lots of skillz
[20:22] <kenvandine> if they disable the key, we need to get an update out with the new key
[20:22] <meebey> true
[20:23] <meebey> so better to allow to pass it at buildtime
[20:23] <meebey> without shipping it in the regular source
[20:23] <kenvandine> yeah... and frankly it is easier to go to dev.twitter.com and register a new app than to go digging in bzr for someone else's :)
[20:23] <kenvandine> but oh well... :)
[20:23] <meebey> yes
[20:23] <meebey> kind if stupid
[20:23] <meebey> s/if/of/
[20:24] <meebey> hm
[20:24] <kenvandine> yeah... they aren't really focused on our use case... desktop apps aren't the top of their priority stack
[20:24] <meebey> actually I have an idea
[20:24] <meebey> hrhr
[20:25] <meebey> I will include a default key that is replacable at buildtime
[20:25] <meebey> if it ever gets abused
[20:25] <kenvandine> yeah
[20:25] <meebey> distros can simply replace it
[20:25] <meebey> ^^
[20:25] <kenvandine> gwibber is doing that too now :)
[20:25] <kenvandine> yup
[20:25] <meebey> :)
[20:25] <kenvandine> we are including a default key that we don't care if it gets shutdown
[20:25] <meebey> yep
[20:25] <kenvandine> and provide an override mechanism for distros to use their own
[20:25] <meebey> do you use a differet name for that one or something?
[20:26] <kenvandine> same variable names
[20:26] <kenvandine> but they come from a different file
[20:26] <kenvandine> which isn't included in gwibber source
[20:26] <kenvandine> but in the package
[20:26] <kenvandine> if that file exists, it uses it for overrides
[20:26] <kenvandine> so you can override any default setting
[20:26] <kenvandine> not just the key
[20:28] <meebey> kenvandine: ic
[20:28] <meebey> kenvandine: with name I meant the software name though in the twitter app db
[20:28] <kenvandine> oh... that is tied to the key
[20:28] <meebey> Gwibber Official, Gwibber FOSS, etc
[20:28] <kenvandine> so nothing in code
[20:28] <meebey> or just Gwibber for all?
[20:29] <meebey> or shows the name in the tweet though
[20:29] <meebey> thats why I ask
[20:29] <kenvandine> it shows the name associated with the key
[20:29] <kenvandine> so for Ubuntu, it now says "from Ubuntu"
[20:29] <kenvandine> instead of from Gwibber
[20:29] <meebey> hm ic
[20:30] <meebey> Gwibber (Ubuntu) would have been nicer probably
[20:30] <meebey> ^^
[20:30] <kenvandine> that is up to the app owner on twitter
[20:30] <meebey> I think I will use Smuxi (default key in source), Smuxi Official, Smuxi ($Distro) if neeed someday
[20:31] <kenvandine> well the owner of the key controls that name, the app developer doesn't
[20:31] <meebey> I know
[20:31] <meebey> as I upstream and downstream though
[20:31] <meebey> ^^
[20:31] <meebey> +am
[20:31] <kenvandine> true
[20:31] <meebey> I do control that
[20:31] <kenvandine> but if fedora packages it then they control it
[20:31] <kenvandine> for example
[20:32] <meebey> indeed
[20:32] <meebey> thats why I want to give good example :)
[20:32] <kenvandine> :)
[20:32] <meebey> so --engine-twitter-engine needs an optional parameter, righto
[20:32] <meebey> errr --enable-twitter-engine
[20:33] <meebey> kenvandine: I just made indicate and notify deps optional for the backwards distros
[20:33] <kenvandine> cool
[20:33] <meebey> say non-debian and non-ubuntu ones
[20:33] <meebey> ^^
[20:33] <meebey> notify-sharp seems to be more spread though
[20:34] <meebey> do you know if inidicate is available elsewhere?
[20:34] <meebey> I would prefere makign the default to "yes" and not "auto"
[20:34] <meebey> but only if the major distros ship it
[20:34] <kenvandine> i know foresight does
[20:34] <meebey> kenvandine: is gwibber also using them as optional builddeps?
[20:34] <kenvandine> but not sure about others
[20:35] <kenvandine> yeah
[20:35] <kenvandine> well optional runtime
[20:35] <meebey> ah ic
[20:35]  * kenvandine hugs python
[20:35] <kenvandine> :)
[20:35] <meebey> its doable in C# too but its nasty, needs black magic
[20:36] <meebey> kenvandine: will gwibber break in the 1st sep?
[20:36] <meebey> s/in/on/
[20:36] <kenvandine> if this update isn't out yet
[20:36] <kenvandine> well sort of... it'll stop working with twitter
[20:36] <meebey> hehe, I am not alone then...
[20:36] <meebey> yeah I meant the twitter support of it
[20:36] <kenvandine> lots of people are behind..
[20:37] <meebey> this has good and bad sides
[20:37] <meebey> good is that most crappy apps will now simply die, finally
[20:37] <kenvandine> i think pino won't work either
[20:37] <meebey> bad is that is puts so much stress on us
[20:37] <kenvandine> yeah, and i need to backport this for lucid and get an SRU
[20:37] <kenvandine> :/
[20:38] <meebey> the JSON parser that Twitterizer uses (the twitter lib that smuxi uses) has a bug currently, making it a showstopper :/
[20:38] <meebey> kenvandine: thanks for the nice chat! going back to hackery...
[20:40] <kenvandine> np
[20:40] <kenvandine> good luck :)
[21:58] <foo123> I don't suppose I can get support for using libindicator here? I'm having a signal problem
[22:27] <foo123> I am using pygtk and appindicator and it appears that I am not receiving most signals. I would like a signal that I can use to determine when the indicator menu is being displayed.