This post relates to creating an Android application with Facebook support (via phonegap-facebook-plugin using Cordova 3.5 and, specifically, without Eclipse. Most existing documentation expects you to spin up Eclipse to link the Facebook libraries – but, we’re using an automated build system with Grunt so that’s not a possibility.
Firstly – the steps to get it working:
- Add the Cordova Facebook plugin:
cordova plugin add https://github.com/phonegap/phonegap-facebook-plugin \
--variable APP_NAME="Test App"
platforms/android/project.properties and add:
where n is the next available reference index. Also note the
target parameter here as you’ll need it next:
- Update the Android project for the plugin:
android update project --target android-19 -p .
android-19 should match the
target parameter from above.
- Prepare and build your application:
cordova prepare android
cordova compile android
Our Taoiseach – who cannot seam to string a coherent sentence together most of the time – said, if you can parse it, the following of Alan Shatter’s donation:
“I think nobody can complain about the benefit that the children who are in the care, the subject of attention from Jack and Jill, nobody can complain about it.”
He was of course referring to Alan Shatter donating the €70,000 severance pay he is due to the Jack and Jill foundation.
What’s effectively happening here is that Alan Shatter, a member of the governing party and a cabinet minister until recently, is effectively saying that he doesn’t trust his own partners in Government to spend this money more wisely than he can.
Typical of Shatter’s arrogance. And a damning critique of Kenny.
Posted in Politics
At Open Solutions, we tend to undertake a lot of fixed price contracts to develop web applications. In fact, clients usually insist on fixed price contracts as they want to know in advance what the bill will be.
However, fixed price contracts have big negatives for both parties:
- for the client, a fixed price contract can often limit them to their earliest ideas. Now, as a service provider, we want to be flexible and so we’re happy to chop and change as a project develops. But, this leads to:
- for the service provider, if change and revision requests are not carefully managed agreed and billed for, the service provider could very quickly end up making a loss on the contract and thus find themselves in the position of funding their clients project!
To this end, we’ve recently been reviewing various web development contracts and have found some nice inspiration for basing our own on.
Following the success of Killer Contract, Andy wrote a plain language NDA (also available as a Gist).
The Court of Justice of the European Union today declared the Data Retention Directive invalid in a joint case brought by Digital Rights Ireland and an Austrian group. This is a great win by privacy advocates against a law that was over reaching, uncontained and unsafe. The courts own press release is a short three page read but some of the key elements include (all emphasis theirs):
- the data “may provide very precise information on the private lives of the persons whose data are retained, such as the habits of everyday life, permanent or temporary places of residence, daily or other movements, activities carried out, social relationships and the social environments frequented”;
- “the directive interferes in a particularly serious manner with the fundamental rights to respect for private life and to the protection of personal data“
- “the directive covers, in a generalised manner, all individuals, all means of electronic communication and all traffic data without any differentiation, limitation or exception being made in the light of the objective of fighting against serious crime”
- “the directive fails to lay down any objective criterion which would ensure that the competent national authorities have access to the data and can use them only for the purposes of prevention, detection or criminal prosecutions concerning offences that … may be considered to be sufficiently serious to justify such an interference” and “the directive does not lay down substantive and procedural conditions under which the competent national authorities may have access to the data and subsequently use them”
- “the directive does not provide for sufficient safeguards to ensure effective protection of the data against the risk of abuse and against any unlawful access and use of the data.”
- and, shockingly (if none of the above was shocking enought), “the directive does not require that the data be retained within the EU“.
This is indeed a good day for digital rights, privacy rights and common sense. We all owe a debt of gratitude to the volunteers at Digital Rights Ireland.
I spent the first few days of St Patrick’s week last month in Leeds at the first of the two annual Euro-IX conferences on behalf of INEX. Trefor Davies, of trefor.net, organised a series of articles called Peering Week on his blog to coincide with it:
During Peering Week we have had 18 excellent contributions from some of the people who run the internet in Europe. This might sound dramatic especially considering that the internet is made up of sixty or seventy thousand Autonomous Networks. The contributors this week run Internet Exchanges where a greats many of these networks connect to each other.
My contribution was about our IXP management system called IXP Manager – co-written by myself and Nick Hilliard for INEX. This tool is now being used to manage two IXPs in the UK, at least five more across Europe, a couple that we know about in the US and it is now the de facto choice for IXPs in Africa and Asia – where we are working with ISOC.
You can read the full article on Tref’s blog here: INEX’s IXP Manager – tools to help manage an Internet Exchange.
I’m glad to say that the good folks at Euro-IX helped ensure I wasn’t too homesick on St. Patricks’s Day – as the days proceedings wrapped up, we were greeted by:
I arrived to work this morning to find that the Heartbleed Bug happened.
This is one of the biggest security issues to crop up in a long time – allowing the data normally protected by TLS/SSL to be compromised. This is the kind of data that normally passes securely between clients and protected websites, email services, instant messaging, etc.
Upgrade all your systems now. This is where my well planned day went.
Be sure to restart all services that use OpenSSL (or reboot your servers). A useful command [source] for this post-upgrade is:
grep -l 'libssl.*deleted' /proc/*/maps | tr -cd 0-9\\n | xargs -r ps u
A useful Python script for testing your web servers can be found in this Gist. NB: it’s not just web servers affected – any services with SSL/TLS may be affected.