Did you ever reflect about your reaction if you were to be jailed? Well, why would you go to jail?

What if your work got you to jail? Would you be mad if a court mistakenly declared you guilty of fraud? And who exactly would you be mad at, if you and your colleagues were mistakenly declared guilty by a court relying on defective software?

Here's hoping few people will answer that last question

According to Associated Press, Germans should be able to store their identity on PC-s this Fall!

Meanwhile, in Canada... the Federal government asks citizens for ideas to design a recovery plan. Do I really to fill a survey so someone in the LPC realizes electronic identification matters in 2021? Come on, Canada! We don't need to wait until the USA or the UK has beaten us to get started!

In December, the Linux Foundation released a report on its 2020 FOSS Contributor Survey. The most important and discussed takeaway was weakness in security (Need to Increase Security). At the core of that finding is that section's very first paragraph, which starts as follows.

These figures are obviously eyebrow-raising. The flagrant error in the figure number right after in that same paragraph surely doesn't help trusting, so I checked. Unfortunately, the report gives no explanation at all about how these figures were computed. And I couldn't reproduce these figures interpreting survey data.

But my third surprise would be even greater. I checked what others were saying about the topic - and found nothing. Not because no one questioned or challenged, but because the Linux Foundation provides no means at all to report an issue in that report.

That is right. The report indicates it was updated to fix errors, but suggests no way to report remaining errors. And that's
just the tip of the iceberg; the Linux Foundation, in general, does not offer any system to track its issues. Nor does it even offer any forum to discuss such matters. Its tens of mailing lists are all project-specific. That, from an organization which suggests greater transparency, no further than in that very report… if FOSS is short on security, it sure isn't on irony!

The ultimate surprise would take a little longer. Having no other option, I questioned the foundation in the only possible way, via its contact form:

The form didn't even send me a copy of my message. But it said I would get a reply within 2 business days.

I have been waiting for 3 business weeks.

I will of course update this as soon as the Linux Foundation replies. But until the foundation is built on stronger foundations, none of its publications should be taken at face value.

This week I witnessed an exchange on KDE's community mailing list. Someone made a reasonable request, quite decently formulated. Someone else, who visibly didn't appreciate that request, sent a reply which could easily have sparked a heated debate.

Thankfully, one respected elder intervened before the discussion degenerated.

So far, this may seem boringly familiar to those into online social production projects. In fact, the problematic reply wasn't even particularly inflammatory.

What I found striking is that the diskussion didn't involve random people. All of the 3 previously mentioned participants master the discussion's language (English) and are recipients of Akademy Awards. In fact, as recipient of a 2013 Akademy Award, Eike Hein was one of the judges who awarded the problematic participant with his own award the following year. The problematic participant is neither particularly young, nor new to social production or even KDE, with over a decade of involvement in KDE. The most striking was to see that this fairly experienced kontributor, who was rhetorically but clearly complaining about excessive load, had−ironically−replied not even a ½-hour after the request.

But a small research showed that my surprise could be partially rooted in a cultural difference. French-speaking kids are taught to "turn their tongue 7 times" before speaking. But the Anglosphere having apparently no equivalent proverb, perhaps it is less surprising to see an adult New Zealander without such a notion. So I thought Hein's reaction could be specified.

The Art of Boringly Calm Discussion

While the following initially felt too childish to share, I remembered I developed my current habits through years of experience. So I thought sharing the more elaborate−although still obvious−following approach, applied to the context of online collaboration (on free software), could speed up that development for some readers.

I am not sharing my exact program, which−having to run on a ridiculously old host−required highly dirty micro-optimizations, but the pseudo-Java code for my generator of boring replies, hereby released in the public domain. Sometimes, the generator saves time by saving from having to write at all, but its main benefit is to improve communication quality.

import HumanEmulation.Feeling;
import HumanEmulation.Judgment;
import Life.*;
import Internet.Message;

// FIXME: Unlikely to build without --leniency=max

public class FingerSaver {
    public static void main(String args[] ) throws Exception {
        Message incoming = Message.getLatest();
        incoming.read();
        if (! incoming.replyWarranted()) {
            System.exit(Feeling.HAPPY);
        }
        if (incoming.isUrgent()) {
            incoming.processDirectly();
            System.exit(0);
        }

        Thread thought = new DeepThinker(incoming);
        thought.start();

        // If we use Thunderbird with XNote++, we could store quick ideas about what to reply as a note.
        String skeleton = thought.getFirstReplyIdeas();

        // Reply versions
        Message initialVersion = null, previousVersion = null, latestVersion = null;
        do {
            if (latestVersion != null) {
                previousVersion = latestVersion;
                if (initialVersion == null) {
                    initialVersion = latestVersion;
                }
            }

            Integer tongueTurns = 7;

            feeling = Feeling.getCurrent();
            tongueTurns = tongueTurns + feeling.getAnger();

            /* Increase quality proportionally to the number of readers
            Also reduce collision risk
            TODO: Make logarithmic rather than linear */
            tongueTurns *= Message.getPeopleInDiscussion();

            if (Message.isEmail()) {
                // We won't be able to delete or modify our message if we send it too fast, so better play safe.
                tongueTurns *= 2;
            }

            // Let our deep thinking thread do its magic while we're eating, showering, exercising, commuting, etc.
            thought.ponderForHours(tongueTurns);

            wait(); // It may take some more time before HumanEmulation wakes us up if we're busy or not feeling good.

            Array<Message> repliesFromOthers = incoming.getReplies();
            if (! skeleton.worthWriting(repliesFromOthers)) {
                throw new Exception("We're exceptionally smart; we managed to let someone else do the job!");
                Life.enjoy();
                if (Life.getFreeTime()) {
                    /* If we saved so much time that we're now feeling guilty about having some free time,
                    use it to attract new recruits in our team.
                    This should be easier now that our team has quality communication
                    and looks like a growth opportunity for prospects,
                    rather than an immature and overwork-frustrated crew. */
                    recruitNewColleagues();
                }
                Feeling.stress--;
                System.exit(Feeling.HAPPY);
            }

            incoming.read(); // WARNING: moving this out of the loop will NOT optimize!

            /* To be truly evil, if others already made some of our points, remember to thank them,
            to encourage them to keep doing our job in the future! */
            // We usually store a reply as a draft in an MUA.
            if (latestVersion == null) {
                latestVersion = incoming.generateReplyFromIdeas(skeleton, repliesFromOthers);
            } else {
                latestVersion.readCarefully();

                /* If the sender discussed a valid problem and it's necessary to discuss timeframes,
                we can use this opportunity to try enticing them to help
                mentioning that more *skilled* manpower would speed up. */
                latestVersion = incoming.reviewReply(latestVersion, repliesFromOthers);
            }
        } while (previousVersion == null || ! Judgment.areAlmostTheSame(previousVersion, latestVersion));
        Message reply = latestVersion;

        if (reply.getValueToReaders() < reply.getCostToRead()) {
            System.out.println("Aborting due to negative net value");
            System.exit(1);
        }

        /* We ended up having to reply anyway, but at least, if others replied first,
         we have less to write, and we let them do some research and practice their writing skills,
         so we get left with even less on our plate next time.

         And the best part is that with all these tongue turns, we're more likely replying during the weekend,
         which means it's more likely recipients will read us on a weekend and will have a cooler reaction,
         even if they're lacking FingerSaver! */
        reply.send();

        /* If we're lucky, our reply was exhaustive and boring.
         We won't need to answer follow-up questions or clarify/justify what we wrote.
         So we shouldn't be back here for a while, but play safe. */
        sleep(A_BIT);

        /* Wow, we managed to write an incredibly insightful reply,
         which makes us look much more brilliant than the stupid program we're using!
         With all the time we saved, we can integrate the people who will volunteer to help us.
         And in case these take some time to show up, while they're digesting the full extent of our genius,
         we can validate that our issue tracker properly reflects our load level,
         and if it's really urgent, call for help. */

        Feeling.stress--; // We won't have to defend having said something stupid.


        /* We're bad judges of our own emotivity, but we can at least see how much we improved
         to estimate the minimum emotivity we were under. */
        Float climateChangeReductionFactor =
                Judgment.getFlammability(initialVersion) / Judgment.getFlammability(latestVersion);

        /* In case our initial reaction turned out excessively inflammatory,
        adjust our system's balance between longevity and performance. */
        System.throttleByFactor(climateChangeReductionFactor);
    }
}
// TODO: Expand to help truly healing from burnout. At this point, this only aims to help with overwork.

4 crashes in 1 year
In this millennium, that's most likely the cost of a somewhat rushed software development. But in 1944, that was apparently the cost one could pay to survive war. And for a pilot to get a lifelong legacy, including a well-deserved nickname.
Thanks to the CBC for the incredible story of Reg "Crash" Harrison, and for relativizing my crashes

5 years ago, I started a dangerous boycott of Quebec's organ donation system. Thankfully, I am still alive, and did not kill anyone yet.

And more importantly, the chances my death won't kill anyone else are increasing, now that a new tissue and organ donation law went into effect in a neighbour province. Since January 18th, donation has been opt-out in Nova Scotia.

Unfortunately, that news taught me that this is a first in North America. This world may have a deadly addiction to egoism, yet according to CBC, there is already talk about following Nova Scotia's lead in another province, no other than Alberta.

Here's hoping Quebec can stop deifying individualism just like it is doing with the SARS crisis and show it has enough hearth not to finish last in this marathon.

Most religions appeared during history, but not recently. We do have accounts of how that happened, like the Bible, but it's not so clear who wrote what when, nor what exactly was written before time and translations altered the texts.

The birth of a third millennium religion constitutes a great opportunity to study how religions were designed and adopted. The Internet and all of today's technological means make its deities much clearer. Technology also gives many more high-quality records of how it spread. But analyzing these still requires skilled historians.

That's where Jesse Frederik, economics correspondent at De Correspondent, comes in. His mission?

And delivering on this promise, Frederik offers Blockchain, the amazing solution for almost nothing. I couldn't have written it better myself.

See also: Crhypeto debunking

Edit

In the "Garden of Snakes", IORADIO's interview with Stephen Diehl, contains a 1-minute discussions of crhypeto's cultishness at 44:50.

Update

With a new religion comes new titles. God Bless Crhypetopastors. 5 "crhypetocurrencies" and a couple religions are all it takes to feed the multitude of scammers!

The crash of Lion Air Flight 610 and the resulting 189 deaths raised quite a few questions. Understandably, a lot of suspicion went towards the plane's manufacturer. But Boeing had much luck in those circumstances; what better target for deflecting blame than dead pilots? And indeed, this crash was initially blamed on pilot error.

Unfortunately for Boeing, the flight had a few survivors: its flight recorders ("black boxes"). And with hundreds more equally flawed planes, 5 months later, when an equivalent failure caused a second "737 Max" crash, Boeing's cover-up blew up. In March 2019, an article by the New York Times already made the existence of MCAS (the Margins and Casualties Augmentation System?) public, and the technical causes of these catastrophes were already mostly known.

Ultimately, it's clear these catastrophes are attributable to governmental failure, after the FAA outsourced safety verifications... and not to independent parties, but to parties paid by manufacturers. Thankfully, Canada's government hasn't given up on all its responsibilities yet, as a remarkable The Fifth Estate episode shows. Congratulations to Terence McKenna and the CBC for managing to deliver such a remarkably both technical and emotional picture in just 24 minutes.

The episode from The Fifth Estate is a little too short to fully cover the technical issues, but I recommend others who are curious about these causes and who are passionate about software and security to read the IEEE Spectrum's How the Boeing 737 Max Disaster Looks to a Software Developer, a detailed explanation of the surreal design failures which culminated in these catastrophes. It would be sin not to thank Gregory Travis for writing an accessible explanation which is nevertheless comprehensive in all aspects—technical (mechanics, redundancy, autopilot, user interface and engineering), historical, social, economic or political. Even though The Fifth Estate's episode had brought me to tears, Travis's careful writing and - having seen quite a few times in my own experience the same patterns he describes - his description of the accumulation of mistakes managed to give me a good laugh.

No bugs, just no design

Despite what the Times article and others may suggest, there is no real "error" which contributed to these crashes. Clearly no pilot error. But also, no defective line of code, nor any kind of software bug. The software behaved as it was intended to behave. All there is are a couple predictable sensor failures, and more importantly, systemic negligence. The wrong engineers influenced by the wrong managers, blind to the few who did manage to foresee what would happen. The wrong people managing critical systems, all under the watch of clueless (or partial) supervisors.

To make a parallel with wheeled vehicles, the "737 Max" is a motor vehicle with a single brake. There is nothing broken in cars which have a single brake. In 1900, owning one would surely have been a great privilege. In 2016 though, there were few ambulances relying on a single brake. And if a hospital was forced to rely on one, you'd expect paramedics driving it to be warned and trained to use it as a last resort only.

Lessons

As outrageous and irresponsible as all this may be, I am not an advocate of market intervention. Governments don't necessarily have to inspect and certify planes themselves. It is unavoidable for airlines to cause negative externalities at times. But if they do, those flying need to accept to internalize these risks. Airlines and governments should warn each passenger and crew member about the risk flying represents. And possibly prevent minors from flying on ridiculously unsafe planes.

Something needs to be done quickly to stop such patterns. Lives fly when you're crashBoeing.

2021-01 Update: Boeing Charged with 737 Max Fraud Conspiracy and Agrees to Pay over $2.5 Billion USD
2022-10 Update: Boeing to pay $200 million to settle charges over misleading investors after 737 Max crashes
2024-07 Update: Boeing will plead guilty to fraud related to fatal 737 Max crashes

2024-01 Addition: Following a new incident involving another 737 Max, former Boeing manager Ed Pierson is blunt about Boeing's failure in his 5-minute interview for CBC.

When a decade of geek madness about "cryptocurrencies" culminated in May, I wrote a public warning. Since then, the hype has finally moved, and I'm happy to see the critical view almost no one had the courage to explain during Peak Crhypeto now well described by a mainstream magazine:

Unfortunately, that article's title also reinforces a misunderstanding which was a basis of that mad decade. Which brings me back to a discussion I had with a physiotherapist early this year, which was a large part of my motivation for going public. This sympathetic guy was not dumb, but he was telling me about the thousands of euros he had invested in "cryptocurrencies", and apparently trying to encourage me to join the party. He regretted not having invested more earlier, and all the money he could have made if he had. This guy had the best intentions, but was unintentionally hurting himself, and perhaps even his patients. I tried to warn him gently that "cryptocurrencies" had no value, but he countered that market valuation was exploding...

"Cryptocurrencies" have always been worthless. But since market valuation is based on trades, and since a buyer always believes what he buys has value, market value cannot - by definition - show the actual value of "assets" such as "cryptocurrencies". The market cap of "cryptocurrencies" is surely going to keep decreasing as more and more people lose their illusions, but it will never reach zero.

The article also has the merit of distinguishing blockchains from "cryptocurrencies". The blockchain technology could be considered valuable. However, I need to warn about how the article treats it. Essentially, blockchains are a marketing invention made to portray Bitcoin as credible and ingenious. Merkel trees are useful, but there is nothing novel or really interesting about blockchains. Most projects using them are either creations of scammers who wanted a credible way to attract investments from superficial investors, just like "cryptocurrencies", or a way for legitimate entrepreneurs with projects that don't need blockchains to convince easily impressed investors more easily. In fact, it turns out the blockchain technology is such a bubble that a study found it is almost always a disappointment.

See also: Crhypeto debunking