Ben Dunkle’s Blog

The size of a pixel is relative to its output device, aka screen resolution.

Some screens are 72 dpi. Some are 300 dpi. So if you specify your font size to be 12px, it should rightly appear legible on the 72 dpi screen, and tiny on the 300 dpi screen.

Instead, use point, or pt. A point is 1/72 of an inch. 12pt will appear legible on any screen, regardless of its dpi.

I bought uofwp.com a long time ago and in a spark of inspiration decided to launch the site. There’s not much there for now.

Check it out:

uofwp.com

If you know me, you probably know I’m a big chess fan. I’ve been playing it almost all my life, having learned it from my friend Chucky’s grampa and being fascinated by every aspect of it ever since.

I definitely play too much–the internet makes it so easy to grab a quick game on a whim, and I have racked up thousands of 1, 2, and 3 minute games this way.

On the one hand, I could argue that it keeps me sharp; playing chess forces me to exercise my brain power, analytical thoughts, and concentration.

Regarding that last point: concentration, I heard an interesting comment by renowned chessmaster and Twitch.tv streamer Eric Rosen recently. He was asked by someone in the chat box: “Does playing chess help you concentrate?” His answer was something like: “Getting lots of sleep, eating well, and exercise helps you concentrate. Chess depletes your concentration.”

Media queries are firmly established methods for serving custom experiences based on the media being used to access content.

However, there’s no way to an experience based on the context being used. How crazy would it be would it be if this were possible?

Imagine some code that went like:

@context (currently-traveling:yes AND role:driver) 
{ * {display:none;} } /* hide app from a distracted driver }

That’s some scary stuff, privacy-wise, but you know if it were possible people’d be writing it. But just think of what you could do with

environment:outdoors

noise-level:loud

The portrait-oriented, single column design approach that’s become so dominant since the advent of smart phones can only last for so long. The new paradigm of wearables, particularly visors/glasses, will see us return to landscape designs. Augmented reality will enable a screen of any size and format to appear in a multitude of contexts. The physical limitations of the handheld phone will become characteristic of a primitive era in the digital age.

It’s no wonder the machine (however you want to define that, the powers that be, the man, our corporate overlords) is mining our data. It’s always mining something: iron, gold, oil, electricity (although the more elegant term for that is harvesting) – it’s just incredible how much data we produce and how easy it is to mine it.

The Social Dilemna does a good job of exposing that, although I could have done without the cheesy scripted stuff. However, it fails to point out the counterpart to our data, and what is in fact infinitely more valuable: our content.

Every post we make-video, photo, rant, tweet, comment, is like food for the machine. Without content, there is no internet. No one logs into Facebook so they can click on ads or fill out surveys or practice browsing habits. They go for content–to consume others’ and to post their own.

Content self-propagates; the machine doesn’t have to invasively collect it, analyze it, reconfigure it, or present it to its paying advertisers, as it does with data. And there’s mountains of it, and we give it away for free!

One of the interviewees suggests that we tax the machine for its data. That sounds great in theory, but I have a hard time understanding how it could be enforced. Instead, they should be taxed on their content they collect. It’s far easier to monitor.

Better yet, we could demand compensation for the food we’re keeping the machine alive with. Kind of like selling the glut of solar power you’re harvesting with your roof panels back to the utility companies. Let’s figure out how to do this.