Category: Tech

Posted on
by

Usability researchers like Jakob Nielsen have long contended that people read differently online than on paper: they tend to skim, follow links, and jump off quickly if they don’t find what they want. (Rather than being judgmental, Nielsen simply advises that you tailor your online writing to this.)

Now the Washington Post reports that people are observing a spillover effect, with online skimming habits interfering with concentration when it comes to more in-depth reading…even when reading print.

Sadly, the article mostly distinguishes between two modes of reading:

  • Online skimming of casual articles and social media on screens.
  • Serious reading of novels and in-depth content in print.

There’s nothing to distinguish, for instance, reading on a dedicated e-reader (without the siren call of Facebook or hyperlinks) from reading on your laptop. Nor is there anything to distinguish casually reading on your phone’s tiny screen from reading at your computer, or sitting on the couch and reading on a book-sized tablet.

A tablet and a breaking paperback.

Personally, I’ve found display size to be the biggest factor in maintaining attention. I get tired of reading on my phone, and I tend to skim on a desktop or laptop, but a handheld tablet (I have a Nexus 7, which is close to the size of a paperback book) works out about right. I’d much rather read a long article on that tablet than on a computer, even with the browser window sized for optimal column width.

So yeah, it’s much easier to concentrate on something long in a book than on a desktop or cell phone…but an ebook reader or a tablet is a lot closer.

There are still tradeoffs: My Les Misérables re-read changed drastically when I switched from a paperback to my tablet…not because I couldn’t concentrate on long passages, but because my method of notetaking changed. My reading actually sped up, but my commentary slowed down. (It did ultimately take me longer than I expected to finish the book, but only because I had so many other books I wanted to read, and ended up taking breaks and reading them instead.)

The main problem I do have with a tablet isn’t continuing to read, but starting to read. Even without a wifi signal, it’s tempting to catch up on email, or saved articles in Pocket, and before I know it, I’m done with lunch and I haven’t even opened the book I’d planned on reading.

(Via Phi Beta Kappa)

Posted on
by

A few nights ago I watched the moon rise. This isn’t actually very common, just because hills and buildings mean that I rarely get a clear view of the horizon, but I had been working late and drove past LAX, which gave me a long flat stretch off to the east.

The weird thing is: it was gray.

I’m used to the moon looking white when it’s up high in the sky, yellow when it’s low, sometimes orange when it’s near the horizon, especially when there’s smoke or smog. A few months ago while the Colby Fire raged in the mountains to the northeast, I reached the top of a hill and had a fantastic view of a deep red moon through the smoke.

But gray? That was a surprise. It looked just like photos of the moon that are taken at the right exposure level to show you details instead of washing everything out. Squished a bit, of course, because it was so low.

As I kept driving, I passed more buildings and lost sight of it. A few minutes later, I caught another glimpse after it had climbed a little higher, and it looked slightly yellowish, just like I’d expect it to at that height.

I don’t know if it was something about how my eyes had adjusted, or if there was something in the haze above Los Angeles or even just nearby that counteracted the normal effect of scattering.

It did, however, remind me that the next full moon will feature a lunar eclipse, visible from our neck of the woods…the first since my son is old enough to (maybe) appreciate it. That should be fun.

Posted on
by

It’s always annoying when someone figures out a way to exploit intentional behavior, especially when it’s a key part of the design.

Sucuri reports on a denial-of-service attack that used thousands of legit WordPress sites to distribute the attack by sending fake pingbacks “from” the target site to all of the reflectors. Those blogs would all contact the targeted site to confirm the pingback and retrieve a title and summary…all at once, overwhelming it and taking it offline.

The quick-and-dirty solution is to remove XML-RPC functionality, but that also breaks certain plugins (like Jetpack) and the ability to connect to your blog using the WordPress mobile apps.

A little background on why Pingbacks work this way:

Waaaay back in the early days of blogging, most bloggers would interact by way of comments. If you wrote a blog post, and I was inspired to write a response, I would then go over to your site and post a comment letting you know about my own post. Two systems were proposed in 2002 to automate this process: pingbacks and trackbacks.

  • Trackbacks sent a complete summary to the remote blog, including the title of your post, the link, and an excerpt (which you could manually craft, or let your software handle).
  • Pingbacks sent a notice — a “ping” — to the remote site with the URL of your post, and then the remote site would retrieve it and extract the title and a summary.

This was also around the time that blog comment spam and spammy blogs were getting to be a big problem. What would happen is a spamming site would send out trackbacks to as many sites as possible claiming that they’d responded to some post, thereby getting backlinks on a zillion blogs and increasing their page rank. Pingbacks had an advantage: Because you were calling back already, your server could check to see whether the other site really had linked to you. It took a long time, but eventually this escalated into spammy blogs creating a temporary post with real links to the pages they pinged, then replacing it with a spam page after a short amount of time.

The problem now is: How do you block abuse of an as-designed behavior? That’s happened before: Back in the early days of the internet, it was considered polite to run your mail server as an open relay and rude to lock it down, but after spammers started massively abusing them, an open relay became a sign of a sysadmin who didn’t know what he was doing.

The comments on the Sucuri article suggest that Akismet, as a collaborative comment-spam filter, might be able to mitigate this type of attack. Wordfence’s collaborative security filter seems like another system well-positioned to detect it. But if that approach fails, pingbacks might just go the way of open relays.

Update March 18: Akismet has released a new version of the anti-spam plugin that mitigates this problem in two ways:

  1. Spam checks on pingbacks are now done before the verification request is sent, so that once an attack is identified, Akismet will prevent blogs from participating.
  2. An X-Pingback-Forwarded-For header is added to the verification request identifying where the pingback actually came from, making WordPress+Akismet a less attractive choice as a reflector by removing the anonymity.

Item #2, IMO, belongs in WordPress itself, not in a plugin, but I imagine this was a way to roll out the feature more quickly, at least to those sites using Akismet.

Update April 8: The X-Pingback-Forwarded-For header has been added to WordPress 3.8.2 and the upcoming 3.9.

Posted on
by

I was reading up on wearable computing today, and with the SDCC badge presale looming, I found myself wondering whether a smart watch would be useful for Comic-Con.  (No plans to actually buy one, I’m just thinking.) I don’t normally wear a watch these days, but it does get annoying to have to reach into my pocket when I want to check the time. For this reason, I make a point to wear a watch at conventions so that I can see the time at a glance and avoid missing events or meetup times.

So, keeping in mind that the current generation of smart watches (Pebble, Galaxy Gear, etc.) mostly pair up with a phone to do the heavy lifting…what might a smartwatch do better for a con than a phone (or a regular watch)?

1. Messages. Between the noise and the walking, it’s already too easy to miss calls or even texts when you’re out on the floor of the convention. It’s easier to notice a buzz on your wrist than a buzz in your pocket, and less intrusive to glance at your wrist to see if it’s something urgent when you’re interacting with people in the real world. You can also tell instantly when you’re crowd-weaving to meet someone whether that text they just sent is “I’m here,” “Running late,” or “Change of plans, meet me at Hall G lobby.”

2. Schedule reminders. Put the event, time, and room number on the screen. How to make it more awesome: pull down the floorplan and use your location to calculate how long it’ll take to get there, and notify you far enough ahead of time that you can make it, Google Now-style. This is more useful for smaller conventions or at least smaller panels at SDCC, since the big ones require you to line up way ahead of time anyway.

3. Wi-Fi hotspot detector. Even if the watch doesn’t support wi-fi, your phone does, and it can ping the watch to let you know.

4. Breaking news alerts. Ironically, I feel like I miss more news when I’m at Comic-Con than when I’m following along from home. This would have to be very well filtered in order to be useful without pulling you out of actually experiencing the convention.

A step counter would be interesting, but I can probably find an app for my phone.

I doubt I’d use a wrist-mounted camera like the one on Samsung’s Galaxy Gear much. Google Glass would be more practical for the blink-and-you’ll miss-it moments, and if you have time to compose a shot, you have time to pull out a phone or dedicated camera. OTOH, a wrist camera is probably a little less creepy than Glass. (On the gripping hand, maybe not.)

Of course the absolute best use of a smartphone at Comic-Con:

5. Get one that can actually handle calls, and wear it with a Dick Tracy costume.

What uses can you think of?

Posted on
by

I’ve been using Pocket lately to offload “Hey, this looks interesting” articles from times when I really should be doing something else to times when I have, well, time.

  • It syncs a copy of the article to each mobile device, which means I can see something in the morning, save it to Pocket, then read it on my tablet at lunch.
  • Feedly talks to it easily. I’ve even linked it up with IFTTT so that tapping “Save for Later” on the tablet will add an article to Pocket.
  • Speaking of IFTTT, I’ve also set it up so that saving an article as a favorite in Pocket also adds it to Delicious.
  • The Android app will accept shares even if there’s no network connection, then sync up when it’s online. That means I can look over a newsletter in Gmail at lunch, save the links that look interesting, and archive the email. Then I can read the article at work or at home…or the next time I’m out somewhere, after it’s synced.

I’ve also started using the text-to-speech feature to listen to articles in the car while driving to and from work. The voice is fairly decent despite the usual flat tones and lack of natural rhythms, but there are a few oddities that take getting used to.

  • # is always read as “hash.” This makes it really odd for comics articles, which frequently talk about issue numbers. “Batman Hash 123” just sounds wrong.
  • Italics are…always…emphasis, and presented by…pausing…rather than changing tone. This makes it…awkward…for anything involving lots of titles.
  • It parses words, rather than using a dictionary, and can’t always figure out whether initials should be read individually or pronounced as a word. This usually works fine, but occasionally leads to phrases like “tah-kay-down notice,” (takedown) “link-uh-din” (who knew LinkedIn rhymed with Vicodin?) or “pohs terminal” (POS as in Point-Of-Sale) On the other hand, it figured out “I-triple-E,” so I imagine it’s got a dictionary for special cases.