Henri Bergius - Politics

MicroFlo and IoT: measuring air quality

henri.bergius@iki.fi (Henri Bergius) — Mon, 26 Feb 2018 00:00:00 +0000

Fine particulate matter is a serious issue in many cities around the world. In Europe, it is estimated to cause 400.000 premature deaths per year. European Union has published standards on the matter, and warned several countries that haven’t been able to reach the safe limits.

Germany saw the highest number of deaths attributable to all air pollution sources, at 80,767. It was followed by the United Kingdom (64,351) and France (63,798). These are also the most populated countries in Europe. (source: DW)

The associated health issues don’t come cheap: 20 billion euros per year on health costs alone.

“To reduce this figure we need member states to comply with the emissions limits which they have agreed to,” Schinas said. “If this is not the case the Commission as guardian of the (founding EU) treaty will have to take appropriate action,” he added. (source: phys.org)

One part of solving this issue is better data. Government-run measurement stations are quite sparse, and — in some countries — their published results can be unreliable. To solve this, Open Knowledge Foundation Germany started the luftdaten.info project to crowdsource air pollution data around the world.

Last saturday we hosted a luftdaten.info workshop at c-base, and used the opportunity to build and deploy some particulate matter sensors. While luftdaten.info has a great build guide and we used their parts list, we decided to go with a custom firmware built with MicroFlo and integrated with the existing IoT network at c-base.

MicroFlo on ESP8266

MicroFlo is a flow-based programming runtime targeting microcontrollers. Just like NoFlo graphs run inside a browser or Node.js, the MicroFlo graphs run on an Arduino or other compatible device. The result of a MicroFlo build is a firmware that can be flashed on a microcontroller, and which can be live-programmed using tools like Flowhub.

ESP8266 is an Arduino-compatible microcontroller with integrated WiFi chip. This means any sensors or actuators on the device can easily connect to other systems, like we do with lots of different sensors already at c-base.

MicroFlo recently added a feature where Wifi-enabled MicroFlo devices can automatically connect with a MQTT message queue and expose their in/outports as queues there. This makes MicroFlo on an ESP8266 a fully-qualified MsgFlo participant.

Building the firmware

We wanted to build a firmware that would periodically read both the DHT22 temperature and humidity sensor, and the SDS011 fine particulate sensor, even out the readings with a running median, and then send the values out at a specified interval. MicroFlo’s core library already provided most of the building blocks, but we had to write custom components for dealing with the sensor hardware.

Thankfully Arduino libraries existed for both sensors, and this was just a matter of wrapping those to the MicroFlo component interface.

After the components were done, we could build the firmware as a Flowhub graph:

To verify the build we enabled Travis CI where we build the firmware both against the MicroFlo Arduino and Linux targets. The Arduino one is there to verify that the build works with all the required libraries, and the Linux build we can use for test automation with fbp-spec.

To flash the actual devices you need the Arduino IDE and Node.js. Then use MicroFlo to generate the .ino file, and flash that to the device with the IDE. WiFi and MQTT settings can be tweaked in the secrets.h and config.h files.

Sensor deployment

The recommended weatherproofing solution for these sensors is quite straightforward: place the hardware in a piece of drainage pipe with the ends turned downwards.

Since we had two sensors, we decided to install one in the patio, and the other in the c-base main hall:

Working with the sensor data

Once the sensor devices had been flashed, they became available in our MsgFlo setup and could be connected with other systems:

In our case, we wanted to do two things with the data:

Log it in the c-base telemetry system to be visualized with NASA OpenMCT
Submit the data from the outdoor sensor to the luftdaten.info database

The first one was just a matter of adding couple of configuration lines to our OpenMCT server. For the latter, I built a simple Python component.

Our sensors have been tracking for a couple of days now. The public data can be seen in the madavi service:

We’ve submitted our sensor for inclusion in the luftdaten.info database, and hopefully soon there will be another covered area in the Berlin air quality map:

If you’d like to build your own air quality sensor, the instructions on luftdaten.info are pretty comperehensive. Get the parts from your local electronics store or AliExpress, connect them together, flash the firmware, and be part of the public effort to track and improve air quality!

Our MicroFlo firmware is a great alternative if you want to do further analysis of the data yourself, or simply want to get the data on MQTT.

Bitcoin as a Medium of Exchange

henri.bergius@iki.fi (Henri Bergius) — Thu, 28 Nov 2013 00:00:00 +0000

Bitcoin — the decentralized digital currency — has been making a lot of headlines lately. Much of this is driven by the current investment boom around it that has raised the exchange rates over the 1000 USD mark. But really, looking at Bitcoin as a medium for currency or asset speculation is a bad idea. Instead, we should see it purely as a medium of exchange.

Not a great holder of value

Much of the press stories about Bitcoin see it as a speculative investment free of currency manipulation by central banks. By its nature, it is a deflationary currency, given that the global supply of Bitcoins is capped. As long as there is interest in Bitcoin, it means the prices are bound to go up. But at the same time, this is a threat to the currency. Deflation disincentivizes people from spending their money, as tomorrow the value is likely to be higher.

This is a big difference to fiat currencies where central banks generally act to ensure that there is a little bit of inflation, giving people incentives to spend, invest, and keep the economy running.

Traditional currencies are given a value by the fact that there is a government requiring taxes to be paid in them. This creates a demand in the currency, as people have to acquire units of that currency somehow, usually by selling goods and services. So, the value of a currency is built on the power of a state to tax its subjects in that currency.

The other traditional holder of value, gold, also differs from Bitcoins in the sense that at least you can make some useful things out of it.

In contrast, the value of Bitcoin without an economy backing it up is exactly zero. Without an active network of miners, and business transactions that create a demand for them, there is not much you could do with a Bitcoin.

Given this setting, Bitcoin as a investment mechanism resembles a ponzi scheme where people make speculative investments in them in hopes of being able to pass them on to the next fool when the prices go up.

This is obviously not sustainable in the long term. But luckily there are things you can do with Bitcoin that still make them interesting if you deal with them as a medium of exchange and not a long-term holder of value.

Great tool for conducting transactions

Now that we’ve established that Bitcoins are not the best thing to put your life savings into, or to stash under your mattress, what is it exactly that makes them interesting?

Mobile money

Bitcoin is a way of making transactions quickly, safely, and without middlemen. A lot of the articles written about it compare it to gold, but in my view a much closer comparison is M-Pesa, the operator-driven mobile payment network that powers over 30% of the Kenyan economy.

M-Pesa on a phone, by Pixel Ballads

When you see people paying with their mobile phones in a African street market, you know they’ve leapfrogged us in technology.

Bitcoin has the exactly same advantages as M-Pesa: you can send it to anywhere with minimal costs and delays, you can keep it on your phone, and anybody can ask for a payment through it. Unlike M-Pesa, Bitcoin is truly decentralized and doesn’t rely on a mobile operator to act as the “central bank”.

Unlike M-Pesa, Bitcoin currently requires an internet-connected smartphone with a wallet application. This limits its usefulness in the world outside of the rich countries (though cheap Android phones are changing the situation). It would be a huge boost for mobile commerce with Bitcoins if there was a service that enabled paying and requesting Bitcoin over SMS.

The one to make Bitcoin work over SMS will be rich

Last summer I was talking with Joerg Patzer, the owner of Room 77, a restaurant in Berlin that has been one of the early adopters of Bitcoin. At the time about 10% of the his sales happened in Bitcoin, and the number has been constantly growing since. He told that he even pays some of his suppliers in Bitcoin, and only converts some of it to euros, solely because you can’t pay taxes in Bitcoin.

Patzer buys the beer for Room 77 from the nearby Rollberg brewery, owned and run by qualified brew and malt meister Wilko Bereit. He pays for the barrels with Bitcoins

Joerg also told me an interesting case where there was a group of tourists having a dinner in his restaurant. A friend of theirs that wasn’t able to make the trip insisted on paying the bill remotely from Israel. This is something that would be hard to do with the traditional credit cards or currencies. Paying in Bitcoin is quite straightforward:

He taps the amount he owes Room 77 into the virtual Bitcoin wallet on his Android phone and, aligning it with a code on the bar’s device, presses a button to process the payment. A theatrical “kerching” sound follows and Gallas is grinning from ear to ear. “It could hardly be easier,” he insisted.

Requesting a payment using Bitcoin Wallet for Android

Global currency for the internet

Map of global Bitcoin nodes

Requesting Bitcoins is as easy as providing a URL. This could be presented as a link on the web, or shared to mobile devices via QR Codes. For example, clicking this link on a device with a Bitcoin wallet would enable you to send me Bitcoins worth around 0.1 EUR (on today’s exchange rates). No need for dealing with payment gateways or complicated protocols.

Ease of paying, no middle men, minimal transaction fees, and no risk of chargebacks make a lot of interesting business scenarios possible online. Consider for example micropayments for online content. This is something that would make online publishing viable without the current ad-driven models, but has been held back by the risks and costs associated with credit card payments. Wider adoption of Bitcoin would suddenly make this a very realistic way of asking for money for the things you do online.

Other clever uses

Since Bitcoins can be exchanged in miniscule amounts, and there is a public record kept on each transaction, they enable all kinds of new use cases.

One such service that I ran into yesterday is Proof of Existence, a tool for storing the fact that you were in possession of a document at a given time, and that it hasn’t been revised since based on microtransactions stored in the Bitcoin block chain. This is a mechanism known as trusted timestamping that could be useful for things we currently utilize notaries for. The Hacker News thread on this listed some interesting use cases, like verifying scientific priority on new inventions, i.e. that you had written a document describing a new invention at a given time even if you publish it only later.

We could also use Bitcoin for solving the spam problem. Emails could be “stamped” with a Bitcoin microtransaction, and email servers could be configured to reject messages that don’t have a valid payment attached to them. This would enable bringing decentralization back to the internet as we could again use distributed systems like email and XMPP without having to resort to the walled gardens like Facebook to keep them spammers away.

Another interesting approach was to use Bitcoin transactions for making bets.

How to get started

A good way to get started with Bitcoin is to read Wired’s Bitcoin survival guide or the materials available on Bitcoins.com. Install a Bitcoin wallet application on your mobile device. Then get some Bitcoin either by buying locally, from an online exchange or by selling goods or services for Bitcoin.

This is all you need to get going. Now you just need to find a way to spend them, for example in online shops, by buying domains, or in shops and restaurants that accept them, like many do in my neighborhood.

Disclaimer: I’m a programmer, not an economist. There are better people to take investment advice from. I do hold a little bit of Bitcoin, giving me some vested interest in the matter. Not the kind of amount that would make it an investment, but just the right amount for being able to buy a few nice dinners, especially at the Berlin prices. Generally, I try to keep the amount I have in BTC low enough to be equivalent of what I might be comfortable with carrying in cash.

Google Glass and the fear of the future

henri.bergius@iki.fi (Henri Bergius) — Fri, 22 Mar 2013 00:00:00 +0000

Google Glass is coming this year, a wearable display that can keep you connected at all the times and supply information and instructions when you need them. And it can record video or take pictures of whatever you see, when you want it to.

The privacy scare

Much of the Glass marketing focuses on the camera aspect, as does the criticism and fearmongering around it. Some feel that the device would bring about an era of ubiquitous surveillance and loss of privacy. Some even label these people as Luddites:

StopTheCyborgs and other Neo-Luddite groups make some pretty compelling arguments against AR, including the credible threat that people could be recorded at any time without their knowledge or permission. Nobody could ever consider conversation in the presence of Google Glass wearers completely private. Any entity that could tap into and process all the information from Google Glass on a minute-to-minute basis could track anyone or any conversation anywhere near the wearers. Google Glass may well begin the destruction of our current definitions of privacy.

The mislabeling aside (the historical Luddites were more concerned about machinery taking away their jobs, as they and globalization together eventually did), the criticism is generally baseless.

We live in cities filled with thousands of surveillance cameras monitoring our every move. We pay for our groceries with credit cards that leave a mark on everything you bought — when, and where — into a database. We carry smartphones that are constantly reporting their location back to the operator. We post our private pictures and current activities to social networks. There is very little privacy left. If you’d see how detailed information law enforcement can get out of our every movement from your operator, you’d know that too.

In a world where a hidden, pencil-shaped spy camera can be bought for about 30$, is a very obviously visible Google Glass device really the biggest risk to privacy? And yet, places are banning them already, a lot before they actually hit the market.

This is the future

The anti-Glass movement has a benefit. While not exactly a flying car, it is yet another sign that we’re living in the future that science fiction authors envisioned. I mean, consider the fact that there is A movement to ban cyborgs.

They even sell stickers.

Consider the possibilities

Since the privacy battle is already lost, shouldn’t we instead focus on the possibilities they can bring? While Google has shown very little of the capabilities of the Glass software apart from videoconferencing and making web searches, various books can provide clues.

Many of them describe a world where you can share with anybody what you see with your own eyes, or access any information without having to hold a bulky device.

It is a little hard to provide good context of the use cases from the books just by short snippets, but here are some. Feel free to provide your own in the comments.

In Daniel Suarez’s Daemon series, Glass-like devices are used for connecting and coordinating a full economy, called the Darknet. Here is a view of an office with augmented reality displays and motion controls:

The center of the room looked to be a staging area, bustling with your people, all wearing eyewear and gloves. To the side was a raised platformn lined with office chairs where a dozen people were grabbing, pulling, and pushing at invisible objects in the air. They were all speaking to unseen people, as though it were a call center.

I could easily imagine manipulating my flow based programs in this way.

The Daemon series also feature other Google products, like driverless cars and an augmented reality game much like Ingress.

Vernor Vinge’s Rainbows End has everybody using augmented reality glasses as an everyday matter. They even change how you see a city like Barcelona:

Vaz strolled to the stone barrier and looked down. If he blocked out all the tourism fantasy [augmented by the Glass], he could see the freight harbor almost two hundred meters below and a kilometer away. The place was an immensity of freight containers rambling this way and that, chaos. If he invoked his government powers, he could see the flow of carge, even see the security certificates…

And of course people interact with the augmented reality projections of others just like they were present:

Even when her friends were gone physically, they were often still around, invisible presences [without the Glass] like Robert’s doctors. Miri walked around the backyard talking and arguing with nobody—a parody of all the cellphone discourtesy that Robert remembered

For the less pleasant view of something like Glass, Neal Stephenson’s Snow Crash focuses on the surveillance aspects, with people using AR displays being called Gargoyles:

Gargoyles are no fun to talk to. They never finish a sentence. They are adrift in a laser-drawn world, scanning retinas in all directions, doing background checks on everyone within a thousand yards, seeing everything in visual light, infrared, millimeter-wave radar, and ultrasound all at once. You think they’re talking to you, but they’re actually poring over the credit record of some stranger on the other side of the room, or identifying the make and model of airplanes flying overhead.

Then again, talking with a Facebook addict can already be a lot like that.

How this will play out

If the glass does what people want it to do, it will become popular.

Just like we’ve taken smartphones and tablets into our lives and homes, eventually we will live in a world where you will feel naked if you step out of your home door without the glass on. How am I supposed to connect and communicate now?

I’d love to have Glass, even if it is clunky in the beginning.

Wearable computing is one of the possible trajectories we’re going with, from room-sized mainframes to desk-bound personal computers to these amazing small slabs of glass and antennas we now carry in our pockets.

Just like with smart spaces, or tablets many years ago, I’m keen to explore the new interaction possibilities.

Sovereignty into the fabric of the Internet

henri.bergius@iki.fi (Henri Bergius) — Mon, 31 Oct 2011 00:00:00 +0000

Mozilla’s mission is to “build user sovereignty into the fabric of the Internet.

—Mitchell Baker, in ExtremeTech article

Where is the future for openness in mobile?

henri.bergius@iki.fi (Henri Bergius) — Mon, 03 Oct 2011 00:00:00 +0000

These are tough times for fans of open mobile environments. Android is less and less open, Symbian was closed again, HP stopped making webOS devices, and now Intel abandoned MeeGo to work with Samsung and operators instead. So, what is the community to do?

One option is to follow the lead of the big companies, hoping that Tizen works, or that Google again sees the benefit of working with others in the open.

The other is to take the matters in our own hands. There is precedent for this. Much of early Linux activity came from the efforts of the community, not on the initiative of corporate interests. And there have been OpenMoko and Mer, the latter an attempt to make a fully open version of Nokia's Maemo environment, suspended when MeeGo promised to bring the same benefits.

Well, now Mer is back.

The goals for Mer align pretty well with what the community would need:

To be openly developed and openly governed as a meritocracy
That primary customers of the platform are device vendors - not end-users.
To provide a device manufacturer oriented structure, processes and tools: make life easy for them
To have a device oriented architecture
To be inclusive of technologies (such as MeeGo/Tizen/Qt/EFL/HTML5)
To innovate in the mobile OS space

There have also been some other invitations to new potential homes for the community, ranging from openSUSE to Debian.

It will be interesting to see how this works out. But whatever we as a community do, we should ensure we look at more than just licensing.

Embrace and extend

henri.bergius@iki.fi (Henri Bergius) — Sun, 11 Sep 2011 00:00:00 +0000

I’m getting worried about Google. Long one of the champions of the open web alongside Mozilla, the rise of social networking silos and the app economy seem to have scared them. And like any scared organism, they lash out.

Many of their plans to make web competitive against native development environments are good, there is indeed much to improve in the stack. But what I’m uneasy with is the unilateral way they go about it, preferring “big reveals” and post-facto standardization instead of the open conversation that built most of the Internet we have today. This is not the way to collaborate.

Consider some of their recent efforts:

SPDY, a protocol to replace HTTP which Web is built on. Currently only supported by Chrome, which uses it to talk to several Google services
Dart, their JavaScript-killer which recently surfaced through a leaked email
Microdata and Schema.org that seek to replace last ten years of semantic web development with a spec cooked up by couple of big vendors in secret

These - together with WebSQL, NaCl, WebM and WebP - mean that Google has active efforts to replace practically every layer of the web (except HTML itself) with something of their own design.

The way all of these were introduced bears strong reminders of how Microsoft tried to embrace, extend, and extinguish the web in late 90s. That period brought horrors like ActiveX and the awful, unkillable IE6. Though, for the sake of fairness, it also brought us XmlHttpRequest which was the enabler of the AJAX revolution.

Google’s new technologies may end up being beneficial for web developers, but they also threaten to fragment the platform. After all, as the competition in the “post-PC” space heats up, the competitors are unlikely to embrace Google’s extensions of the web stack. That would be a loss to all.

Brendan Eich, the original author of JavaScript comments on Hacker News:

So “Works best in Chrome” and even “Works only in Chrome” are new norms promulgated intentionally by Google. We see more of this fragmentation every day. As a user of Chrome and Firefox (and Safari), I find it painful to experience, never mind the political bad taste.

Ok, counter-arguments. What’s wrong with playing hardball to advance the web, you say? As my blog tries to explain, the standards process requires good social relations and philosophical balance among the participating competitors.

Google’s approach with Dart is thus pretty much all wrong and doomed to leave Dart in excellent yet non-standardized and non-interoperable implementation status. Dart is GBScript to NaCl/Pepper’s ActiveG.

Disclaimer: I’ve been a long-time fan of many of Google’s services, and have visited some of their offices a few times. I like the company. Which is exactly why I’m so concerned about this unilateral approach at standards. I am also involved in some standards processes through the IKS Project.

Openwashing

henri.bergius@iki.fi (Henri Bergius) — Thu, 05 May 2011 00:00:00 +0000

Somehow I had missed this term being coined:

The old "open vs. proprietary" debate is over and open won. As IT infrastructure moves to the cloud, openness is not just a priority for source code but for standards and APIs as well. Almost every vendor in the IT market now wants to position its products as "open." Vendors that don't have an open source product instead emphasize having a product that uses "open standards" or has an "open API."

"Openwashing" is a term derived from "greenwashing" to refer to dubious vendor claims about openness. Openwashing brings the old "open vs. proprietary" debate back into play - not as "which one is better" but as "which one is which?"

Especially Google seems to be doing this quite a bit. If you want to be open, work in the open. This is the only way to ensure acceptance and sustainability for your code.

Techno-optimism and free software

henri.bergius@iki.fi (Henri Bergius) — Wed, 04 May 2011 00:00:00 +0000

Cory Doctorow on Locus:

To understand techno-optimism, it’s useful to look at the free software movement, whose ideology and activism gave rise to the GNU/Linux operating system, the Android mobile operating system, the Firefox and Chrome browsers, the BSD Unix that lives underneath Mac OS X, the Apache web-server and many other web- and e-mail-servers and innumerable other technologies. Free software is technology that is intended to be understood, modified, improved, and distributed by its users.

Also about the threat that centralized social networks produce:

As a techno-optimist, I was heartened to see the role that networked technologies played in aiding activists in Iran, Egypt, Libya, Bahrain and other middle-eastern autocracies to coordinate with one another. But as a techno-pessimist, I was horrified to see activists making use of unsecured unfit systems like Facebook, which make it trivial for authorities to snoop on and unpick the structure of activist organizations.

The Universal Runtime

henri.bergius@iki.fi (Henri Bergius) — Wed, 09 Mar 2011 00:00:00 +0000

In the coming years another billion people will get online. They will do it with their smartphones instead of what we consider computers. And their experience will be quite different from ours when we initially started using the internet.

Despite its promises, it looks like the post-PC ecosystem will be a lot more restrictive than the PC one was even in the worst days of the wintel duopoly. For a while it looked like software freedom might be one of the cornerstones of the new world, but since then it has been shown that the tech giants Apple and Microsoft, together with the American content industry, will ensure that this new environment is more tightly locked down than anything we've seen before.

These companies will have a say on who gets to create something, who to distribute it, and who to use it. Users will be 'protected from themselves' by enabling these devices to run only code approved by the company. We've already seen that this approval can be declined, or even retroactively withdrawn on a whim, and on grounds more political than technical.

If we want to ensure digital freedoms for ourselves, and for the people only now reaching across the digital divide, we must act. We must find ways to enable creativity to happen on these new devices. We need to find ways to enable people to create, distribute and use any software on their phones, regardless of what locked-down ecosystem their mobile operator pushed them into.

Luckily there is one programming environment, one runtime that even the most restrictive players haven't had the courage to lock down: the web. Web browsers, coupled with the modern, fast JavaScript engines, could be the tool to build the next step of the free software revolution. We must embrace it.

JavaScript is already fairly prominent in free software development. The GNOME Shell has been largely written in it, Qt Quick builds on it, and most of the common JavaScript libraries are free software. There are even ways to run JS as a server or build your own desktop applications with it.

For those looking to get started with JavaScript, here are some useful resources:

Eloquent JavaScript is a free e-book that provides an introduction to the language. Read especially the chapter on functional programming
CommonJS is a specification for writing interoperable JS modules. There is a tutorial on writing modules that work both on the browser and the server
Backbone.js is a useful Model-View-Controller system for JavaScript. We use it with Midgard Create
For those who dislike the JS syntax, there is CoffeeScript that provides a cleaner way to write your code. It compiles to JavaScript much like Vala compiles to GObject-oriented C
Cloud9IDE provides a web-based IDE for JavaScript development. It integrates with Git repositories, and you can either run your own instance or use the hosted version
JSLint is a good way to check your code for hidden problems
The JavaScript Garden is also a good source of documentation

While there will never be a "one true language" to program in, JavaScript has the potential to be a big thing. And for writing and sharing software across platform boundaries, it may be the only way. It runs even on the most walled of gardens.

Finland's brand strategy builds on the ideas of free software

henri.bergius@iki.fi (Henri Bergius) — Thu, 25 Nov 2010 00:00:00 +0000

Finland's national brand strategy project released their report today on the Tehtävä Suomelle website. The basic idea is to promote the Finnish capability for getting things done, and the communal approach to problem solving.

I found the beginning of the Finland - It Works document particularly interesting:

"Just a hobby, won’t be big and professional" 25 Aug 91 20:57:08 Newsgroups: comp.os.minix

This statement sparked a revolution. The amateur computer programmer Linus Torvalds had come up with a way of enabling an unlimited number of people to work on the development of the same program source code. This was to prove to be a highly successful approach. Linux, which since then has evolved into a huge success, is one of the most significant open-source operating systems. The Internet would not be possible without a service infrastructure, which is currently largely based on Linux and open source.

Torvalds understood that a complex system, such as a global network, can only function if there are a large number of motivated individuals contributing to its development. This is expressed in another famous statement made by Torvalds: "Given enough eyeballs, any bugs are shallow". In other words, the difficulty of problems depends on the number of people involved in finding a solution.

Linux, which was created by Torvalds, and other open source systems combine the foremost virtues of Finnish functionality: nurturing the commons in a successful way, and the shrewd use of human resources. Thus it is probably no coincidence that the main impetus for open source came from Finland, from a country where functionality is the highest praise for almost anything.

I would imagine this is the first time a country uses FOSS philosophy as one of the building blocks for a national strategy.

If you have the time, go to the project website and read the materials. They seem to have some interesting suggestions on how to move Finland's public image forward.