We are Voyeurs

I sponged this text from a FB page of MR Sugar somethinG

“I want to share an update on the Cambridge Analytica situation — including the steps we’ve already taken and our next steps to address this important issue.

We have a responsibility to protect your data, and if we can’t then we don’t deserve to serve you. I’ve been working to understand exactly what happened and how to make sure this doesn’t happen again. The good news is that the most important actions to prevent this from happening again today we have already taken years ago. But we also made mistakes, there’s more to do, and we need to step up and do it.

Here’s a timeline of the events:

In 2007, we launched the Facebook Platform with the vision that more apps should be social. Your calendar should be able to show your friends’ birthdays, your maps should show where your friends live, and your address book should show their pictures. To do this, we enabled people to log into apps and share who their friends were and some information about them.

In 2013, a Cambridge University researcher named Aleksandr Kogan created a personality quiz app. It was installed by around 300,000 people who shared their data as well as some of their friends’ data. Given the way our platform worked at the time this meant Kogan was able to access tens of millions of their friends’ data.

In 2014, to prevent abusive apps, we announced that we were changing the entire platform to dramatically limit the data apps could access. Most importantly, apps like Kogan’s could no longer ask for data about a person’s friends unless their friends had also authorized the app. We also required developers to get approval from us before they could request any sensitive data from people. These actions would prevent any app like Kogan’s from being able to access so much data today.

In 2015, we learned from journalists at The Guardian that Kogan had shared data from his app with Cambridge Analytica. It is against our policies for developers to share data without people’s consent, so we immediately banned Kogan’s app from our platform, and demanded that Kogan and Cambridge Analytica formally certify that they had deleted all improperly acquired data. They provided these certifications.

Last week, we learned from The Guardian, The New York Times and Channel 4 that Cambridge Analytica may not have deleted the data as they had certified. We immediately banned them from using any of our services. Cambridge Analytica claims they have already deleted the data and has agreed to a forensic audit by a firm we hired to confirm this. We’re also working with regulators as they investigate what happened.

This was a breach of trust between Kogan, Cambridge Analytica and Facebook. But it was also a breach of trust between Facebook and the people who share their data with us and expect us to protect it. We need to fix that.

In this case, we already took the most important steps a few years ago in 2014 to prevent bad actors from accessing people’s information in this way. But there’s more we need to do and I’ll outline those steps here:

First, we will investigate all apps that had access to large amounts of information before we changed our platform to dramatically reduce data access in 2014, and we will conduct a full audit of any app with suspicious activity. We will ban any developer from our platform that does not agree to a thorough audit. And if we find developers that misused personally identifiable information, we will ban them and tell everyone affected by those apps. That includes people whose data Kogan misused here as well.

Second, we will restrict developers’ data access even further to prevent other kinds of abuse. For example, we will remove developers’ access to your data if you haven’t used their app in 3 months. We will reduce the data you give an app when you sign in — to only your name, profile photo, and email address. We’ll require developers to not only get approval but also sign a contract in order to ask anyone for access to their posts or other private data. And we’ll have more changes to share in the next few days.

Third, we want to make sure you understand which apps you’ve allowed to access your data. In the next month, we will show everyone a tool at the top of your News Feed with the apps you’ve used and an easy way to revoke those apps’ permissions to your data. We already have a tool to do this in your privacy settings, and now we will put this tool at the top of your News Feed to make sure everyone sees it.

Beyond the steps we had already taken in 2014, I believe these are the next steps we must take to continue to secure our platform.

I started Facebook, and at the end of the day I’m responsible for what happens on our platform. I’m serious about doing what it takes to protect our community. While this specific issue involving Cambridge Analytica should no longer happen with new apps today, that doesn’t change what happened in the past. We will learn from this experience to secure our platform further and make our community safer for everyone going forward.

I want to thank all of you who continue to believe in our mission and work to build this community together. I know it takes longer to fix all these issues than we’d like, but I promise you we’ll work through this and build a better service over the long term.”

People claim they stay with FB because mr Sugar so and so is a world class leader. I humbly like to state he is a voyeur like I am a voyeur and that’s the only reason I have a FB account….

Nostalgia – RMS Queen Mary 2

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2606

We met her a bit upriver

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004IMG_2615akl

Passed her and saw her ginourmous wake without having real speed for the first time. Notice the slightly plump backside

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2619aakl

Turned around and passed her again

QM2 IMG_2628akl

Sailed in Front of her

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2629akl

Sailed in Front and let her come closer

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2627aakl

Watched al the spectators lined up in Front of the Radio Port Rotterdam building in Hook of Holland. The first 3 rows would get wet feet from the wake when she passed.

Queen Mary 2

Watched her passing one of the two “Mushrooms” at the mouth of the Nieuwe Waterweg

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2654a_1KL

Saw the Pilot Tender Enterprise approach alongside to pick up the Pilot

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2659aakl

Made a close up just after the Pilot boarded the Pilot Tender

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2673akl

Escorted her a bit further before we turned around and headed for Scheveningen

Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004 IMG_2674aaaKL

And said “Goodbye” when she literally sailed into the sunset.

Nostalgia – Meeting Cruise Ship Queen Mary 2 in Rotterdam, 2004

In 2004 we still had our hotel Haagsche Suites and our boat Haagsch Schuim and even sometimes some money to to fill the tank of the gasoline guzzling 500 HP of the boat and some time to have adventures.

With hindsight one of the best trips was that of July 21 2004. We departed from Scheveningen in the afternoon and sailed to the Nieuwe Waterweg, which is the name of the water connection between Rotterdam and the North Sea. It took us only 3 quarters of an hour. We would encounter the Cunard cruise liner Queen Mary 2, which was inauguratede in Spring 2004 as the largest cruise liner of that year. It was its first visit to Rotterdam for just one day and thousands and thousands spectators were looking on, both in the city where she was berthed in front of the old head office of the Holland America Line and a new cruise terminal, and alongside the Nieuwe Waterweg. Estimates were around 200,000 visitors.

We met it a bit upriver and consorted it to the North Sea together with various other boats, part private and part in function like Pilot tenders, Dutch Police Patrol Boats and Rotterdam Port Authority Patrol vessels.

When QM2 entered service in 2004 on the Southampton to New York route, British Royal Mail granted it the RMS (Royal Mail Ship) designation (prefix) as a gesture to Cunard’s history.

Skull Speakers

Jarre Skull Green I56A1652

Jarred Skull Speakers

I’ve visited IMM Cologne yesterday, mainly hunting for chair news. However, I noticed these skull docking stations on display. They come in 7 colors if I’m counting right. I won’t disclose more about the manufacturer than I did here already (think ALT…). I believe it is something you don’t want to use in your home, but many may disagree with me.

At least they are interesting photo objects…