bug – Techdirt (original) (raw)

Total Wipes Blames Trying To Take Down Every Page With The Word 'Download' On 'A Bug'

from the no-doubts-about-it dept

So, we just had a story about German-based Total Wipes issuing a series of increasingly bizarre takedown notices, including one that tried to claim that basically any website with the URL “download” was infringing (including the URLs of tons of popular software, from Skype to Open Office to Evernote). The company has now responded to the takedowns, insisting that it’s all no big deal because it was all just a software bug. “No doubts about it,” the company says:

Due to several technical servers problems on the first February week (from the 2nd to the 8th) our script sent hundreds DMCA to hundreds domains not related at all with any copyrights of our contents. Taking a look at https://www.chillingeffects.org/notices/10420406 is pretty clear that for a few hours only the word “download” has been used by the script and that caused several illegal and wrong DMCA requests. It was our fault, no doubts about it. The DMCA is a serious issue and it must be carefully managed. Google rejected most of these DMCA but we totally understand the damage of it for small and medium companies that have to remove and manage them manually. It was a bug just on that week and this is not our daily routine, 99% of our found/removed links are about people that steal music and make moneys illegally. However, our Anti-piracy system has been taken down a week ago in order to add more improvements and avoiding further trouble about the DMCA sending.

Of course, that would be slightly more plausible if Total Wipes hadn’t done something similar just a few months ago, trying to take down every URL with the word “coffee” in it. Given that, the “it’s just a bug” excuse doesn’t seem particularly believable.

However, even if we take Total Wipes at its word, that this is not the company’s “daily routine,” this still demonstrates how problematic any system for automatically issuing takedowns is for concepts such as free speech. If you’re issuing DMCA takedowns you are, by default, stifling speech. You can argue that it’s acceptable if that “speech” is nothing more than infringing on someone else’s work — and there’s a reasonable argument to be made there. But it is immensely problematic when you combine the default “take this down!” nature of the DMCA with the automated efforts to issue such notices. It becomes not a tool to stop infringement, but rather a widespread tool of censorship, thanks to a broken copyright law.

Filed Under: bug, censorship, copyright, dmca, takedown
Companies: total wipes

NVIDIA Calls A Feature A 'Bug,' Strips Away Overclocking Option On Its Mobile Device Cards

from the you-can-buy-it-but-you-can't-have-it dept

In theory, the marketplace for goods works like this: a purchaser hands over <spanclass="katex−display"><spanclass="katex"><spanclass="katex−mathml"><mathxmlns="http://www.w3.org/1998/Math/MathML"display="block"><semantics><mrow><mi>a</mi><mi>n</mi><mi>d</mi><mi>i</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>t</mi><mi>u</mi><mi>r</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>c</mi><mi>e</mi><mi>i</mi><mi>v</mi><mi>e</mi><mi>s</mi><mi>a</mi><mi>p</mi><mi>r</mi><mi>o</mi><mi>d</mi><mi>u</mi><mi>c</mi><mi>t</mi><mi>t</mi><mi>h</mi><mi>a</mi><mi>t</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>o</mi><mi>w</mi><mi>n</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>c</mi><mi>a</mi><mi>n</mi><mi>u</mi><mi>s</mi><mi>e</mi><mi>a</mi><mi>s</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>s</mi><mi>e</mi><mi>e</mi><mi>f</mi><mi>i</mi><mi>t</mi><mimathvariant="normal">.</mi><mi>I</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>a</mi><mi>l</mi><mi>i</mi><mi>t</mi><mi>y</mi><moseparator="true">,</mo><mi>p</mi><mi>u</mi><mi>r</mi><mi>c</mi><mi>h</mi><mi>a</mi><mi>s</mi><mi>e</mi><mi>r</mi><mi>s</mi><mi>o</mi><mi>f</mi><mi>t</mi><mi>e</mi><mi>n</mi><mostretchy="false">[</mo><mi>h</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>o</mi><mi>v</mi><mi>e</mi><mi>r</mi></mrow><annotationencoding="application/x−tex">andinreturnreceivesaproductthattheyownandcanuseastheyseefit.Inreality,purchasersoften[handover</annotation></semantics></math><spanclass="katex−html"aria−hidden="true"><spanclass="base"><spanclass="strut"style="height:1em;vertical−align:−0.25em;"><spanclass="mordmathnormal">an<spanclass="mordmathnormal">d<spanclass="mordmathnormal">in<spanclass="mordmathnormal">re<spanclass="mordmathnormal">t<spanclass="mordmathnormal">u<spanclass="mordmathnormal"style="margin−right:0.02778em;">r<spanclass="mordmathnormal">n<spanclass="mordmathnormal">rece<spanclass="mordmathnormal">i<spanclass="mordmathnormal"style="margin−right:0.03588em;">v<spanclass="mordmathnormal">es<spanclass="mordmathnormal">a<spanclass="mordmathnormal">p<spanclass="mordmathnormal">ro<spanclass="mordmathnormal">d<spanclass="mordmathnormal">u<spanclass="mordmathnormal">c<spanclass="mordmathnormal">tt<spanclass="mordmathnormal">ha<spanclass="mordmathnormal">tt<spanclass="mordmathnormal">h<spanclass="mordmathnormal">eyo<spanclass="mordmathnormal"style="margin−right:0.02691em;">w<spanclass="mordmathnormal">nan<spanclass="mordmathnormal">d<spanclass="mordmathnormal">c<spanclass="mordmathnormal">an<spanclass="mordmathnormal">u<spanclass="mordmathnormal">se<spanclass="mordmathnormal">a<spanclass="mordmathnormal">s<spanclass="mordmathnormal">t<spanclass="mordmathnormal">h<spanclass="mordmathnormal">eysee<spanclass="mordmathnormal"style="margin−right:0.10764em;">f<spanclass="mordmathnormal">i<spanclass="mordmathnormal">t<spanclass="mord">.<spanclass="mordmathnormal"style="margin−right:0.07847em;">I<spanclass="mordmathnormal">n<spanclass="mordmathnormal">re<spanclass="mordmathnormal">a<spanclass="mordmathnormal"style="margin−right:0.01968em;">l<spanclass="mordmathnormal">i<spanclass="mordmathnormal">t<spanclass="mordmathnormal"style="margin−right:0.03588em;">y<spanclass="mpunct">,<spanclass="mspace"style="margin−right:0.1667em;"><spanclass="mordmathnormal">p<spanclass="mordmathnormal">u<spanclass="mordmathnormal">rc<spanclass="mordmathnormal">ha<spanclass="mordmathnormal">serso<spanclass="mordmathnormal"style="margin−right:0.10764em;">f<spanclass="mordmathnormal">t<spanclass="mordmathnormal">e<spanclass="mordmathnormal">n<spanclass="mopen">[<spanclass="mordmathnormal">han<spanclass="mordmathnormal">d<spanclass="mordmathnormal">o<spanclass="mordmathnormal"style="margin−right:0.03588em;">v<spanclass="mordmathnormal"style="margin−right:0.02778em;">er<math xmlns="http://www.w3.org/1998/Math/MathML" display="block"><semantics><mrow><mi>a</mi><mi>n</mi><mi>d</mi><mi>i</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>t</mi><mi>u</mi><mi>r</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>c</mi><mi>e</mi><mi>i</mi><mi>v</mi><mi>e</mi><mi>s</mi><mi>a</mi><mi>p</mi><mi>r</mi><mi>o</mi><mi>d</mi><mi>u</mi><mi>c</mi><mi>t</mi><mi>t</mi><mi>h</mi><mi>a</mi><mi>t</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>o</mi><mi>w</mi><mi>n</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>c</mi><mi>a</mi><mi>n</mi><mi>u</mi><mi>s</mi><mi>e</mi><mi>a</mi><mi>s</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>s</mi><mi>e</mi><mi>e</mi><mi>f</mi><mi>i</mi><mi>t</mi><mi mathvariant="normal">.</mi><mi>I</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>a</mi><mi>l</mi><mi>i</mi><mi>t</mi><mi>y</mi><mo separator="true">,</mo><mi>p</mi><mi>u</mi><mi>r</mi><mi>c</mi><mi>h</mi><mi>a</mi><mi>s</mi><mi>e</mi><mi>r</mi><mi>s</mi><mi>o</mi><mi>f</mi><mi>t</mi><mi>e</mi><mi>n</mi><mo stretchy="false">[</mo><mi>h</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>o</mi><mi>v</mi><mi>e</mi><mi>r</mi></mrow><annotation encoding="application/x-tex">and in return receives a product that they own and can use as they see fit. In reality, purchasers often [hand over</annotation></semantics></math>andinreturnreceivesaproductthattheyownandcanuseastheyseefit.Inreality,purchasersoften[handover<spanclass="katex−display"><spanclass="katex"><spanclass="katex−mathml"><mathxmlns="http://www.w3.org/1998/Math/MathML"display="block"><semantics><mrow><mi>a</mi><mi>n</mi><mi>d</mi><mi>i</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>t</mi><mi>u</mi><mi>r</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>c</mi><mi>e</mi><mi>i</mi><mi>v</mi><mi>e</mi><mi>s</mi><mi>a</mi><mi>p</mi><mi>r</mi><mi>o</mi><mi>d</mi><mi>u</mi><mi>c</mi><mi>t</mi><mi>t</mi><mi>h</mi><mi>a</mi><mi>t</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>o</mi><mi>w</mi><mi>n</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>c</mi><mi>a</mi><mi>n</mi><mi>u</mi><mi>s</mi><mi>e</mi><mi>a</mi><mi>s</mi><mi>t</mi><mi>h</mi><mi>e</mi><mi>y</mi><mi>s</mi><mi>e</mi><mi>e</mi><mi>f</mi><mi>i</mi><mi>t</mi><mimathvariant="normal">.</mi><mi>I</mi><mi>n</mi><mi>r</mi><mi>e</mi><mi>a</mi><mi>l</mi><mi>i</mi><mi>t</mi><mi>y</mi><moseparator="true">,</mo><mi>p</mi><mi>u</mi><mi>r</mi><mi>c</mi><mi>h</mi><mi>a</mi><mi>s</mi><mi>e</mi><mi>r</mi><mi>s</mi><mi>o</mi><mi>f</mi><mi>t</mi><mi>e</mi><mi>n</mi><mostretchy="false">[</mo><mi>h</mi><mi>a</mi><mi>n</mi><mi>d</mi><mi>o</mi><mi>v</mi><mi>e</mi><mi>r</mi></mrow><annotationencoding="application/x−tex">andinreturnreceivesaproductthattheyownandcanuseastheyseefit.Inreality,purchasersoften[handover</annotation></semantics></math><spanclass="katex−html"aria−hidden="true"><spanclass="base"><spanclass="strut"style="height:1em;vertical−align:−0.25em;"><spanclass="mordmathnormal">an<spanclass="mordmathnormal">d<spanclass="mordmathnormal">in<spanclass="mordmathnormal">re<spanclass="mordmathnormal">t<spanclass="mordmathnormal">u<spanclass="mordmathnormal"style="margin−right:0.02778em;">r<spanclass="mordmathnormal">n<spanclass="mordmathnormal">rece<spanclass="mordmathnormal">i<spanclass="mordmathnormal"style="margin−right:0.03588em;">v<spanclass="mordmathnormal">es<spanclass="mordmathnormal">a<spanclass="mordmathnormal">p<spanclass="mordmathnormal">ro<spanclass="mordmathnormal">d<spanclass="mordmathnormal">u<spanclass="mordmathnormal">c<spanclass="mordmathnormal">tt<spanclass="mordmathnormal">ha<spanclass="mordmathnormal">tt<spanclass="mordmathnormal">h<spanclass="mordmathnormal">eyo<spanclass="mordmathnormal"style="margin−right:0.02691em;">w<spanclass="mordmathnormal">nan<spanclass="mordmathnormal">d<spanclass="mordmathnormal">c<spanclass="mordmathnormal">an<spanclass="mordmathnormal">u<spanclass="mordmathnormal">se<spanclass="mordmathnormal">a<spanclass="mordmathnormal">s<spanclass="mordmathnormal">t<spanclass="mordmathnormal">h<spanclass="mordmathnormal">eysee<spanclass="mordmathnormal"style="margin−right:0.10764em;">f<spanclass="mordmathnormal">i<spanclass="mordmathnormal">t<spanclass="mord">.<spanclass="mordmathnormal"style="margin−right:0.07847em;">I<spanclass="mordmathnormal">n<spanclass="mordmathnormal">re<spanclass="mordmathnormal">a<spanclass="mordmathnormal"style="margin−right:0.01968em;">l<spanclass="mordmathnormal">i<spanclass="mordmathnormal">t<spanclass="mordmathnormal"style="margin−right:0.03588em;">y<spanclass="mpunct">,<spanclass="mspace"style="margin−right:0.1667em;"><spanclass="mordmathnormal">p<spanclass="mordmathnormal">u<spanclass="mordmathnormal">rc<spanclass="mordmathnormal">ha<spanclass="mordmathnormal">serso<spanclass="mordmathnormal"style="margin−right:0.10764em;">f<spanclass="mordmathnormal">t<spanclass="mordmathnormal">e<spanclass="mordmathnormal">n<spanclass="mopen"><spanclass="mordmathnormal">han<spanclass="mordmathnormal">d<spanclass="mordmathnormal">o<spanclass="mordmathnormal"style="margin−right:0.03588em;">v<spanclass="mordmathnormal"style="margin−right:0.02778em;">er and find that the product they purchased is still in the grips of the company that took their money but seems loathe to honor its end of the deal.

Case in point #38,909: guess what NVIDIA thinks is a “bug,” not a “feature.”

Starting with the Fermi drivers, though, a software overclock was possible in the drivers, which allowed you to adjust your laptop GPU’s clockspeeds at will. Tools like AfterBurner from Micro-Star International Comp., Ltd. and Turbomaster by ASUSTek Computer Inc. allowed users to more easily and safely tweak their GPU’s clockspeeds on select gaming laptops with cooling solutions designed to cope with the higher thermal load. Companies like the Clevo Comp., Sager, ASUS, MSI, and Dell’s Alienware regularly sold models billing overclockability as a sales feature.

What OEMs apparently didn’t expect was that NVIDIA would rob customers of that feature. But that appears to be precisely what happened.

NVIDIA pushed out new drivers last December that took away customers’ ability to overclock their cards. These were targeted at cards for mobile and hybrid devices, where the chance of overheating (and causing serious damage) was more pronounced. Those who had overclocked their cards but now were unable to do so demanded answers from the manufacturer. And wouldn’t you know it, the explanation for NVIDIA’s removal of this option cites “safety” as the primary motivator.

Unfortunately GeForce notebooks were not designed to support overclocking. Overclocking is by no means a trivial feature, and depends on thoughtful design of thermal, electrical, and other considerations. By overclocking a notebook, a user risks serious damage to the system that could result in non-functional systems, reduced notebook life, or many other effects.

There was a bug introduced into our drivers which enabled some systems to overclock. This was fixed in a recent update. Our intent was not to remove features from GeForce notebooks, but rather to safeguard systems from operating outside design limits.

“Safeguard systems from operating outside design limits” sounds an awful lot like “your purchased items are only as flexible as we allow them to be.” Sure, warranty departments handling burnt up/out devices may have been making some noise about dealing with the aftereffects of careless overclocking, but if so, they’re no less blameless than NVIDIA. Overclocking is generally one of those warranty-voiding activities, and if companies didn’t want to be replacing torched devices, they should have handled it better at their end. (And, as Daily Tech points out, they should probably stop advertising overclocking as a “feature” if it’s truly that much trouble in the warranty department.)

But NVIDIA’s action takes the purchased product out of paying customers’ hands. Most people who dabble in overclocking are technically adept and know the limits of their hardware (and the terms of their warranties). There will always be those who push too far or get in over their heads, and a few overclockers who disingenuously expect the device’s manufacturer to bail them out when things go wrong, but these customers are in the minority.

When a company takes away a feature (especially one that has been advertised by the devices’ manufacturers) and calls it a “bug,” it’s basically telling customers that they won’t ever own what they purchased. In this case, NVIDIA is hurting some of its most loyal customers — people who know their devices inside and out and will pay good money to stay ahead of the tech curve.

And NVIDIA’s being a bit disingenuous itself. It calls overclocking a “bug” when explaining why it took this feature away. But if it truly was a bug, why didn’t it issue a patch rather than eliminating the option? The obvious answer is that overclocking is no bug and NVIDIA knows it. But it has apparently chosen to placate its OEMs at the expense of some of its most reliable customers.

NVIDIA hasn’t issued any further statements on its “bug fix,” so it’s safe to assume it doesn’t really care whether it’s angered a number of its customers. Its position in the graphics accelerator market is virtually unassailable, especially in the area (mobile/hybrid) where it has just guaranteed its customers will get less product than they paid for.

Filed Under: bug, feature, overclocking, ownership, video chips
Companies: nvidia

DailyDirt: Lies My Computer Told Me…

from the urls-we-dig-up dept

We trust automated solutions to perform all kinds of critical tasks, but how often do we verify that we’re actually getting the right results? We survived the Y2K bug, but there are plenty of other examples of software and hardware flaws that could be much more (deadly) serious. Here are just a few disturbing computer glitches that you might have missed.

Recently, it’s been discovered that some Xerox machines don’t make exact copies, and in an effort to “clean up” images, they can introduce egregious errors that can swap numbers. The scary thing about this is that you might never notice that the photocopier changed your numbers around for you…. #youonlyhadonejob! [url]
Intel sold millions of defective Pentium chips that didn’t quite perform calculations correctly, and a math professor (Thomas Nicely) discovered the problem while he was working on a computational number theory project. Intel ultimately recalled the processors, but it publicly stated that the flaw would only affect a typical PC user with a spreadsheet less than 1 time every 27,000 years. [url]
In the mid-1980s, the Therac-25 medical accelerator had a software problem that killed at least 5 people and others were seriously injured from radiation overexposure. A race condition in the Therac-25’s operating system that allowed the device to turn on an electron beam even when its metal X-ray target was out of position. [url]

If you’d like to read more awesome and interesting stuff, check out this unrelated (but not entirely random!) Techdirt post via StumbleUpon.

Filed Under: bug, computer, defective, error, flaw, glitch, mistake, pentium bug, photocopier, race condition, software, therac-25, thomas nicely, y2k
Companies: intel, xerox

Apple Takes Credit For 'Uncovering' Its Patented Location 'Bug' That Isn't Really Tracking You, But Which It'll Fix

from the reality-distortion dept

Apple and Steve Jobs are semi-famous for the “reality distortion field” that sometimes comes with Apple product announcements. But can it do the same when it screws up. It took a week after the kerfuffle last week concerning iPhones and iPads storing your location for Apple to finally respond, and the full response is an amusing study in corporate doublespeak.

As far as I can tell, Apple’s key points are:

Apple (not researchers, or tons of other people who have noted this “bug” for a year or so) “discovered” a bug with location data on the phone:

The reason the iPhone stores so much data is a bug we uncovered and plan to fix shortly
There’s no tracking going on. There’s nothing to see here.

Apple is not tracking the location of your iPhone. Apple has never done so and has no plans to ever do so.
Even though there’s no tracking and nothing to see here, it’s still a bug which will be fixed.
The reason people are concerned about this is because people are confused.

Got that? People are confused and there’s nothing to see here, but Apple has discovered a minor bug which will be fixed.

Oh, and did we mention that Apple has also applied for a patent on this particular “bug”?

Filed Under: bug, ipad, iphone, location, patents, privacy, tracking
Companies: apple

How Many Websites Have Totally Bogus Traffic Numbers Due To Facebook Bug?

from the just-wondering... dept

For a while now, we’ve heard of websites claiming that they now get a ridiculous amount of referral traffic from Facebook. We’ve certainly noticed that we get a decent amount of traffic from Facebook, but it’s rarely in the top five sites for referrals. For a while, I’ve just wondered if people just don’t like to pass around our stuff on Facebook (as opposed to Twitter, which does drive lots of traffic — or if, perhaps, we didn’t do enough to encourage people to follow our Facebook page). However, something odd happened a couple weeks ago. All of a sudden, we noticed a ton of traffic coming from Facebook. Before noon, we’d already passed a normal day’s worth of traffic, and by the afternoon, we were on track to more than triple a standard day’s page views. But, then we noticed a few oddities. First, a lot of the traffic was going to relatively old stories. Second, doing a search on Facebook didn’t turn up anyone linking to those stories. Third, and most importantly, looking at the number of unique visitors, as opposed to pageviews, showed that those were more or less in line with a standard day’s traffic. Clearly something was off.

I started chatting with a few folks about it, and Marcus Carab pointed us to information on a Facebook bug that’s been around for about a year, in which Facebook’s “like” button adds a string (fb_xd_fragment, for those who are curious) to the URL that leads to a blank page… often causing multiple pageviews. There are workarounds, though it’s stunning that Facebook — which is pushing use of the “like” button all over the place — has not implemented its own fix. By that evening we’d installed a workaround, redirecting the bogus links to legitimate links, and stopping some of the false reloads. Yet, over the next few days, we noticed that even when we fixed that “known” problem, we were still seeing a hell of a lot more traffic from Facebook than made sense or that we had seen before.

Eventually, we used the referrer URL (www.facebook.com/plugins/like.php?….) to track it down to a problem with the way Facebook’s “like” button behaves when our pages are accessed with IE7 (and possibly IE6). Something in the button basically goes into a loop and just keeps requesting the page that it is on — essentially, repeatedly “reloading.” This makes page views shoot up like crazy. Because of this, if you visit our page with IE, we no longer show you a “like” button. Since doing so, our pageview numbers have returned to expected levels. (For our IE users, now that we’ve confirmed that the problem was the like button on IE, we plan to try an alternative implementation of the like button to see if that avoids the problem.)

Apparently, we’re not alone. Other sites also just noticed that they were dealing with similar issues and put in place similar workarounds.

But here’s the question: how many people don’t realize that these Facebook bugs exist, and are happily lapping up the not-really-there pageviews and reporting them as legit? I would guess that many people who are recipients of such a traffic deluge honestly don’t realize that it’s a bug and that the traffic is phantom traffic. But it wouldn’t surprise me if a few sites are simply happy for any way to “juice” their numbers. Over the years there have been a few big cases of newspaper circulation scandals. It kind of makes you wonder when we’ll start to see something similar with websites that report fake numbers concerning their traffic?

Of course, for us, being honest probably costs us money. Since many ad campaigns work on a page view (CPM) basis, if we can report triple our existing page views, that certainly would boost our ad revenue. But it’s also incredibly dishonest, and, for those who know this is happening, potentially fraud. It seems like only a matter of time until we hear about sites purposely leveraging such things for their own advantage.

Filed Under: bug, like, traffic, web traffic
Companies: facebook

Bizarre Amazon Password Bug: Ignores Everything After 8th Character On Some Old Passwords

from the passwordblahblah dept

The folks over at Consumerist do a nice job summarizing a weird bug in some old Amazon passwords that was discovered and discussed on Reddit. For whatever reason, on some “older” passwords, Amazon apparently ignores anything past the 8th character in your password. That is, if your password was password123, anything that has those first eight letters — “password” — will work. So, just plain old “password.” Or “passwordblahblahblah.” Of course, this can make it much easier to crack certain Amazon passwords. In looking at why this happens, it sounds like Amazon used to use an old hashing technique that would truncate input to just 8 characters. At some point, Amazon caught up to modern technology and changed this, but for old passwords, it only had the hash for those first 8 characters, and had no way to recreate the “full” password. For users, the fix is just to update your old password, but for folks who have kept passwords that long, it seems like it may be difficult to get them to update their passwords without Amazon prompting them to do so.

Filed Under: bug, hash, passwords
Companies: amazon

Multitasking Is Our Main Activity

from the learn-to-love-it dept

Earlier this year, I wrote a post questioning whether the “inefficiency” found in multitasking was a bug or a feature. It was in response to studies pointing out that people who multitask tend to be less efficient at specific tasks. Folks like Nick Carr like to hold up things like that as examples of how modern technology makes us dumber, but more and more people are questioning that concept. While this is from a few months ago, Kevin Donovan points us an excellent piece by economist Tyler Cowen that challenges the concept that internet multitasking is a problem. In it, he makes a key point:

Multitasking is not a distraction from our main activity, it is our main activity.

That’s a nicer way of saying what we said a few months ago. The “inefficiencies” from multitasking aren’t a bug. They’re a feature. Cowen goes on to explain it using the analogy of a long distance relationship compared to a stable marriage:

A long-distance relationship is, in emotional terms, a bit like culture in the time of Cervantes or Mozart. The costs of travel and access were high, at least compared to modern times. When you did arrive, the performance was often very exciting and indeed monumental. Sadly, the rest of the time you didn’t have that much culture at all. Even books were expensive and hard to get. Compared to what is possible in modern life, you couldn’t be as happy overall but your peak experiences could be extremely memorable, just as in the long-distance relationship.

Now let’s consider how living together and marriage differ from a long-distance relationship. When you share a home, the costs of seeing each other are very low. Your partner is usually right there. Most days include no grand events, but you have lots of regular and predictable interactions, along with a kind of grittiness or even ugliness rarely seen in a long-distance relationship. There are dirty dishes in the sink, hedges to be trimmed, maybe diapers to be changed.

If you are happily married, or even somewhat happily married, your internal life will be very rich. You will take all those small events and, in your mind and in the mind of your spouse, weave them together in the form of a deeply satisfying narrative, dirty diapers and all. It won’t always look glorious on the outside, but the internal experience of such a marriage is better than what’s normally possible in a long-distance relationship.

The same logic applies to culture. The Internet and other technologies mean that our favorite creators, or at least their creations, are literally part of our daily lives. It is no longer a long-distance relationship. It is no longer hard to get books and other written material. Pictures, music, and video appear on command. Culture is there all the time, and you can receive more of it, pretty much whenever you want.

In short, our relationship to culture has become more like marriage in the sense that it now enters our lives in an established flow, creating a better and more regular daily state of mind. True, culture has in some ways become uglier, or at least it would appear so to the outside observer. But when it comes to how we actually live and feel, contemporary culture is more satisfying and contributes to the happiness of far more people. That is why the public devours new technologies that offer extreme and immediate access to information.

Many critics of contemporary life want our culture to remain like a long-distance relationship at a time when most of us are growing into something more mature. We assemble culture for ourselves, creating and committing ourselves to a fascinating brocade. Very often the paper-and-ink book is less central to this new endeavor; it’s just another cultural bit we consume along with many others. But we are better off for this change, a change that is filling our daily lives with beauty, suspense, and learning.

The full piece is much longer, but beautifully written and quite convincing.

Filed Under: bug, efficiency, feature, multitasking, tyler cowen

Is The Inefficiency Of Multitasking A Bug Or A Feature?

from the questions-to-ponder... dept

There have been a bunch of studies recently claiming that multi-tasking and our constant use of technology harms our ability to concentrate or accomplish certain tasks. A recent example is a study claiming that so much tech usage is harming our ability to learn because kids can’t focus as much on long form work. Of course, I’m a bit skeptical of any such claims (almost all anecdotal) considering that actual studies have shown that kids read more books today than in the past. And, it’s not just kids. More people are reading books than in the past in the general population as well.

Still, there’s another argument to be made also, which reader JJ recently pointed out. Stowe Boyd notes that all of these types of studies miss the point, in that personal efficiency may be less important than being more interactive:

Perhaps what we are doing has nothing to do with efficiency. I don’t operate the way I do with the principal goal of speeding things up. My motivations are much more complex and diffused.

I don’t perceive what I am doing as multitasking, really. I am not trying to speed up how quickly I shift from one thing to another. Instead, I am involved in a stream of activities, in which other people figure prominently, either synchronously through direct discussion (a la Twitter or IM) or indirectly, through their writings and my responses.

In many cases, I leave activities dangling because I don’t know exactly how I feel about them. In some cases, I could resolve my feelings and take some action if I simply stopped other activities and focused solely on that activity, but in most cases that is not the case. And simply forcing myself to focus on the next thing in the activity would not lead to an acceptable or beneficial result, necessarily.

It’s like a painter with a number of works in process. My primary motivation is not getting a particular painting ‘done’, but adding dabs of paint that I feel are the right ones.

I honestly had never thought of it this way, and I’ll admit I’m not sure how I feel on this. But it is an interesting way of looking at such things. Obviously, in a work setting, personal productivity may matter. But, in general — just doing stuff online — is it a problem that we multitask? Or is that a feature?

Filed Under: bug, efficiency, feature, multitasking