Iceland: Elves, ATV Rides, and the Blue Lagoon

Our last day in Iceland was eventful and action packed. Throughout the trip I’d been doing my best to see elves and huldufólk (hidden people) in the many majestic landscapes we visited. Luck hadn’t been on my side but on this last day, our guide took us to a special beach and gave us all a “pill” to grant us powers to see the elves.

I didn’t see any elves, but the seascape was spectacular. Even more magical was having the sun come out for a brief period of time, a rare and welcome treat.

the Elf Beach

After the beach we headed to Grindavik, a town in the Reykjanes Peninsula. We toured the Search and Rescue center, where we heard from a volunteer about the different sorts of rescue missions performed by the center.

Following the tour, we suited up for an ATV ride through the lava fields.

My mom was in the back seat of the ATV and I proved to be a terrible driver. The ATV was clunky to steer and I veered off the path once or twice. The terrain was bumpy and full of muddy depressions making it challenging to stay on course. At the midway point, we stopped to take pictures of an abandoned ship.

Following the ATV ride, we had lunch, then headed to the famous Blue Lagoon spa for a relaxing afternoon soak in the mineral-rich waters.

I felt a bit conflicted about the Blue Lagoon because it’s a manmade natural wonder. The Blue Lagoon, we discovered, was created from a geothermal power plant’s seawater run-off. As I learned during my trip, Icelanders love a hot soak and I suppose the local residents couldn’t resist the allure of the heated, turquoise waters surrounding the power plant. They started bathing in it and discovered that the mineral-rich waters had restorative and healing properties.

Although I normally prefer swimming to lounging around in hot waters, I thoroughly enjoyed my time in the Lagoon. The spa consisted of one giant pool, but temperatures varied in different places. Plus, it was really cool to feel how the mineral deposits created a smooth, enameled surface on the lava rocks and crevices filled with soft, silty mud.

Feeling refreshed and rejuvenated from my soak, I boarded the bus. We headed back to Rekyjavik for a farewell dinner and one last magical night in Iceland.

Banks and Automation

Although I’m usually pretty quick to adapt to new technologies and automation, I’ve been a holdout with the banks. The rare time I get a check, I still prefer to go into the bank and endorse it in front of a teller. I usually handle cash the same way.

I’m not sure why I cling to my old-fashioned and outdated modes of banking. Now it’s possible to deposit a check from anywhere by taking a picture of it with your phone. And most ATMs now accept cash and check deposits without an envelope. The first time I observed my partner, a modern and updated bank customer, seamlessly deposit cash without an envelope, I was kind of impressed with how well the system worked.

Prior to that, having to find an envelope and a pen to make a deposit, was always kind of annoying. Often the ATMs wouldn’t be stocked with envelopes making it impossible to do a deposit. I remember remarking once to my partner that he should just carry around some extra ATM envelopes so he always had one. But then the new system arrived providing a paper-free experience with ATM deposits.

Now I was ready to embrace ATM deposits, a seamless experience without the hassle of envelopes and pens, and long awkward waits at the machines for people to count and prepare their deposits. I would just leapfrog ahead from my ancient dinosaur, luddite methods of banking straight to the most modern and slick option. But alas, the new system at the ATM has failed me on a number of occasions.

Some months ago, spying a long line inside, I figured I would use the ATM to make a cash deposit. However, the machine wouldn’t accept any of my bills, something that never happens when you hand cash to a person. When I finally reached the teller, he explained that sometimes the ATMs refuse cash if it has little creases or bends in it. This seemed like a pretty serious design flaw to me as people rarely deposit cash in mint condition into an ATM.

The ATM deposits are mostly a seamless experience, but every once in a while, the machine refuses to accept a certain bill, making me long for the good old days of tellers or cumbersome envelopes. Options that accept your deposits in full, wrinkled and creased.

Not Built for Deletion

A lot of apps that we use come equipped with default options to save everything. For example, removing the inbox label from an email in Gmail automatically results in the item being “archived.” Or with my iPad, when I delete photos from my Camera Roll, they are automatically saved to a temporary album called “Recently Deleted” photos where they will remain for 30 days. I always have challenges with this because my iPad automatically backs up the last 1000 photos I’ve taken, which includes the deleted photos stored in this temporary album. I deleted the photos for a reason, to make space for the photos I want to save and back up.

When I first noticed my deleted photos were being backed up on my iPad, I called Apple about this. It made no sense to me why valuable backup space was being used for things I had intentionally deleted. When I mentioned to the customer service rep that it didn’t seem like their systems and platforms were built for people like me who prefer to delete and organize, she agreed. She explained that when they didn’t set it up that way, people had called in a panic because they had deleted all their stuff by accident.

And yes, the accidental deletion is very upsetting and panic inducing. I know because I’ve done it a few times. I still feel a little hesitant using Google Note because it autosaves changes so fast and there’s no “undo” feature in case of an accidental deletion.

Though it seems to me like we’ve employed an extreme measure to safeguard everything. Is the best solution to accidental deletions really to save everything?  All the time? And sometimes without people knowing that their deleted stuff is being saved or “archived”?

When I delete something on my computer or from my email, my assumption is that the item is actually being purged, or expunged. I know on my home computer deleted items sit in my “trash” area for a designated amount of time, but eventually they get overwritten. They’re not secretly saved or “archived” somewhere that I don’t know about, to account for the rare time when I may have deleted something that I actually need years later.

So what’s the solution? As always, The Deletist advocates for strategic saving. Know what you have, identify what’s important, and devise plans/strategies to take care of these priority items.

Facebook’s App Developer Investigation

Facebook recently posted an update on their app developer investigation. After the Cambridge Analytica fiasco, Facebook decided to take a more in-depth look at how app developers were using users’ information from the platform.

One of the main points with Cambridge Analytica is that they were able to gather user data not only from the people who filled out their surveys, but from all of their friends and friends of friends. The goal was to try and determine personality profiles based on the data points gathered. The reach was far and invasive, in my opinion. In an effort to prevent developers from gaining broad access to the Facebook social web, Facebook decided to launch an investigation of existing apps and developers.

Some of the main challenges with allowing developers to connect applications to Facebook is that the definition of personally identifiable information is blurry. Many companies now collect dozens, if not hundreds of data points on us. Most people would probably recognize a few obvious examples, such as, SSN/SIN, phone numbers, birthdates, etc. as being personally identifiable, but lots of other bits of data are not so distinct.

Sometimes data points can be taken in aggregate and become personally identifiable. For example, some algorithms can determine a person’s sexual orientation based on their likes/dislikes. Or when a woman is pregnant based on her purchases. When these disparate data points are combined together, it can result in unintended consequences, such as someone being “outed” in a place where it isn’t acceptable. So unless these kinds of issues are identified and regulated, it will be challenging to properly protect peoples’ data.

Facebook, and social media in general, is in a tough position with these kinds of issues. Facebook was originally created with the idea of sharing openly and connecting with anyone and everyone. Part of the strategy was also to allow companies to send advertisements to targeted audiences based on their profile data. This was to keep the platform free for everyone.

However, the ramifications of having an open platform with communications going in every direction weren’t fully considered. Or how to manage these things on a global level.

The rapid expansion, and lack of attention towards privacy and regulation, resulted in a lot of challenging situations for Facebook and other forms of social media. I’m not sure what the resolution is, but it’s encouraging that people are finally paying attention.

Iceland: Journey to Another Planet

After a full morning of foss (aka waterfalls) and basalt columns, we headed to Vik, the southern most city in Iceland, for a super truck tour through black sand landscapes to visit a glacier.

Our tour guide didn’t tell us much about the tour beforehand because she wanted us to be completely surprised about what would happen. After lunch we arrived at the Super Truck for our journey to another planet. We boarded the bus and started traveling through what was becoming a familiar landscape, expansive fields dotted with black lava rocks, covered with a mosaic of mosses in myriad shades of greens, yellows, browns, and whites.

It wasn’t long before the landscape started to transform to a black sand desert, splashed with chartreuse-colored moss patches. The longer we drove, the thicker the fog became, enveloping us in a soft, shroud of white mist.

We finally arrived and stepped out of the jeep onto a landscape I felt certain wasn’t on Earth any longer. Black sand stretched out in every direction. The fog largely obscured my view, but I could dimly make out some shapes like hills or mountains in the distance. After suiting up in safety gear (mostly just a helmet) and a short demonstration on the different kinds of rocks we would see, we descended into the terrain.

The black desert landscape, covered with fog.

It wasn’t entirely clear where we were headed, but after some time our guide led us to what appeared to be a smallish mountain with caves we could enter. Much to our surprise, we weren’t in a mountain at all, but the famed Katla Glacier so covered with black sand that it looked like rock instead of ice.

Entering the glacier.

My eyes adjusted and I started to see the ice formations beneath the black sand. I still didn’t really believe everything around me was a glacier until the guide started to chip at the ice to show us. He kept chopping up the ice until he had enough clean pieces for us all to enjoy a cold, refreshing shot of vodka named after the glacier.

Chilled shots of Katla vodka.

Our eventful day concluded in Selfoss. I captured this picturesque scene of the town the day before in the morning before we headed out.

The Autosave: When is it too much?

One default setting I’ve grown to appreciate is the autosave.  I have definitely been burned more than once by the computer, or internet, malfunctioning at a crucial time often resulting in me losing hours of work. Many times, I’ve been saved because the application I was working in automatically saved a version that could be restored in case of a random failure. When working with MS applications, the autosave is there to restore a previous version in case of a system glitch, but it isn’t retained unless I consciously decide to do so.

However, there are times when autosave has backfired on me. And other times when the autosave turns into an over-save, and too much is retained. I prefer to maintain a balance between intentionally saving, i.e., when I have some control over what I want to save and when vs. the autosave for restoration purposes in case of a malfunction.

What drives me crazy about autosave is when an application automatically saves each keystroke change as a new revision, such as when I’m working with Google Docs or Google Sheets. The benefit of this is that I can always go back in time to reconstruct an earlier version. Except when every tiny change is saved as a new version, it can be difficult to figure out when I made major changes. I want the ability to designate which revisions are worth saving as a version. I know with Google Docs I can go in and edit version names, or write comments, but that feels like more work to me than consciously deciding to save a document at a specific point in time.

The other time I’ve been burned with autosave is when it saves too fast, replacing what was there previously. I blogged about this before when I accidentally deleted something from a Google Note. The delete key moved faster than I anticipated, erased some information I wanted to keep and the Note autosaved with the modifications. Read about it here.

My preference is to have autosave designed as a built-in feature in case of a system failure. The latest version is saved automatically for restoring, but I’m still in control of when I ultimately want to capture the changes in a new version. Autosaving for a specific purpose, rather than over-saving every keystroke just because we can.