Archive for the ‘Web Basics’ Category

File Under: Web Basics

A Guide to Understanding Page-Speed Tests

Photo: tobias.munich/Flickr

Anyone who’s ever tried to optimize a website has faced the very basic question — how long does your site take to load?

The answer seems like it would be easy to discover: Load your site in a page speed crawler like WebPagetest and soon you’ll have your numbers. But that’s just it; you won’t have a number, you have numbers and figuring out which numbers to listen to is trickier than you might think.

Strangeloop’s Joshua Bixby recently tackled the performance metric question in a blog post titled a Non-Geeky Guide to Understanding Performance Measurement Terms. The whole article is well worth reading, but perhaps the best advice is to make a video of the page load. “If you want to get a ground-zero look at your site’s performance,” writes Bixby, “capturing videos and filmstrip views of your pages’ load times are one of the best ways to go.”

The filmstrip view Bixby refers to is part of the WebPagetest results and shows what the visitor sees in a progressive series of page captures. To create a filmstrip or video test of your website, head over to WebPagetest and select the “visual comparison” tab.

Some common performance mistakes Bixby cautions against include using “response time” and “load time” interchangeably and “not realizing that ‘response time’ can mean any number of completely different things.”

To help those unfamiliar with the nuances of loading metrics, Bixby then breaks down and defines all the terms, including what exactly is meant by “start render” or “time to first byte,” as well as some caveats to bear in mind when going over the numbers for your website.

While Bixby’s post can be extremely helpful, especially to those who are just starting out in the often confusing world of website optimization, bear in mind that testing sites like WebPagetest are no substitute for real-world tests. “As a matter of due course, you always need to gather large batches of data and rely on median numbers,” writes Bixby, “but you also need to periodically get under the hood and take a real-world look at how your pages behave for real users.”

File Under: Security, servers, Web Basics

Google, Microsoft, Yahoo, PayPal Go After Phishers With New E-Mail Authentication Effort

Major e-mail providers, including Google, Microsoft, and Yahoo are teaming up with PayPal, Facebook, LinkedIn, and more, to implement a new system for authenticating e-mail senders to try to prevent the sending of fraudulent spam and phishing messages.

The protocol that powers e-mail, SMTP, dates back to a more trusting era; a time when the only people who sent you e-mails were people you wanted to send you e-mails. SMTP servers are willing to accept pretty much any e-mail destined for a mailbox they know about (which is, admittedly, an improvement on how things used to be, when they’d accept e-mails even for mailboxes they didn’t know about), a fact which spammers and phishers exploit daily.

Making any fundamental changes to SMTP itself is nigh impossible; there are too many e-mail servers, and they all have to interoperate with each other, an insurmountable hurdle for any major change. So what we’re left with is all manner of additional systems that are designed to give SMTP servers a bit more information about the person sending the e-mail, so that they can judge whether or not they really want to accept the message.

The two main systems in use today are called SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). Both systems use DNS to publish extra information about the e-mail sender’s domain. SPF tells the receiving server which outgoing servers are allowed to send mail for a given domain; if the receiving server receives mail from a server not on the list, it should assume that the mail is fraudulent. DKIM embeds a cryptographic signature to e-mail messages and an indication of which DNS entry to examine. The receiving server can then look up the DNS entry and use the data it finds to verify the signature.

These systems are not perfect; though both are used widely, they haven’t been adopted universally. This means that some legitimate mail will arrive that doesn’t have SPF or DKIM DNS entries, and so mail servers can’t depend on its presence. Common legitimate operations can also break them; many mailing list programs add footers to messages, which will cause rejection by DKIM, and forwarding e-mails causes rejection by SPF. As a result, failing one or other test is not a good reason to reject a message.

These systems also make it hard to diagnose misconfigurations; receiving servers will typically just swallow or ignore mails sent by systems with bad SPF or DKIM configurations.

The large group of companies, which includes the biggest web mail servers and some of the most common corporate victims of phishing attempts, is proposing a new scheme, DMARC (“Domain-based Message Authentication, Reporting & Conformance”), in an attempt to tackle these problems. DMARC fills some of the gaps in SPF and DKIM, making them more trustworthy.

DMARC's position within the mail receipt process (illustration by dmarc.org)

DMARC is based on work done by PayPal in conjunction with Yahoo, and later extended to Gmail. This initial work resulted in a substantial reduction in the number of PayPal phishing attempts seen by users of those mail providers, and DMARC is an attempt to extend that to more organizations. As with SPF and DKIM, DMARC depends on storing extra information about the sender in DNS. This information tells receiving mail servers how to handle messages that fail the SPF or DKIM tests, and how critical the two tests are. The sender can tell recipient servers to reject messages that fail SPF and DKIM outright, to quarantine them somehow (for example, putting them into a spam folder), or to accept the mail normally and send a report of the failure back to the sender.

In turn, this makes SPF and DKIM much safer for organizations to deploy. They can start with the “notification” mode, confident that no mail will be lost if they have made a mistake, and use the information learned to repair any errors. DMARC also allows recipients to know if a domain should be using SPF and DKIM in the first place.

Without a global rollout, DMARC can’t solve all phishing and spam problems. The companies that have signed up to support the project include major recipients of phishing attempts—the various free e-mail providers—and sites against which phishing attacks are regularly made. Mail sent between the organizations will be verified using the SPF/DKIM/DMARC trifecta. Anyone using the major mail providers and the major services should see a substantial reduction in fraudulent mail. Senders and recipients who want to receive similar protection can implement DMARC themselves by following the specification that the DMARC group is working on.

Given the constraints imposed by SMTP, we may never get an e-mail system that is entirely free of malicious and annoying junk. SMTP e-mail was never designed to be trustworthy, and systems like SPF and DKIM are constrained by the inadequacies of SMTP’s design. Nonetheless, mechanisms such as DMARC can still make a big difference, and with the support of these major companies, e-mail might get that little bit safer.

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.

Illustration by dmarc.org

File Under: Web Basics

Mozilla Questions Web Orthodoxies With ‘Pancake’

Mozilla Labs has launched a new project designed to question the web as we know it, including what some might think of as the web’s sacred cows — like whether or not we need to see URLs.

Pancake, as the new project is known, will help Mozilla, “better understand what people do on the web, why and how they do those things, and how we can make those things easier and more efficient.” The goal of Pancake according to Mozilla’s new, awesomely titled Director of Pancake Stuart Parmenter, is to play with “huge concepts, monumental problems and occasionally crazy ideas.”

Among the ideas in Pancakes’ sights that many might consider crazy is questioning whether users need to care about the URL. Note that no one is questioning the URL itself, just whether or not the user needs to be concerned with it. Indeed Pancake won’t be the first time Mozilla has questioned whether or not the user needs to know about URLs, nor is Mozilla alone on that score, Google’s Chrome team has also experimented with hiding the URL bar.

Might there be some better means of letting the user know where they are, where a link leads and all the other things URLs currently do? That’s exactly the sort of question that Pancake wants to ask. We’ll never know the answer, and possibly never push the web in interesting new directions, if no one is asking the question.

If you consider the URL bar a sacred part of the web browser, fear not, no one is taking way your URL bar. The goal of Pancake is not to force anything down your throat, but to make the web better. That might mean, as Parmeter writes, “inventing new metaphors and new systems,” but the main goal of those new metaphors and systems is to “give users greater power and control within the modern web.”

In that sense it’s difficult to tell exactly what Mozilla plans to do with Pancake. In the immediate future Pancake will be rolling out its first prototype app, but the announcement is extremely vague about what that app might involve. Historically Labs projects are a very mixed bag. For every very successful Labs effort — like the syncing features that are now a standard part of Firefox — there are several others that have been quietly shelved (Ubiquity anyone? Prism?).

Pancake’s first prototype app — whatever it may be — will be released within the next few months. In the mean time you can check out the new wiki page or join the Pancake Google Group. All the other usual Labs pages — documentation, roadmap, designs and other content — will come in the weeks ahead.

File Under: Web Basics

Video: When We Build

The web is buzzing, and rightly so, about Wilson Miner’s incredibly inspiring talk from the 2011 Build Conference in Belfast. You may recognize Miner’s name from his role in developing Django, as part of the team that built Apple.com or as one of the founders of Everyblock.

Miner’s talk is not your typical web developer talk; in fact, he hardly mentions the web for most of it. Rather, Miner focuses on the broader impact that technologies, and the developers and designers who create them, have on our world, and how that world in turn shapes us. Miner reminds us that we aren’t building “just websites” but shaping the world we will live in for much of the foreseeable future. And, as the Alistair Smith quote shown in the talk says, “at times of change, the learners are the ones who will inherit the world, while the knowers will be beautifully prepared for a world which no longer exists.”

So turn off your music, throw the video in fullscreen mode and give it 38 minutes. Trust us, you won’t be sorry.

After you’re done be sure to visit Miner’s website, which has links to all the material used in the talk, including books, videos, music and images for anyone who would like to learn more.

File Under: Web Basics

The Disneyfication of Tech

Truth is this — users are caught between tech and media. Neither of them is looking out for our interest. Each of them own politicians each owns tech. The tech industry is better at tech (no surprise) and the media industry is better at a lot of other things, including getting Congress to do their bidding.

I’ve been warning the news publishers to be careful about viewing Twitter and Facebook as if they were equivalent to the web. This would be like Kodak trusting Apple to handle its digital photography strategy. We know now how that turned out.

Twitter and Facebook are rich and getting richer. Either of them could easily buy a struggling but independent news organization. Then where would you be if you were dependent on them to distribute news? It would be like the Times depending on Murdoch to print their daily paper. Instead the Times invested in their own printing plant, presumably so they could have better control of the product, both from a creative and tactical standpoint. If Murdoch owned the presses and the trucks, who do you think would deliver the most timely news? They have to think about Twitter that way. At some point they will come to see themselves as a media company, if they don’t already.

Caught in the middle is the original idea of the Internet and the web, that people could be media instead of just consuming it. For that to continue, enough people have to see their future as publishing independently, and enough people have to read independently of corporate media, neither originating from Silicon Valley or Hollywood, to keep the flame alive.

I still hope that there’s a remnant of the idealism of tech. That there was value in the personal-ness of PCs. The net is the same way. We need to make it ever-easier for people to own and run their own infrastructure. People think it’s hard, but it doesn’t have to be! Each of us can have the equivalent of a printing plant, that’s the magic of tech. No harder to keep running than a laptop. To those people in tech who still hold to the ideal of free communication unrestricted by government or corporations, please use some of your profits to help guarantee the future of an independent Internet.

Otherwise, I think we can all see this clearly now, the net will be a single amorphous Disneyfied mess, not too far down the road.

This post first appeared on Scripting News.

Dave Winer, a former researcher at NYU and Harvard, pioneered the development of weblogs, syndication (RSS), podcasting, outlining, and web content management software. A former contributing editor at Wired magazine, Dave won the Wired Tech Renegade award in 2001.
Follow @davewiner on Twitter.
File Under: search, Web Basics

See the World Through the Eyes of Google Images

Dutch artist Sebastien Schmieg has elevated the Google Image search from its humble intent, creating a short film that strings together a series of image searches. The result oscillates between the prosaic and profound, and feels more like a grand homage to humanity than a collection of random images.

To create the image sequence Schmieg fed a single transparent PNG into Google Images and used the “visually similar” feature to recursively loop through the results. Schmieg’s movie of the results, entitled Search by Image, Recursively, Transparent PNG, #1, is a (slightly NSFW) truly hypnotic, algorithmic tour of life as Google Images knows it.

In all there are some 2,951 images in the video. The “visually similar” option in Google Image Search tends to get stuck in loops using it the way Schmieg did so if an image had already been used in the sequence, he would skip to the next image in the results. But otherwise the sequence is entirely algorithmic. Beware pareidolia.

For more info about the movie and some other, similar efforts, be sure to check out Schmieg’s website.

File Under: Web Basics

Protesting SOPA: How to Make Your Voice Heard

This week, “call your Congressperson” is not just a cliché. It’s one of the most important things you can do to make your voice heard.

As Ars readers know, Wikipedia, reddit, Craigslist, and others are blacking out their sites today in protest of the Stop Online Piracy Act (SOPA) and Protect IP Act (PIPA), antipiracy bills that protestors believe would give far too much power to rightsholders at the expense of the Internet as a whole.

Members of Congress are already backpedaling on some of the provisions in SOPA and PIPA, and Rep. Darrell Issa (R-CA) said Tuesday that he expects to have more co-sponsors for his alternative (and much saner) OPEN Act than “than SOPA has in the House.”

SOPA opponents say it is critical to block the bill now, because if it is turned into law website owners will be at risk of having payments blocked, or forced into lengthy and expensive litigation even if they’re not trying to enable piracy or profit from it.

“Scribd could not have come into existence in a world governed by SOPA,” said Scribd co-founder Jared Friedman during a conference call yesterday. Alexis Ohanian, co-founder of reddit (which shares a parent company with Ars Technica), said much the same thing about Internet entrepreneurs. “I’d hate to be the Congressperson who has to go back to his or her district and say, ‘You know what, maybe this is not the industry for you. Maybe you can try your luck in Canada.’”

Video hosting site Veoh found out the hard way what litigation can do to an Internet business, even when the law is on your side. Veoh was “litigated to death” before being finally cleared in a lawsuit filed against the site by Universal Music Group. “The lawsuit dramatically impacted our company,” said founder Dmitry Shapiro. “It cost us millions of dollars to litigate. It took up a tremendous amount of executives’ time. More importantly, it dramatically demotivated our 120 employees who were constantly concerned about what this meant and what would happen to them and their families.”

Veoh’s defense, that it was eligible for safe harbor protection under the Digital Millennium Copyright Act, was upheld on appeal. But it was too late—Shapiro laid everyone off and sold the company in a fire sale.

Friedman said he’s grateful to Shapiro, because Veoh’s “success” in defending itself helped Scribd fend off its own legal threats. But SOPA would weaken safe harbor protections and give copyright owners a “private right of action” to go after money and ad networks, making it even more difficult for future Veohs to gain traction.

You don’t have to be a digital pirate to oppose SOPA, Issa added. “We don’t want people taking brand-new movies and putting them online and prospering while the actual creator of the art is denied,” Issa said. But OPEN, by focusing on the money supply through the International Trade Commission, would target the vast majority of abuses that SOPA intends to prevent without resorting to censorship, he argued. “We think we can do 80 percent of the good with almost no trauma.”

“It is a great time to contact your members of Congress, make sure they know there is an alternative, and that there is a reason to slow down and get it right,” Issa added.

Contact your senator or representative

Sending a message to our elected leaders’ underlings has never been easier. Old-fashioned phone calls count for a lot; they take effort to make, and so they indicate opposition in a way that a mass form e-mail never will. The official Senate site lists the phone numbers and links to contact forms for all senators, while the House has a handy tool that lets you search for your representative by ZIP code and state.

If you’re having trouble thinking of something to say, various anti-SOPA and anti-PIPA organizations can help. Public Knowledge has a form for sending letters to senators describing why PIPA is “overbroad … ripe for abuse … [and] speeds fragmentation of the Internet.” The Electronic Frontier Foundation is providing a similar service for contacting both senators and representatives, as is AmericanCensorship.org.

You can also sign several petitions. This one urges President Barack Obama to veto SOPA should it ever come to his desk and has more than 51,000 signatures; it led to the Obama administration criticizing portions of SOPA, saying that the administration “will not support legislation that reduces freedom of expression, increases cybersecurity risk, or undermines the dynamic, innovative global Internet.”

Another petition backed by Craigslist and reddit is aimed at Congress and has 117,000 supporters. Want to go further and convince your fellow humans that SOPA is bad? If you’re already an expert on SOPA or PIPA, another site lets you volunteer to to explain it to newbies on the phone or in person.

Black out your website

Many of you have your own personal websites. Just because you’re not as big as Wikipedia and reddit doesn’t mean you can’t join the blackout brigade or “SOPA strike,” as some are calling it. On GitHub, one SOPA opponent is providing HTML that can be used to change a website’s homepage to a black screen which lights up when you move your cursor over the middle, revealing a message of protest:

Your own website could look like this today—if you download a bit of code from GitHub

If you have a WordPress site, you can choose from several plugins to make your point, including one that lets you customize which dates the blackout message appears and whether users see it on only their first visit or on all visits. Widgets can also direct visitors to anti-SOPA or anti-PIPA petitions. For those who can’t or don’t want to go completely dark, there are “Stop PIPA” bars to put at the top of your site, while one “SEO-friendly” protest tool created by CloudFlare blacks out any word longer than five characters, making your site look like a redacted government document. Mucking with a site carries some danger of Google’s web-crawling bots not seeing it properly, but luckily a Google employee has posted a handy guide on what not to do.

Boycott SOPA supporters

If you’ve contacted your Congressperson, blacked out your website, and are still itching for more protest action, you can identify SOPA supporters and take the fight to them directly—or boycott their goods and services. One extension for Google Chrome, called No SOPA, warns you when you visit the website of a company that supports the legislation. “Boycott? Nasty letter time? You decide,” writes the maker of the extension.

There’s also quite an extensive list of SOPA supporters on the website of chief SOPA backer Rep. Lamar Smith (R-TX). (GoDaddy was removed from this list after it was the victim of a successful boycott of the company.)

The Internet speaks

“This is the first time we’ve seen an Internet-based action,” Ohanian said yesterday. “There were no leaders of this movement.” But people from numerous political persuasions lined up in agreement that “this was terrible legislation that looked a lot more like lobbyist dollars at work. If you don’t believe this is an election issue already, it is already happening.” In fact, several “real life” protests and rallies are happening today in the streets of San Francisco, New York City, Seattle and perhaps other cities. 

Just because SOPA and PIPA have plenty of opponents doesn’t mean they can’t pass. The bills still have sizable support from music and movie industry groups. Former US Senator Chris Dodd, now CEO of the Motion Picture Association of America, fired off a press release yesterday calling the SOPA blackout “yet another gimmick, albeit a dangerous one, designed to punish elected and administration officials who are working diligently to protect American jobs from foreign criminals.”

If you’re among those who disagree with Dodd, what are your plans now that SOPA blackout day is upon us? If you have any interesting protest ideas, feel free to share them in the comments.

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.

Protest SOPA: Black Out Your Website the Google-Friendly Way

On Wednesday Jan. 18, Reddit, Wikipedia and many other websites will black out their content in protest of the Stop Online Piracy Act (SOPA), the Protect Intellectual Property Act (PIPA) and the Online Protection and Enforcement of Digital Trade Act (OPEN). Organizers of the SOPA Strike are asking interested sites to black out their content for 12 hours and display a message encouraging users to contact their congressional representatives and urge them to oppose the legislation.

Although it was rumored that Google might join in the protest, that does not appear to be the case. The search giant does, however, have some advice for anyone who would like to black out their site and ensure that doing so doesn’t harm their Google search rank or indexed content. [Update: It appears Google will be participating in some fashion. A Google spokesperson tells Ars Technica that "tomorrow [Google] will be joining many other tech companies to highlight this issue on our U.S. home page.” WordPress and Scribd will also be participating. You can read the full story on Ars Technica.]

Writing on Google+, Google’s Pierre Far offers some practical tips in a post entitled, “Website Outages and Blackouts the Right Way.” The advice mirrors Google’s previous best practices for planned downtime, but warrants a closer look from anyone thinking of taking their site offline to protest the SOPA/PIPA/OPEN legislation.

Far’s main advice is to make sure that any URLs participating in the blackout return a HTTP 503 header. The 503 header will tell Google’s crawlers that your site is temporarily unavailable. That way your protest and blacked out website won’t affect your Google ranking nor will any protest content be indexed as part of your site. If you use Google’s Webmaster tools you will see crawler errors, but that’s what you want — your site to be unavailable, causing an error.

Implementing a 503 header page isn’t too difficult, though the details will vary according to which technologies power your site. If you’re using WordPress there’s a SOPA Blackout plugin available that can handle the blackout for you. It’s also pretty easy to create a 503 redirect at the server level. If you use Apache ensure that you have the Rewrite module installed and then add something like the following code to your root .htaccess file:

    RewriteRule .* /path/to/file/myerror503page.php

That will redirect your entire website to the 503 error page. Now just make sure that your myerror503page.php page returns a 503 error. Assuming you’re using PHP, something like this will do the trick:

    header('HTTP/1.1 503 Service Temporarily Unavailable');
    header('Retry-After: Thu, 19 Jan 2012 00:00:00 GMT');

For more details, be sure to read up on the HTTP 503 header and see the rest of Far’s Google+ post to learn how to handle robots.txt and a few things you should definitely not do (like change your robots.txt file to block Google for the day, which could mean Google will stay away for far more than just a day). Even if you aren’t planning to participate in the anti-SOPA blackout tomorrow, Far’s advice holds true any time you need to take some or all of your site offline — whether it’s routine server maintenance, rolling out an upgrade or as part of a political protest.

[Image by SOPAStrike.com]

Building a Responsive, Future-Friendly Web for Everyone

A handful of the many screens your site needs to handle. Photo: Ariel Zambelich/Wired.com

This week’s Consumer Electronics Show in Las Vegas has seen the arrival of dozens of new devices from tablets to televisions. Some of these newfangled gadgets will soon be in the hands of consumers who will use them to access your website. Will your site work? Or will it end up mangled by a subpar web browser, odd screen size or slow network connection?

No one wants to rewrite their website every time a new device or browser hits the web. That’s why approaches like responsive design, and the even broader efforts of the future-friendly group, are trying to develop tools and techniques for building adaptable websites. That way, when a dozen new tablets suddenly appear on the scene, you can relax knowing your site will look and perform as intended, no matter which devices your audience is using.

Even if you aren’t a gadget lover, CES should help drive home the fundamental truth of today’s web — devices, they are a comin’. Webmonkey has compiled helpful resources for creating responsive design in the past, but the field is new and evolving rapidly so here’s an updated list of links to help you get started responsive, future-friendly sites that serve your audience’s needs whether they’re browsing with a tiny phone, a huge television or the web-enabled toaster of tomorrow.

Basics:

  • Use @media to scale your layout for any screen, but remember that this alone isn’t really responsive design.
  • Use liquid layouts that can accommodate any screen size. Don’t simply design one look for 4-inch screens, one for 7-inch, one for 10-inch and one for desktop. Keep it liquid, otherwise what happens when the 11.4-inch screen suddenly becomes popular?
  • Roll your own grids based on the specifics of your site’s content. Canned grid systems will rarely fit the bill. The problem with canned grids is that they don’t fit your unique content. Create layouts from the content out, rather than the canvas (or grid) in.
  • Start small. Start with the smallest size screen and work your way up, adding @media rules to float elements into the larger windows of tablet and desktop browsers. Start with a narrow, single-column layout to handle mobile browsers and then scale up from there rather than the other way around. Starting with the smallest screen and working your way up means it’s the desktop browsers that need to handle @media, make sure older browsers work by using polyfills like Respond.
  • Forget Photoshop, build your comps in the browser. It’s virtually impossible to mock up liquid layouts in Photoshop, start in the browser instead.
  • Scale images using img { max-width: 100%; }. For very large images, consider using something like Responsive Images to offer the very smallest screens smaller image downloads and then use JavaScript to swap in larger images for larger screens. Similar techniques can be used to scale video.
  • Forget about perfect. If you haven’t already, abandon the notion of pixel perfect designs across devices. An iPad isn’t a laptop isn’t a television. Build the perfect site for each.

Further Reading:

  • Future Friendly — An overview of how some of the smartest people in web design are thinking about the ever-broadening reach of the web: “We can’t be all things on all devices. To manage in a world of ever-increasing device complexity, we need to focus on what matters most to our customers and businesses. Not by building lowest common-denominator solutions but by creating meaningful content and services. People are also increasingly tired of excessive noise and finding ways to simplify things for themselves. Focus your service before your customers and increasing diversity do it for you.”
  • Building a Future-Friendly Web — Brad Frost’s excellent advice: “Think of your core content as a fluid thing that gets poured into a huge number of containers.”
  • There is no mobile web — “There is no mobile web, nor desktop web. It is just the web. Start with the content and meet people halfway.”
  • Responsive by default — Andy Hume on why the web has always been responsive, but was temporarily sidetracked by the fad of fixed-width sites.
  • COPE: Create Once, Publish Everywhere — NPR’s Director of Application Development, Daniel Jacobson, walks through how NPR separates content from display and uses a single data source for all its apps, sites, APIs and feeds. A great example of what Frost talks about regarding content as a fluid thing.
  • Support Versus Optimization — It can seem daunting to support dozens of mobile browsers, but if you aren’t up to the challenge of a few mobile browsers now what are you going to do when you need to support car dashboards, refrigerators, televisions and toasters, all with dozens of varying browsers?
  • The Coming Zombie Apocalypse — Not satisfied thinking a few years ahead? Scott Jenson explores further into the future and tries to imagine what the web might look like when devices all but invisible.

Techniques:

File Under: Web Basics

The Un-Internet

The tech world is in an infinite loop.

I’ve written about it so many times, but that’s how it goes with loops. You don’t have to write original stuff more than once. Each time around the loop, at some point, everything comes back into style.

No need to list all the loops, other than to say Here We Go Again!

At issue is this: Control.

For whatever reason, the people who run the tech companies want it. But eventually the users take it.

I wrote in 1994, my first time as a chronicler of the loops: “The users outfoxed us again. It happens every fifteen years or so in this business, We lost our grounding, the users rebelled, and a new incarnation of the software business has been created.”

In the same 1994 piece: “Once the users take control, they never give it back.”

You can see it playing out in the Twitter community, and now the Tumblr community.

It isn’t a reflection on the moral quality of the leaders of the companies, to want to control their users. But it’s a short-term proposition at best. Either the companies learn how to take the lead from their users, or they will be sidelined. Unless the laws of technology are repealed, and I don’t think laws like that can be repealed.

Lest you think I was smart enough to see this coming in my own early experience as a tech entrepreneur, I wasn’t. We were scared of software piracy, didn’t understand how we could continue to be in business with software that could be easily copied. So we established controls that made it difficult for non-technical users to copy the software. That created a market of other software that would copy our software. So it was reduced down to whether or not the users would knowingly do something we disapproved of. Many of our users were honorable, they did what I would have done in their place. They stopped using our products. I would regularly receive letters from customers, people who had paid over $200 for the disks our software came on, with the disks cut in half with a scissor. These letters made their point loud and clear. One day everyone took off their copy protection, and the users got what they wanted. I came to believe then that this is always so.

This time around, Apple has been the leader in the push to control users. They say they’re protecting users, and to some extent that is true. I can download software onto my iPad feeling fairly sure that it’s not going to harm the computer. I wouldn’t mind what Apple was doing if that’s all they did, keep the nasty bits off my computer. But of course, that’s not all they do. Nor could it be all they do. Once they took the power to decide what software could be distributed on their platform, it was inevitable that speech would be restricted too. I think of the iPad platform as Disneyfied. You wouldn’t see anything there that you wouldn’t see in a Disney theme park or in a Pixar movie.

The sad thing is that Apple is providing a bad example for younger, smaller companies like Twitter and Tumblr, who apparently want to control the “user experience” of their platforms in much the same way as Apple does. They feel they have a better sense of quality than the randomness of a free market. So they’ve installed similar controls. Your content cannot be displayed by Twitter unless you’re one of their partners. How you get to be a partner is left to your imagination. We have no visibility into it.

Tumblr has decided that a browser add-on is unwelcome. Presumably it’s only an issue because a fair number of their users want to use it. So they are taking issue not only with the developer, but with the users. They have admitted that the problem is that they must “educate” their users better. Oy! Does this sound familiar. In the end, it will be the other way around. It has to be. It’s the lesson of the Internet.

My first experience with the Internet came as a grad student in the late 70s, but it wasn’t called the Internet then. I loved it because of its simplicity and the lack of controls. There was no one to say you could or couldn’t ship something. No gatekeeper. In the world it was growing up alongside, the mainframe world, the barriers were huge. An individual person couldn’t own a computer. To get access you had to go to work for a corporation, or study at a university.

Every time around the loop, since then, the Internet has served as the antidote to the controls that the tech industry would place on users. Every time, the tech industry has a rationale, with some validity, that wide-open access would be a nightmare. But eventually we overcome their barriers, and another layer comes on. And the upstarts become the installed-base, and they make the same mistakes all over again.

It’s the Internet vs the Un-Internet. And the Internet, it seems, always prevails.

Photo: Benoit/Flickr

This post first appeared on Scripting News.

Dave Winer, a visiting scholar at NYU’s Arthur L. Carter Journalism Institute, pioneered the development of weblogs, syndication (RSS), podcasting, outlining, and web content management software. A former contributing editor at Wired Magazine, Dave won the Wired Tech Renegade award in 2001.
Follow @davewiner on Twitter.