Laplace’s Demon [coming home!]

A new online seminar is starting this week, called Laplace’s Demon [after too much immersion in His Dark Materials, lately, ather than Unix coding, I first wrote daemon!] and concerned with Bayesian Machine Learning at Scale. Run by Criteo in Paris (hence the Laplace filiation, I presume!). Here is the motivational blurb from their webpage

Machine learning is changing the world we live in at a break neck pace. From image recognition and generation, to the deployment of recommender systems, it seems to be breaking new ground constantly and influencing almost every aspect of our lives. In this seminar series we ask distinguished speakers to comment on what role Bayesian statistics and Bayesian machine learning have in this rapidly changing landscape. Do we need to optimally process information or borrow strength in the big data era? Are philosophical concepts such as coherence and the likelihood principle relevant when you are running a large scale recommender system? Are variational approximations, MCMC or EP appropriate in a production environment? Can I use the propensity score and call myself a Bayesian? How can I elicit a prior over a massive dataset? Is Bayes a reasonable theory of how to be perfect but a hopeless theory of how to be good? Do we need Bayes when we can just A/B test? What combinations of pragmatism and idealism can be used to deploy Bayesian machine learning in a large scale live system? We ask Bayesian believers, Bayesian pragmatists and Bayesian skeptics to comment on all of these subjects and more.

The seminar takes places on the second Wednesday of the month, at 5pm (GMT+2) starting ill-fatedly with myself on ABC-Gibbs this very Wednesday (13 May 2020), followed by Aki Vehtari, John Ormerod, Nicolas Chopin, François Caron, Pierre Latouche, Victor Elvira, Sara Filippi, and Chris Oates. (I think my very first webinar was a presentation at the Deutsche Bank, New York, I gave from CREST videoconference room from 8pm till midnight after my trip was cancelled when the Twin Towers got destroyed, on 07 September 2001…)

the end of travel?

First came the bad news that travelling [by plane] with any electronic device larger than a small cell phone would be prohibited unless the device was checked in. I first thought this was a sort of weird protectionism for American airlines, since only Middle-East carriers seem to be impacted at the moment, but there are serious hints this could soon be extended to all flights to the USA. And to the UK. And likely to about every flight in a near future. That is fairly annoying and more, not only because it hugely reduces the ability to work on a plane [unless carrying paper printouts of every paper one wanted to read or review during a long flight, until this is as well considered as a fire hazard!], but mostly because quite likely these electronic devices in checked-in bags will be damaged or stolen. So the only convenient [least inconvenient] solution may be to stop travelling with laptops and operate on remote or cheap disposable machines from whenever one is. Since I presume even the smallest PCs like Raspberry Pi’s will be banned at some point. The only good news are for computer companies. And book sellers maybe.On top of this, I learned that the UK has [again!] copied the US in requiring visitors and even its own citizens to open devices to Border or Customs officers. And to disclose social media identities and associated passwords. A British Human Rights activist was recently arrested at London Heathrow for refusing to do so. And I read today that divulging those media IDs are now optional on the visa waiver program and possibly soon to be compulsory. Which sounds insane as a way to fight terrorism as it is obvious to set parallel accounts. And yet another travel nuisance.

At some point in the past, I had mused that we would soon be forced to travel with no personal item, maybe not even our own clothes, but a uniform provided by the airline. With luggages on a drone plane following by a safe margin. The invasion of privacy now contemplated and soon implemented by states that do not any longer seem concerned with Human Right goes way beyond this fantasy scenario. If travelling between countries means a massive reduction of one’s rights and dignity [which is already quite reduced under the current conditions], travelling may soon become a rare occurrence…

the vim cheat sheet

Ubuntu issues

It may be that weekends are the wrong time to tamper with computer OS… Last Sunday, I noticed my Bluetooth icon had a “turn off” option and since I only use Bluetooth for my remote keyboard and mouse when in Warwick, I turned it off, thinking I would turn it on again next week. This alas led to a series of problems, maybe as a coincidence since I also updated the Kubuntu 14.04 system over the weekend.

1. I cannot turn Bluetooth on again! My keyboard and mouse are no longer recognised or detected. No Bluetooth adapter is found by the system setting. Similarly, sudo modprobe bluetooth shows nothing. I have installed a new interface called Blueman but to no avail. The fix suggested on forums to run rfkill unblock bluetooth does not work either… Actually rfkill list all only returns the wireless device. Which is working fine.
2. My webcam vanished as well. It was working fine before the weekend.
3. Accessing some webpages, including all New York Times articles, now takes forever on Firefox! If less on Chrome.

Is this a curse of sorts?!

As an aside, I also found this week that I cannot update Adobe reader from version 9 to version 11, as Adobe does not support Linux versions any more… Another bummer. If one wants to stick to acrobat.

Update [03/02]

Thanks to Ingmar and Thomas, I got  both my problems solved! The Bluetooth restarted after I shut down my unplugged computer, in connection with an USB over-current protection. And Thomas figured out my keyboard had a key to turn the webcam off and on, key that I had pressed when trying to restart the Bluetooth device. Et voilà!

Glibc GHOST vulnerability

Just heard about a security vulnerability on Linux machines running Red Hat version 5 to 7, Ubuntu 10.04 and 12.04, Debian version 7, Fedora versions 19 and older, and SUSE versions 11 and older. The vulnerability occurs through a buffer overflow from some functions in the C library Glibc, which allows for a remote code to execute, and the fix to the problem is indicated on that NixCRaft webpage. (It is also possible to run the GHOST C code if you want to live dangerously!)