You can kludge on encryption in the pipeline:

http://sourceforge.net/project...

If they told everybody "your info was hacked" while they hadn't cleaned it up yet, a bunch of folks would have logged on and changed their passwords, immediately exposing the NEW ones. You clean up first, then you engage the PR folks.

As you discovered, advertising is only worthwhile if you are reaching the proper audience. Adwords should be a last-resort as it is way too easy to cast a very wide net and takes quite a bit of effort to tweak.

From your description you had the 'content network' enabled in Adwords, which is indeed a very easy way to waste your budget on useless visitors. The content network means that your ads could be shown on all the sites out there that use Adsense (I think you mixed Adsense and Adwords: Adwords is Googles ad-delivery platform and costs money, Adsense shows those ads on non-Google websites and allows the website to earn money).

Stick to the 'search network' (Google.com and related sites) only and limit your keywords to only the most relevant ones. Google will automatically broaden searches, so learn how to adjust your keywords to limit their range and use negative keywords to avoid matches on irrelevant searches.

Also, I've often seen Google mentioning that I should set the cost-per-click higher as my ads weren't showing, but they were showing regardless.

So for those of you looking to use Adwords: start off slowly and know that just as you are tweaking your keywords and prices, so does Google tweak their algorithms to get the most out of advertisers. You don't become a megacorp by giving out free lunches.

While individual components are being published as GPLv3, they're requesting, and getting, written permission from some contributors to re-publish the code under alternative licenses, at Canonical's whim. That is releasing licensing rights to someone else. Even if Canonical proves trustworthy (and they've not, due to their strange browser collection data practices), that goes far beyond most open source or freeware licenses.

Although I enjoy slinging mud, copyright assignments and contribution agreements are commonplace when contributing to larger free/open source projects.

Transferring copyright for example to GNU is mandatory when contributing, gives the project the flexibility to relicense in case an upgrade is in order (like GPLv2->GPLv3) and avoids having to hunt down all individual contributors in case a change in license is required. Such agreements are in place with Apache and Mozilla too.

All things considered, GNU would indeed be more trustworthy in my book than Canonical (if only because GNU doesn't have a commercial motive) but regardless when an "entity" does the bulk of the work I think it's fair to allow them the flexibility to relicense when contributing.

It is a different situation when the owning "entity" drops the ball and the community does the bulk of the work, but then the option to fork is always open. LibreOffice serves as a nice reminder that being able to relicense doesn't mean much if the community decides to fork and move on.

I can even think how to comment on the new beta. If you dont get how important this comment are - how this should not even have got to Beta without the comments working. Than /. is doomed.

Wow - these games are never even on my radar. Any FreeCIV like games for android ? (Apart from FreeCiv its self)

Wow - looking really good. Is opensource hardware on the way ?

Good, but why not pay for more development of the GNU/Linux version.

Its not actual lag so much as poor UI choices that are perceived as lag at this point in my opinion, but I most certainly can 'feel' the lag.

We're currently finishing up a fairly simple music app for Android with a couple of fun features.

In the beginning we were fussing around a lot with the Android UI and Audio APIs, as the lag when a user pressed a button widget until audio was played was very noticeable, we couldn't get rid of it. After hitting a brick wall we simply started from scratch using only a blank canvas, manually drawing buttons and handling events and the like and things worked perfectly.

So I the lag we (and probably everyone else) experiences has little to do with Dalvik but everything to do with the Android UI widget event handling, it causes unresponsive UIs.

I never noticed it before but now I see it all over the place. The only apps that don't have it are games and apps like ours who sidestep most of the Android Widget/Event API and go the manual route.

Dyslexic and un-coordinated, but stubborn enough to learn juggling. Even got up to 5 balls at one point. Once you learn, it is engrained. Can still juggle whilst drunk.

www.xrdp.org
Works very well.

Recently even the Kernel developers got caught into this mess, having Linus calling some maintainer of UDEV a lier.
Google UDEV and systemd to see the whole gory mess, and mind my words, this is only the beginning of the troubles in GNU/Linux land.

People disagree with each other and call each other names on the internet, wow what an eye-opener.

If you think this is bad you might want to look back a few years on lkml, or any other major open source project. Given the ego's and the ability to instantly spout a reply from the top of your head it's a miracle there are intelligent discussions at all on the Internet.

Disagreements and differing interests go all the way back and are one of the reasons we have such a huge eco-system of Free software. IMHO without them we still would be waiting for HURD.