Dear Hotels: Quit Being A-holes
Bob Frankston says connectivity will eventually become "ambient"—something we just assume, much as we assume electricity, water, sewage treatment and other infrastructural conveniences. None of those conveniences are free of cost, of course, and we pay for them one way or another. As utilities, it is normal for those paying for them to share reasonable use of them for free with others. Thus, we assume that, for example, a restroom in a hotel or gas station has a sink with running water, a light that goes on and a toilet that flushes. In less-developed parts of the world, or away from those conveniences, we make do with less, or on our own. But civilization requires that certain conveniences are available as a matter of course and are offered by those who pay for them directly as a simple grace to others.
This is not yet the case with Internet connectivity, especially in the hospitality industry.
I am facing this fact at the Novotel Lakeside, an otherwise fine hotel in Queenstown, New Zealand. Here my Internet connection is so sphinctered that all I can do is contemplate the problem at hand rather than the original subject of this month's column. I cannot continue writing about that subject because to do so would require that I use the Internet in a fully interactive way. What I have instead is a connection that has suddenly slowed to a tortuous crawl. This happened after the hotel cut me off and then offered to let me proceed at a slow pace or pay $.10/MB (or about $100/GB) for the full-speed connection I thought I would have for the 7GB that already cost me $115 at the start of my stay.
By that deal, I had seven days to use the 7GB, and up to four devices I could connect in my room, over Wi-Fi. I thought it was worth paying for, even though we were staying only for three days, and it was unlikely that we'd use 7GB of data. It also was the most expensive deal offered, so I thought it would cover the most use, with the most convenience. Instead, it was less a bait-and-switch than a bait-and-whack.
To get a sense of my frustration at the moment, consider what I am looking at right now on my screen (Figure 1).
Figure 1. Screenshot of Doc's Time and Data Remaining
The problem with his message is that 6,995.0MB is not what's remaining. That's how much I might now pay $.10/MB for, or $699.50 if I eat through the whole thing.
So, in my frustration and confusion, I just went down to the front desk, where they printed out a more readable form of this (Figure 2).
Figure 2. Screenshot from Doc's Hotel
(Note: I copied the screenshot shown in Figure 2 and inserted it later, when I had a better connection.)
Never mind the insanity of torturing customers with this strange mix of conditionalities. The market will fix that stuff eventually. (And I'll do my part with this column.) Think instead of negative vs. positive economic externalities.
On the negative side is the unlikelihood that I will ever stay in this hotel again—or in any other Accor Hotel, all of which, I gather, have the same aversive Internet offering. Also on the negative side, for the likes of Accor, is my preference these days to stay in AirBnB homes, for the simple reason that all of the ones I consider have good Internet connections, and none of them see their Internet connection as the digital equivalent of a pay toilet.
On the positive side, think about how Linux—and everything developed by geographically separated creators over the Internet—requires easily available and low-cost connections—and which then in turn produce even more products and services with positive economic externalities.
The main problem is that we're dealing with a new and awful norm here: metering the Internet as if it were an old-fashioned phone service.
Although not verbatim, both the hotel and the help desk on the phone told me "all the hotels work this way". It could be that that's true in New Zealand, although I doubt it. In the US and Europe, the expensive hotels are the ones with inconvenient connectivity deals (although I've seen none with data caps or metered usage). It's the cheap hotels that offer free Internet, just like they offer free electricity, heat, air conditioning and running water.
In the wired parts of the Internet, where we connect by Ethernet through fiber, cable TV or phone lines, we tend not to sense prices for sums of data, even if there are "caps" involved. Comcast, for example, has "flexible" terms surrounding its 250GB/month data caps. But in the wireless parts of the Net connected over 3G and 4G/LTE connections, the "caps" are very present and constantly threatening. They are also much lower than we see with wired, and with costs that are much higher. (See, for example, AT&T's and Verizon's plans.)
If we follow the model set by expensive hotels and mobile phone companies, the Net will turn into a complicated "service" on the model of phone and cable systems, rather than the much simpler model of pure utilities with boundless positive economic and social externalities, such as we have with electricity, water and sewage treatment. This is a huge fork in the road of the Net's future.
Back when he was Chief Scientist at BT, JP Rangaswami said the core competence of phone companies was not communications, but billing. As a group they are very successful at that. The result is what Scott Adams calls a "confusopoly": "a group of companies with similar products who intentionally confuse customers instead of competing on price". Confusopolies are very complicated shell games in which no customer can intuit, much less find, a first cost. Nor can they find any source of simplicity behind the baffling choices they face in what amounts to a captive marketplace. With real utilities, that first cost can be sensed. We can see in our minds the rivers, dams, lakes, power plants, distribution wires and sewage treatment facilities required. Those things may be complicated, but what they yield is simple, and we appreciate that simplicity and its pure usefulness.
The Internet should be the same way. But it won't get there as long as its plumbing providers care more about making billing complicated than making service simple.
And maybe, after we get that down, we can work on making it ambient as well.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Interview with Patrick Volkerding
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide