As many of you will have seen, unfortunately the Ubuntu Edge campaign did not reach our goal of $32million. The final total reached was $12,812,776. I am hugely proud and thankful to everyone who pledged, supported the campaign, wrote about it, and helped to spread the word. Some have described us not meeting the goal as a "failure". I don't see it that way. Let's be honest: $32million was always an incredibly ambitious target. We would have liked to have done it for less money, but building a F1 superphone doesn't come cheap (and remember that the $32million didn't include any costs for software engineering and project managementCanonical were providing that for free). It was an ambitious target, but disrupting an industry is ambitious in itself, and we gave the crowd-funding campaign our best shot. The story does not end here though. I am not surprised that we didn't hit this ambitious $32million target, but I am surprised at what we did achieve. We broke all the crowd-funding records, garnered media attention across CNBC, Engadget, The Independent, TechCrunch, the BBC, T3, Stuff, The Verge, The Guardian, Wired, pandodaily, Fast Company, Forbes, The Telegraph and more. Every single person who put their support into the Ubuntu Edge campaign should be proud of their achievements and we are all thankful for your tremendous and inspiring support. One thing to be critically clear about is that the Ubuntu convergence story does not end here. We are as voraciously excited and committed to bringing this Free Software convergence story to the world as ever before; our work with OEMs, Carriers, and ISVs continues apace. We have fantastic work going on across all fronts, and we are on track to have a 1.0 release of the Ubuntu Phone platform in October. When did the Ubuntu Edge campaign raise $12,812,776? Pick the correct answer from the following options: A. before setting a goal of $12 million B. before setting a goal of raising $32 million C. not enough information D. After setting a goal of raising $32 million
D

(Question)
I lost my baby boy at 31 weeks of pregnancy in February 2013. My heart shattered into a million pieces that weekend in February. I knew that I wanted the chance to bring home another live, healthy baby in my arms. I had some medical issues that would concern doctors during a uncomplicated pregnancy and would put me at high risk if, and that at the time was a big if I was able to get pregnant, and could I make it past the second trimester. I had doctors who supported my decision to try again, but my body wasn't co operating. 2015. I got pregnant, straight on the medication I needed, lots of blood tests. Got a horrible sinking feeling something went wrong at the 6 week stage, bleeding at 8 weeks. At 9weeks of pregnancy, got a scan and no heartbeat was found. I choose the d&c operation, I couldn't deal with seeing the miscarriage blood for days. I tried to convince myself to give up, move on. Wasn't an easy thing to do, but the depression and sadness wasn't fair to my 6 year old son. He needed his mummy who was always sad, in his mind. About 6 months later, I was having a scan. This time, I had a strong heart beat on screen. The pregnancy was extremely high risk, consultant led, daily injections, scans every 2 weeks from 18 weeks. No guarantees of a good outcome. Planned c section at 38 weeks. Healthy baby girl. I was lucky, I got the chance to have my happy ever after. Was it worth the heartache and infertility caused by stress - yes Was it worth the terrifying 34 weeks of pregnancy- yes Do I miss and wish the baby boy I lost at 31 weeks was here - every day For me, being bloody minded and stubborn worked out for me. Why was the writer sad and depressed Pick the correct answer from the following options: A. Her husband left her B. not enough information C. She did not want to be pregnant D. She lost a baby at 31 weeks and thought that she was infertile
(Answer)
D

Facebook has a long track record and sordid history of abusing their users' trust and privacy, including the most recent and egregious cases currently making headlines with Cambridge Analytica as well as election meddling in the US and Britain. As if that wasn't enough, it then came to light that they have also been tracking and storing users' phone call and text message data, including "who contacted whom, what time, and how long the conversation was." This is nothing new, as we can see from this 2012 "study" in which they deliberately manipulated news feeds to influence users' emotional state. And again with their settlement with the FCC back in 2011 (that they likely violated with their recent offenses) over deceiving consumers by telling them their information was private, but then repeatedly sharing it and making it public. And then there's The Ugly Memo, in which a FB exec justifies growth at any cost in the name of connecting people, even if that results literally in people dying: We talk about the good and the bad of our work often. I want to talk about the ugly. We connect people. That can be bad if they make it negative. Maybe it costs a life by exposing someone to bullies. Maybe someone dies in a terrorist attack coordinated on our tools. And still we connect people. The ugly truth is that we believe in connecting people so deeply that anything that allows us to connect more people more often is *de facto* good. And up until this most recent Cambridge Analytica scandal, Facebook was negotiating with various healthcare organizations to share patients' health data with FB so they could match it up to your social circle to allegedly provide better health care. Um yeah right. Each time this stuff happens, they issue an apology (or a justification for their behavior) and promise they will take steps to better inform users and protect their privacy, but it's clear that this is just lip service at this point. How did the facebook exec try to justify the Ugly memo? Pick the correct answer from the following options: A. Connecting people is de facto good B. not enough information C. It would improve health care D. It was in response to the FCC settlement
A