Tag: #TechnologyHeadache

Posted on

Why Crypto Isn’t Ready for Us

Photo from New York Magazine.

Sam Bankman-Fried is on trial this week for fraud in cryptocurrency, which seems like the perfect time to analyze why crypto is neither necessary nor sufficient for life in 2023. In other words, I don’t like it.

I’m supporting a couple of online investing classes that each had a whole module all about crypto, so I may have to “teach it.” One of my beefs is that explanation about a new payments process should not obsess about the technical aspects of how it works. If you start the discussion of “what is digital currency” by using the word “blockchain” and a set of Rubik’s cubes, then I know it’s already gone off the rails. Hope I don’t have to grade any assignments touting this nonsense er… technology still underdeveloped.

For those of you who don’t know the difference between proof of stake and proof of work or which Marvel movie featured the Scarlet Witch or how many points a ranger adds to their acrobatics D20 roll… in other words, if you’re not mesmerized by geekery over this stuff, let me see if I can detangle why digital currency’s time has not come. It has to do with 1) technological vulnerability; 2) lack of standardization; 3) volatility; 4) diffusion of purpose. Allow me to expound.

TechnoBabble

There’s actually a joke about crypto in the mystery series “After Party II.” The murdered guy made his fortune in crypto, and when one person asks what exactly he was doing, the official nerdy character jump in with, “Let me explain what blockchain is…” That’s how we know this is all silly. If you are explaining either an investment or a way to pay for a sandwich by talking about how the currency is built, we’re in trouble. Do I need to know what kind of special ink is used to make a twenty dollar bill or how they put the hologram on in order to know that it’s not counterfeit? If you ask me how a bank works, do I start by explaining what kind of reinforced concrete they use for the vaults?

Photo from Open Access Govt. Notice how you need digital art to create digital photos of blockchains.

Blockchain may indeed be quite secure. Encryption is pretty secure. Fort Knox, I suspect, is quite secure. The question of how digital currency works should not begin with whether or not it’s secure or how it’s secure. It should begin with how you use it. To my mind, there is vulnerability there. Why? Because digital currency can only be used from within a program.

Say I want to buy a soda at my local mini-mart with crypto. I need my phone, my password to the phone, my password to the app. And the phone needs service and to be fully charged. The mini-mart needs technology, too, as well as working access, service, etc. All of a sudden, this “so easy” process has several layers. Not convinced? One of the first folks to pay with crypto at Subway, which touted its willingness to accept payment, described this incredibly easy process as:

Once our subs were made the employee took out an iPad and opened Coinbase. She punched our total in the register and then in the iPad, which immediately generated a custom QR code linked to the store’s Coinbase account which was preloaded with our exact total calculated. I took out my iPhone, opened my Coinbase app, and scanned the QR code. Instantly the total popped up on my screen and gave me the option to leave a note about my purchase.

From Coindesk.com blog.

I’ll stop you right there. The employee took out an iPad? A separate piece of technology, disconnected to the register? That has to coordinate with the store’s accounting system? Who do you think is making these sandwiches at Subway? It’s not Chat GPT, I’ll tell you that much.

Photo at Coindesk.com.

By the way, googling this topic about Subway also led to story #1: Subway has just been sold to a giant conglomerate private equity firm that also owns a dozen other food service chains. Story #2: Subway-themed trading bot makes millions using ‘sandwich’ attacks! That means a digital pirate stole millions digitally using Subway as his villain name. And that whatever Subway wanted to do with digital currency acceptance may soon go out the window with the new ownership. Let’s see if crypto stays on Subway’s menu.

Continue reading “Why Crypto Isn’t Ready for Us”
Posted on

I Do Not Consent to the Googles

Hmmm, I hope selecting this image for the post didn’t start a purchase. I am Not Paying For it!

“Why is my phone telling me the weather in Seattle? I didn’t ask for that!”

My long-suffering spouse looks at me, sighing, and says, “That’s Google Assistant.”

“I didn’t turn on Google Assistant. I didn’t give it permission. Why is it doing this?”

She shouts towards my phone, “Hey Google….” Nothing happens. “It must not recognize me.”

“Why would it recognize you? It’s not on.” Ignoring my own retort, I bark at my phone. “Hey, you Google…”

Nothing, of course, happens, other than a cheery notification that tells me what the baseball scores are from games that happened seven hours ago. The baseball games which I had already watched and could already tell you who scored what when with runners on base over which pitch count.

Off the Grid Is Impossible

I do not Hey Google. I respect you if you do, but I don’t believe in talking to objects. I don’t believe we should have robots listening throughout the house to our every activity. I don’t have seeing eyes peering out the front door to spy on mischievous-looking passers-by nor do I have glowing orbs in my bedroom, blinking to notify me that there might be a lost dog three miles away.

Continue reading “I Do Not Consent to the Googles”
Posted on

5 Primo Coding Secrets for English Majors

Last week, as I was trudging through the quicksand of changing my website theme, constantly sinking into the swamp of contradictory code and grasping at branches of CSS held out by travelers before me, I wondered if something positive could be pulled out of the mess. Aha! I could share what I learned with the blogosphere. Thus, in the spirit of passing on some recently, painfully-earned wisdom, I will share the most dominant lessons.

CSS code response = success
Source: Dreamstime.com

Have you ever forgotten to save your writing after a long stretch of creativity, only to have your computer crash and lose hours of your genius? In the old pre-computer days, this was known as “the teacher lost my paper.” Two weeks of my best creativity disappeared because I was too cheap to make a copy of my seminal work on the religious imagery in e.e. cummings’ poetry. It still bothers me, decades later! Back up your work. Here’s what that means when you are creating or making changes to a blog site.

1. Write down the changes you make–preferably as you go

Most writers know how and why to keep track of changes as they go, either by using a Track Changes feature or the primitive “print it out and make edits by hand” method. Version control becomes an issue when you don’t keep track. Also, what if you change something and you decide you don’t like it? You might want that original brilliant phrase back which only sounded mundane after a night reading Seamus Haney. The same logic applies to changes to technology. Continue reading “5 Primo Coding Secrets for English Majors”

%d bloggers like this: