Slashdot Mirror

WebMink writes "In an interview at OSCON, Mark Shuttleworth of Canonical spoke about the vision behind the Ubuntu Edge phone as a concept device to test features the mobile industry is too conservative to try. Notably, he agreed with the Free Software Foundation's demands that the device should carry no proprietary software and have Free drivers (transcript): '... we'll ship this with Android and Ubuntu, no plans to put proprietary applications on it. We haven't finalized the silicon selection so we're looking at the next generation silicon from all major vendors. I would like to ship it with all Free drivers.'" Although not a hard promise, it is a promising development.

theodp writes "In the movie Groundhog Day, a weatherman finds himself living the same day over and over again. It's a tale to which software-designers-of-a-certain-age can relate. Like Philip Greenspun, who wrote in 1999, 'One of the most painful things in our culture is to watch other people repeat earlier mistakes. We're not fond of Bill Gates, but it still hurts to see Microsoft struggle with problems that IBM solved in the 1960s.' Or Dave Winer, who recently observed, 'We marvel that the runtime environment of the web browser can do things that we had working 25 years ago on the Mac.' And then there's Scott Locklin, who argues in a new essay that one of the problems with modern computer technology is that programmers don't learn from the great masters. 'There is such a thing as a Beethoven or Mozart of software design,' Locklin writes. 'Modern programmers seem more familiar with Lady Gaga. It's not just a matter of taste and an appreciation for genius. It's a matter of forgetting important things.' Hey, maybe it's hard to learn from computer history when people don't acknowledge the existence of someone old enough to have lived it, as panelists reportedly did at an event held by Mark Zuckerberg's FWD.us last Friday!"

c0d3g33k writes "Prompted by the addition of new security features in Android 4.3 that limit the effectiveness of elevated privileges, Steve Kondik wonders which uses really require full root. Most common activities that prompt owners to root their devices (backup/restore tools, firewall/DNS resolver management, kernel tuning), could be accomplished without exposing root, argues Kondik, by providing additional APIs and extensions to the user. This would improve security by limiting the exposure of the system to exploits. Reasonable enough, on the face of it. The title of the post, however, suggests that Kondik believes that eventually all useful activities can be designed into the system so the 'dangerous and insecure' abilities provided by root/administrator privileges aren't needed. This kind of top-down thinking seems a bit troubling because it leads to greater control of the system by the developer at the expense of the owner of the device. It's been said that the best tools are those that lend themselves to uses not anticipated by the creator. Reducing or eliminating the ability of the owner to use a device in ways that are unanticipated ultimately reduces its potential power and usefulness. Perhaps that's what is wanted to prevent an owner from using the device in ways that are inconvenient or contrary to an established business model."

johanneswilm writes "While writing my Ph.D in anthropology I found out it's almost impossible to get non-geeks to help me with editing my thesis because it was written in Latex. Lyx is almost there, but as it's not web based, it's difficult to use for online collaboration. Writelatex.com is online, but typing LaTeX code is a no-go for non-geeks. Google Docs is web based and near-WYSIWYG, but lacks support for professional print formats such as Latex. The Ph.D took longer than expected, so before finishing me and three others were able to code an entirely new editor: Fidus Writer: web based, open source (AGPL), almost-WYSIWYG and with tools for academics such as citation management and formula support and output formats PDF, Epub, Latex, HTML."

rysiek writes "When a politician starts talking about defending the innocence of children, there's bound to be a great policy initiative ahead. That's how British PM David Cameron introduced the British porn block. That's also how the Polish Minister of Justice started his remarks yesterday morning on how good an idea it is and that it should be introduced in Poland. This started the shortest Internet censorship debate ever, as in the evening of the same day the Polish Prime Minister and the Minister of Administration and Digitization denounced any such ideas: 'We shall not block access to legal content regardless of whether or not it appeases us aesthetically or ethically.' There had been several full-blown Internet censorship debates in Poland during the last four years. Apparently the arguments against it were not lost on at least some of Polish politicians."

At a press conference dubbed "Breakfast With Sundar," Google announced two new pieces of hardware and a minor revision to Android. Complete stories and commentary are still coming in, but in the mean time you can skim a liveblog or two First is the new Nexus 7. The hardware is slightly improved (full HD screen, better graphics, etc.). The specs managed to "leak" hours before the event through Best Buy opening preordering too early. On the software side, they've announced a minor revision to Android, 4.3. It features improved Bluetooth support (including Bluetooth 4.0), OpenGL ES 3.0, enhanced internationalization, enhanced DRM, and multi-user support. The multi-user support looks most exciting: now you can share a tablet with more than one person. One of the features Google focused on was restricted profiles: a device owner can create accounts that e.g. cannot make in-app purchases (Junior won't rack up a $3000 bill again). Bad news: Google is implementing stricter DRM for books and video, locking down the entire video stack. The consolation prize is that Netflix will work on more devices and at 1080p. Also demoed were a new version of Chrome that brings the tablet experience closer to the desktop, improved hangouts, and improved maps. Google also appears to be making a push into gaming, emphasizing tablet-only games that integrate into Google+. In addition to gaming, they have secured deals with five major textbook publishers to sell students presumably DRMed electronic textbooks that can be purchased or rented, enhanced with better search and highlighting (because PDF readers don't support those features already). As usual lately, all of the really nice additions to Android are proprietary and tied to Google services, further eroding the open nature of Android. Finally, they announced a tiny $35 dongle named Chromecast that appears to be the successor of the Nexus Q. Running Chrome OS, it connects to any HDMI port, finds your Wi-Fi network, and Just Works (tm) for online video. The online and mobile Youtube and Netflix interfaces will allow you to hit a single button and forward the video to your television as well. Google Music streaming to the television is also supported. The Chromecast looks like a handy little device, hopefully it is turns out it can be reflashed. Of course, when using your browser as a remote, all of the commands go through The Cloud. An SDK and more details on the software side of things are slated for release later today, although conspiciously absent on their supported platforms list is GNU/Linux, listing only Chrome OS and Android. Update: 07/24 18:01 GMT by U L : The Chromecast SDK is out, but with an awfully restrictive license that requires written permission from Google to distribute any cast enabled applications, which appears to make it completely incompatible with Free/Open Source software.

An anonymous reader writes "How can we ensure, together, that this will not be the last GUADEC? Last year, during GUADEC, there was that running joke amongst some participants that this was the last GUADEC. It was, of course, a joke. Everybody was expecting to see each other in Brno, in 2013. One year later, most of those who were joking are not coming to GUADEC. For them, the joke became a reality. People are increasingly leaving the desktop computer to use phones, tablets and services in the cloud. The switch is deeper and quicker than anything we imagined. Projects are also leaving GTK+ for QT. Unity abandoned GTK+, Linus Torvald's Subsurface is switching from GTK+ to Qt. If you spot a GNOME desktop in a conference, chances are that you are dealing with a Red Hat employee. That's it. According to Google Trends, interest in GNOME and GTK+ is soon to be extinct."

mikejuk writes "Google Research recently released details of a Machine Vision technique which might bring high power visual recognition to simple desktops and even mobile computers. It claims to be able to recognize 100,000 different types of object within a photo in a few minutes — and there isn't a deep neural network mentioned. It is another example of the direct 'engineering' approach to implementing AI catching up with the biologically inspired techniques. This particular advance is based on converting the usual mask-based filters to a simpler ordinal computation and using hashing to avoid having to do the computation most of the time. The result of the change to the basic algorithm is a speed-up of around 20,000 times, which is astounding. The method was tested on 100,000 object detectors using over a million filters on multiple resolution scalings of the target image, which were all computed in less than 20 seconds using nothing but a single, multi-core machine with 20GB of RAM."

An anonymous reader writes "Google today announced it is bringing its Cloud Print project to Windows. The company has launched both a driver and a service, both of which are available for download now from Google Tools. For those who don't know, Google Cloud Print connects Cloud Print-aware applications (across the Web, desktop, and mobile) to any printer. It integrates with the mobile versions of Gmail and Google Docs, and is also listed as a printer option in the Print Preview page of Chrome." One of the things that annoys me about Android: having to print through the Cloud (tm) when I have an Internet Printing Protocol CUPS server on the same network as my phone connected to a printer ten feet from me. It wouldn't be so bad if the Google Cloud Print libraries weren't proprietary and did something like IPP proxying instead of using a similarly proprietary API.

An anonymous reader writes "Google today announced it is bringing its Cloud Print project to Windows. The company has launched both a driver and a service, both of which are available for download now from Google Tools. For those who don't know, Google Cloud Print connects Cloud Print-aware applications (across the Web, desktop, and mobile) to any printer. It integrates with the mobile versions of Gmail and Google Docs, and is also listed as a printer option in the Print Preview page of Chrome." One of the things that annoys me about Android: having to print through the Cloud (tm) when I have an Internet Printing Protocol CUPS server on the same network as my phone connected to a printer ten feet from me. It wouldn't be so bad if the Google Cloud Print libraries weren't proprietary and did something like IPP proxying instead of using a similarly proprietary API.

sfcrazy writes "Aaron Seigo, a lead KDE developer, says that the ambitious KDE tablet Vivaldi is shipping to the team for quality testing. Seigo writes on his Google+ page, 'A great start to the week with a warm, sunny, quiet Monday. Well, almost quiet. The first Vivaldi tablets, new dual-core engineering boards and the custom EOMA68 developer workbenches we commissioned have all been shipped out. Don't get too excited: the tablets are pre-certification (EC/FCC) and are on their way to us so we can verify the Q/A targets we set out. Still ...'" It looks like long-time reader lkcl's EOMA-68 initiative is working out; in related news the first batch of Allwinner A10 EOMA-68 cards is shipping to the "...20 Free Software developers brave enough to take one of these at this very early phase." Update: 07/23 17:16 GMT by U L : Correction from lkcl: the first batch of EOMA-68 cards are actually using the Allwinner A20, a bit of an upgrade from the original design.

Nerval's Lobster writes "In June, Steven Spielberg predicted that Hollywood was on the verge of an 'implosion' in which 'three or four or maybe even a half-dozen megabudget movies are going to go crashing to the ground.' The resulting destruction, he added, could change the film industry in radical and possibly unwelcome ways. And sooner than he may have thought, the implosion has arrived: in the past couple weeks, six wannabe blockbusters have cratered at the North American box office: 'R.I.P.D.,' 'After Earth,' 'White House Down,' 'Pacific Rim,' and 'The Lone Ranger.' These films featured big stars, bigger explosions, and top-notch special effects—exactly the sort of summer spectacle that ordinarily assures a solid run at the box office. Yet all of them failed to draw in the massive audiences needed to earn back their gargantuan budgets. Hollywood's more reliant than ever on analytics to predict how movies will do, and even Google has taken some baby-steps into that arena with a white paper describing how search-query patterns and paid clicks can estimate how well a movie will do on its opening weekend, but none of that data seems to be helping Hollywood avoid shooting itself in the foot with a 'Pacific Rim'-sized plasma cannon. In other words, analytics can help studios refine their rollout strategy for new films—but the bulk of box-office success ultimately comes down to the most elusive and unquantifiable of things: knowing what the audience wants before it does, and a whole lot of luck."

An anonymous reader writes "Google is building a Chrome remote desktop app, which lets you access other computers or another user access your computer over the Internet, for Android. The new addition, called Chromoting, will likely be pushed as a mobile version of the existing Chrome Remote Desktop offering. For those who don't know, the original Chrome Remote Desktop is an extension for Google's browser. It was first released as a beta in October 2011 and could be used to control another one of your own computers as well as a friend's or family member's (usually to help with IT issues)."

First time accepted submitter husemann writes "Micah Lee from the EFF filed a bug report about Google storing all your WLAN passwords on their application settings backup service without allowing you to encrypt them. So far it's not known whether the passwords are stored encrypted at rest, but just the fact that Google can read them (and disclose them if forced by 'law') is a bit surprising, too put it nicely. Already one German university is concerned enough about this 'feature' that they issued a warning to their users."

jones_supa writes "Entertainment industry groups in Norway have spent years lobbying for tougher anti-piracy laws, finally getting their way earlier this month. But with fines and site-blocking now on the agenda, an interesting trend has been developing. According to a new report published by Ipsos, between 2008 and 2012 piracy of movies and TV shows collapsed in Norway, along with music seeing a massive drop to less than one fifth of the original level. Olav Torvund, former law professor at the University of Oslo, attributes this to good legal alternatives which are available today (Google translation of Norwegian original). Of those questioned for the survey, 47% (representing around 1.7 million people) said they use a streaming music service such as Spotify. And of those, just over half said that they pay for the premium option."

darthcamaro writes "Last week, Rain Forrest Puppy (aka Jeff Forristal) first disclosed the initial public report about an Android Master Key flaw. Code was released earlier this week for attackers to exploit the flaw — but what about users? Google has claimed that it has patched the issue but how do you know if your phone/carrier is safe? Forristal's company now has an app for that. But even if your phone is not patched, don't be too worried that risks are limited if you still to a 'safe' app store like Google Play. 'The only way an Android user can be attacked via this master key flaw is if they download a vulnerable application. "It all comes down to where you get your applications from," Forristal said.'"

Two bits of Google news from today/yesterday. This morning, Google started rolling out a major update to mobile Maps. They've created a new tablet interface, improved integration with local places, integrated the Zagat guide, and enhanced navigation to automatically route you around traffic incidents. As usual lately, Google also removed a few features: Latitude and Check-ins. If you used those you'll have to use the Google+ application now. They also made a strange change to offline maps: instead of a menu option, you now access the area you want to make available offline and search for "OK Maps." On the Chrome front, Google released Chrome 28 yesterday, the first release featuring the WebKit fork Blink. The under-the-hood changes look promising, quoting the H: "The developers say that the increased speed is also thanks to the new threaded HTML parser, which frees up the JavaScript thread, allowing DOM content to be displayed faster. The HTML parser also takes fewer breaks, which is said to result in time savings of up to 40 per cent."

New submitter Nicolas Jondet writes "French courts will not be able to disconnect convicted file-sharers from the Internet anymore. On Tuesday, the French Culture minister issued a decree modifying the graduated response scheme and removing the disconnection penalty. 'The report says that instead of simply disconnecting users, those suspected of copyright could be fined if they did not reply to warnings, with a relatively low fine (€60) to begin, and the size of the fine would increase depending on the number of infractions. French anti-piracy will now their focus – instead of handing heavy punishments to individual users, the government is looking towards penalizing "commercial piracy" and "sites that profit from pirated material," according to an official spokesperson.'"

An anonymous reader writes "Google today released Chrome version 28 for Windows and Mac. The new version features a notification center, although it's only available on Windows (in addition to Chrome OS of course). You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome. This is also the first release of Chrome that ships with Blink instead of WebKit. You can check the Blink ID yourself tag by navigating to chrome://version/."

NF6X writes "UCSD Lecturer Brett Stallbaum has released an Android app called Gun Geo Marker to allow people to 'Geolocate Dangerous Guns and Owners.' The app description states: 'The Gun Geo Marker operates very simply, letting parents and community members mark, or geolocate, sites associated with potentially unsafe guns and gun owners. These locations are typically the homes or businesses of suspected unsafe gun owners, but might also be public lands or other locations where guns are not handled safely, or situations where proper rights to own or use any particular type of firearm may not exist.' I question how the motivation behind developing this app differs from, say, developing an app to allow others to publicly geotag homes of people believed to belong to a particular religion or political party."

chicksdaddy writes with news of a Proof-of-Concept exploit for the recent Android APK signature vulnerability. From the article: "Pau Oliva Fora, a security researcher for the firm Via Forensics, published a small, proof of concept module on GitHub that exploits the flaw in the way Android verifies the authenticity of signed mobile applications. The flaw was first disclosed last week by Jeff Forristal, the Chief Technology Officer at Bluebox Security, ahead of a presentation at the Black Hat Briefings in August. ... The simple program leverages APKTool, an open source tool for reverse engineering Android applications — decompiling and then recompiling their contents. His script allows a user to select and then decompile a legitimate Android application and then recompile it, creating an altered, 'malicious' APK that will have the same, cryptographic signature as the original file. In an e-mail statement, Google said that a patch for Forristal's vulnerability was provided to Google's OEM and carrier partners in March, and that some (Samsung) have already shipping a patched version of Android to customers. However, that response hasn't been universal — a reflection of Android's fragmented install base."

Asiana Flight 214 from Seoul crashed while landing at San Francisco Airport today. Early reports suggest the plane was unstable as it touched down, which led to the tail of the plane breaking off. There are no official casualty reports yet, but passengers were seen walking off the plane. Preliminary estimates say one or two dead and 75 being transported to area hospitals. (Others are reporting two dead and several dozen injured.) Eyewitness report: "You heard a pop and you immediately saw a large, brief fireball that came out from underneath the aircraft," Anthony Castorani said on CNN. "At that moment, you could see that that aircraft was again starting to lift and it began to cartwheel [Ed: he likely means spinning horizontally, like a top]. The wing broke off on the left hand side. You could see the tail immediately fly off of the aircraft. As the aircraft cartwheeled, it then landed down and the other wing had broken." The media has estimated about 290 people were on board the plane. The top of the cabin was aflame at one point, but it's not known yet whether that affected the passengers. "Federal sources told NBC News that there was no indication of terrorism." Some images from the news make it look like the plane may have tried to touch down too early, hitting the seawall just before the runway.

First time accepted submitter aBaldrich writes "Edward Snowden was offered 'humanitarian asylum' by Nicolás Maduro, the president of Venezuela. The country's official news agency reports (original Spanish, Google translation) that the decision was taken after a meeting of the presidents of Argentina, Bolivia, Ecuador, Suriname, Uruguay and Venezuela. Maduro denounced an attempt to 'colonize' several European countries, and that he is acting 'on behalf of the dignity of the Americas.'" The Guardian confirms.

Freshly Exhumed writes with this news (quoting The Guardian): "France runs a vast electronic surveillance operation, intercepting and stocking data from citizens' phone and internet activity, using similar methods to the U.S. National Security Agency's Prism programme exposed by Edward Snowden, Le Monde has reported. An investigation by the French daily [en français; Google translation] found that the DGSE, France's external intelligence agency, had spied on the French public's phone calls, emails and internet activity. The agency intercepted signals from computers and phones in France as well as between France and other countries, looking not so much at content but to create a map of 'who is talking to whom,' the paper said."

GenieGenieGenie writes "After all the talk of printed guns and the problems they pose to traditional methods of perimeter security, we get a live demo courtesy of some rather brave journalists from Israel's Channel 10, who took the plastic weapon known as the Liberator past security into the Israeli parliament, and held it within meters of the Israeli prime minister Benjamin Netanyahu. I say brave because had they been caught pulling this stunt, which involved taking their toy out of the bag while sitting in the audience of a speech by the prime minister, they would have faced some real steel. Haaretz has the video (sorry, Hebrew only at the moment) [Google-translated version of the article -- Ed.] where you can follow the breach (from ~6:30) and see them pass the metal detector and the moment when the gun comes out. The movie also shows some testing of the gun in a police-supervised weapons range. Parliament security officials said that 'this is a new phenomenon and they are checking the subject to give it a professional solution as quickly as possible.' I hope this doesn't mean we will now officially face an era of ever more intruding security checks at entrances to events like this." Would-be Liberator printers, take note: the testing shows the barrel violently separating from the rest of the gun.

Sarah's CyberCraft "about" page says, "Here at CyberCraft Robots, our Orbiting Laboratory allows us to search local star systems for Artifacts from the Future." CyberCraft's Earthside component is in St. Petersburg, Florida, where Sarah assembles robots from found parts that others might think are just ordinary industrial detritus, but that she has learned to recognize as parts from disassembled or abandoned robots. She has an alternate version of CyberCraft's history for people "with less imagination," about how she jumped from being a math whiz to studying for an EE to working as a programmer to art... and into making art robots. Or robot art, depending on how you look at it. The robots, ray guns, and spaceships Sarah makes will not fight battles or clean your house. They just sit there and look good. And they get shown in fine art galleries, so we know they're art, not just ordinary robots. This isn't to say Sarah is the only human making robot sculptures. A Google search for "robot sculpture" turns up plenty of others. We met Sarah purely by chance. We easily could have met one of the many other robot sculptors instead, but she's the one we happened to come across first. Perhaps the Quantum Computer that runs the Orbiting Robot Laboratory directed us to her. That's as good an explanation as any, isn't it?

vikingpower writes "The official Russian Press agency Interfax has the scoop: Edward Snowden asks for political asylum in Russia (Google Translate). Russia Today, however, denies the news. Is this part of a clever disinformation move by Snowden, who reportedly is still in the Moscow airport Sheremetyevo 2?" The Washington Post is also reporting Snowden did apply for asylum in Russia. Snowden released a statement last night through Wikileaks, quoting: "For decades the United States of America has been one of the strongest defenders of the human right to seek asylum. Sadly, this right, laid out and voted for by the U.S. in Article 14 of the Universal Declaration of Human Rights, is now being rejected by the current government of my country. The Obama administration has now adopted the strategy of using citizenship as a weapon. Although I am convicted of nothing, it has unilaterally revoked my passport, leaving me a stateless person. Without any judicial order, the administration now seeks to stop me exercising a basic right. A right that belongs to everybody. The right to seek asylum."

It's not just for obscure Japanese islands anymore: reader NobleSavage writes with news that "If you're a tourism board, non-profit, university, research organization or other third party who can gain access and help collect imagery of hard to reach places, you can apply to borrow the Trekker and help map the world." You can also help map the world (albeit without the very neat Trekker backpack cam) without an application process via OpenStreetMap. But if you had access to a panoramic camera like this, what places or spaces would you want to capture? I hope there will be street view imagery of Petra, but I don't see any yet.

New submitter jshurst1 writes "Google has announced QUIC, a stream multiplexing protocol running over a new variation of TLS, as well as UDP. The new protocol offers connectivity with a reduced number of round trips, strong security, and pluggable congestion control. QUIC is in experiment now for Chrome dev and canary users connecting to Google websites."

New submitter jshurst1 writes "Google has announced QUIC, a stream multiplexing protocol running over a new variation of TLS, as well as UDP. The new protocol offers connectivity with a reduced number of round trips, strong security, and pluggable congestion control. QUIC is in experiment now for Chrome dev and canary users connecting to Google websites."

Nerval's Lobster writes "Google is adding data about malware to its Transparency Report. For the past seven years, the search-engine giant has offered a Safe Browsing program that warns Web-surfers about unsafe Websites (i.e., those loaded with malware or phishing scams). The new section of the Transparency Report will show how many people see those Safe Browsing warnings on a weekly basis, along with other malware-related tidbits, including Webmaster response times to threats and Website reinfection rates. The data includes malware distribution by autonomous systems, which are one (or more) networks controlled by a single entity such as a university or ISP. 'This data is part of our effort to support a safer and more secure web,' read Google's explanatory note in the Report. 'By sharing information from our scans, we hope to encourage cooperation among those who battle malware.' Google takes all that autonomous system data and breaks it down by country. For example, of the 31 million Websites in the United States scanned by Google, roughly 2 percent host malware. In other words, this data just reinforces what pretty much everybody knows: it's not a safe Internet out there."

Nerval's Lobster writes "Google is adding data about malware to its Transparency Report. For the past seven years, the search-engine giant has offered a Safe Browsing program that warns Web-surfers about unsafe Websites (i.e., those loaded with malware or phishing scams). The new section of the Transparency Report will show how many people see those Safe Browsing warnings on a weekly basis, along with other malware-related tidbits, including Webmaster response times to threats and Website reinfection rates. The data includes malware distribution by autonomous systems, which are one (or more) networks controlled by a single entity such as a university or ISP. 'This data is part of our effort to support a safer and more secure web,' read Google's explanatory note in the Report. 'By sharing information from our scans, we hope to encourage cooperation among those who battle malware.' Google takes all that autonomous system data and breaks it down by country. For example, of the 31 million Websites in the United States scanned by Google, roughly 2 percent host malware. In other words, this data just reinforces what pretty much everybody knows: it's not a safe Internet out there."

itwbennett writes "There's a lot to like about Google Voice, including 'voicemail transcriptions, the ability to send and receive unlimited text messages by phone or website, and recording incoming calls,' says Voice convert Kevin Purdy. But when it comes to app integration, Voice is falling short — even on Android phones: 'Most apps that do neat things with incoming texts, like read them out loud when you're driving, can't work with Voice. Tasker, a crazy, nerdy automation tool that can do things like turn your volume up when you get a text from your wife, can't work with Voice.... Online services that text you to verify or remind you are about 50/50.' Google employee Nikhyl Singhal wrote in a Google+ post that 'Hangouts is designed to be the future of Google Voice.' But what Voice users like Purdy are looking for is some sort of 'assurance that Google Voice can work just like any other text messaging system.'"

symbolset writes "On Thursday night the Lee's Summit city council passed three resolutions to welcome Google Fiber to their community. This is the 12th community in the Kansas City Metro Area to welcome Google Fiber and the 14th city overall. The KC map now covers almost all of the KC metro area with parts in both Kansas and Missouri. 8 months into the rollout two fiberhoods have been completed, 30 more are underway and 50 more are to start by the end of summer. This covers most of the territory of both Kansas Citys ahead of schedule and completes before the end of winter so the timeline has been accelerated. As Google runs their fiber across town it appears they're putting backbones down the major thoroughfares to be trunks out to the wider communities. With Provo wired with fiber already, Austin to start next, it looks like Google Fiber's ambitions are not to deliver their symmetric gigabit uncapped, unfiltered, inexpensive fiber Internet to just a few privileged enclaves. They still have over 1,000 cities left to go who have already petitioned to be Google Fiber cities, so it's not like they're going to run out of work."

An anonymous reader points out a report at Groklaw about another new lawsuit from patent firm Intellectual Ventures against Motorola Mobility (they have an earlier patent suit against Motorola underway already). The suit seeks damages from alleged infringement of seven patents, most of which involve wireless communications and Motorola's use of Android. One of the patents, US5790793, is "A method and system for sending and receiving Uniform Resource Locators (URLs) in electronic mail over the Internet." Intellectual Ventures' complaint (PDF) says Motorola product that implement MMS violate this patent. PJ at Groklaw thinks this is another patent attack on Android: "And guess where IV got these patents? Not directly from the USPTO. I'll give you a big hint. Some of them, from what I'm seeing, are from working companies. Don't they call that privateering, when active companies outsource their patents to trolls to do their dirty work? Why yes. Yes, they do. Can you guess one company in this picture? Someone helping Microsoft in its anti-competitive attack on Android and Linux, you say? Yes, one of the companies that seems to have transferred two patents to IV for its holy quest is Nokia, Microsoft's 'partner in crime', as I like to think of them. I know. You are shocked, shocked to know that patents are being used anti-competitively in a court of law."

New submitter irventu writes "The long-awaited PHP 5.5.0 has finally been released, bringing many new features and integrating Zend's recently open-sourced OPcache. With the new Laravel PHP framework winning RoRs and CodeIgnitor converts by the thousands, Google recently announcing support for PHP in its App Engine and the current PHP renaissance is well underway. This is great news for the web's most popular scripting language." The full list of new features is available at the Change Log, and the source code is at the download page.

Contributor Tom Geller writes: "I recently wrote an article about Bitcoin and the law for Communications of the Association for Computing Machinery. In researching it I ran into plenty of wishful thinkers, ridiculous greedheads, and out-and-out nutbags promising a rosy future. I also found the expected blowback from vehement naysayers who think the best way to combat crazy is with more crazy. But despite that, I walked away believing that Bitcoin — or a decentralized cryptocurrency like it (let's call it "Coin") — is here to stay. As an interested outsider to the Coin economy, and a long-time technology commentator, here's what I think its future holds." Read on for Tom's predictions. Coin's primary use will continue to be in international transactions.

While people wonder "When will I be able to pay for groceries and utilities with Bitcoin?", that use might never come. But Coin already shines in international transactions, where it provides a clear advantage over current systems, which are expensive and complicated hassles. That's why PayPal has become the go-to solution: it just works, albeit with typical fees around 3-5%.

Coin reduces that fee to a small fraction of 1% (when sent directly), and is available in places where PayPal fears to tread (Zimbabwe, Pakistan, etc.). Coin transactions occur instantly, with no intermediary, and — for better or worse — without recourse.

That leads to Coin's second primary use: to store liquid value in places where other stores (such as national currency) are unreliable. For all the cries that Bitcoin is "unstable", it seems to have settled quite nicely after its April spike. Certainly it looks appealing to anyone in an unstable country, and it's even tempting for those in places where the currency's been on a long, slow slide, like Argentina.

Coin's big vulnerability is its interface with national currencies ("real money").

None of this matters if you can't get your money out again. And that's where governments are taking a close look at Coin — with good reason. First, Coin exchanges have a terrible track record; second, such points of exchange are bottlenecks through which financial crimes often flow.

In the U.S., the government's Financial Crimes Enforcement Network (FinCEN) issued guidance asserting its right to regulate "Money Services Businesses", and defining exchanges dealing in virtual currencies (including Bitcoin) as such. That's a problem for many existing Coin exchanges, as the costs for complying with regulations are high. But if there's not a stable and reliable way to get national currency in and out of Coin, its value will plummet.

Conversely, Coin's value is likely to shoot up if this interface gets easier. Right now, it's surprisingly hard to buy Bitcoin (et al.) directly with U.S. dollars. Most methods require bank wires, tricky multi-step workarounds, and high fees. (I found Coinbase to be the most accessible, albeit with long delays and a bank verification procedure similar to PayPal's.) If Coin becomes as easy to buy as a gift card and redeemable at every bank, its practical utility will soar for everyday people.

No government will make Coin illegal.

Despite bloviation by a few politicians and baseless statements in the press, Coin is not per se illegal, and there have been no serious attempts to make it so. The FinCEN guidance mentioned earlier explicitly says that ordinary users — those who buy and sell using Coin — are "not subject to FinCEN's... regulations for MSBs". It's possible that other government agencies will continue to claim authority, but there doesn't seem to be much support for it.

A lot of noise has been made about Coin's use in illegal business, for example on Silk Road (where it's the only currency). But law enforcement is realizing that the currency isn't to blame, much as they've started to say that Craigslist isn't responsible for crimes organized through its ads. I predict that that distraction will continue to surface from time to time, but will essentially die soon.

Even if governments attempt to illegalize Coin, there's only so much they could do to criminalize ordinary users. Again, Coin's real vulnerabilities are higher up the chain. However....

If Coin succeeds, governments will get involved — for the better.

"Noooo!!!" scream the cryptoanarchists who are Coin's pioneers. "Keep the government out of this! Coin can't be controlled! Nobody can take away our freedoms!" What they don't realize is that this attitude doesn't reflect the values of Coin's future users. The benefits of "freedom" matter to the innovators; convenience and safety matter to those who follow.

"Government" in this case could also be a government-size corporation, syndicate, or other entity. The important thing is that it's big enough to administer, back, and enforce initiatives to protect the Coin economy. Whatever that "bully entity" is, Coin adopters will welcome it because of two major flaws currently in (Bit)Coin's design.

First, Coin is ridiculously easy to destroy by accident. If you lose the private cryptographic key that identifies your coin, it's gone. Not just stolen, but removed entirely from the economy, so nobody will ever own it again. Consider these stories on Bitcointalk.org, where within a few messages the cumulative total tops 10,000 BTC — currently valued around a million dollars. A central authority could address this in several ways such as tracking, restitution, etc.. People don't care that their cash is anonymous when the rent money disappears.

Second, the entire system is vulnerable to a brute-force attack. Without getting into the specifics, Coin (well, Bitcoin) works because it assumes that at least 50% of the computer power on the network is held by honest players. But a recent 51% attack on Feathercoin (a Coin with much lower capitalization) showed that it's possible for a single party (or syndicate) to trump that.

Let's do the math for Bitcoin, the Coin with by far the highest capitalization, at just north of USD$1 billion (1 x 10^9). To reliably overwhelm the network, you'd need computing power delivering about 100,000 gigahashes per second. Computers optimized for Bitcoin processing are currently available for about $1,000/gigahash, so sufficient computing power can be bought for $100 million. Electricity cost for the deed would be about $200,000/day.

O.K., it's not something a basement hacker could whip up. But there are over 400 people, and thousands of syndicates with a billion dollars in the U.S. alone. Perhaps at least one of them is crazy enough to drop 1% of the wealth to partially control (or completely destroy) a billion-dollar system. (Hell, one of them recently spent 1/10th of that price tag on his wedding.)

Those are only the two biggest technical concerns. Then there's the galaxy of financial services (such as insurance) that's available for fiat money, but which would be hard or impossible to provision for Coin without a central authority. Time could overcome these barriers; a bully entity would overcome them faster, and with greater public buy-in.

Bitcoin is not the end game.

Along those lines, I don't believe that Bitcoin will be the ultimate winner in this game. It's the 1.0, and a brilliant first effort at that. But it's not perfect, and several pretenders to the throne already claim to fix some of its bugs. In fact, shifting conditions may require periodic issuance of new Coin as a matter of course. (As I said before, I believe such issuances will involve a central authority.)

These predictions all assume that Coin will grow, and there are many reasons it might not. However, I'm bullish on it for the long-term. It's already proven its value in use; the public is used to handling Coin-like money (viz. Square Wallet); and its first major hurdles are in the past. Now it's ready to enter a fascinating future.



- - - - -
Tom Geller (tomgeller.com) writes about technology and business. He's best known for Drupal-related work that includes eight video courses for lynda.com, a book for Peachpit Press, and corporate work for Acquia, Commerce Guys, and others. He first became involved in computers as a grade-school student in 1976, playing "Hunt the Wumpus" on a 100-pound monster that spewed tractor-feed paper onto the floor. He lives in Oberlin, Ohio.

First time accepted submitter ramorim writes "In honor of the Chemist Day, celebrated in Brazil on this day June 18, 2013, I publish a proposal for a new Periodic Table of Elements (Original, in Portugese) in a modular spiral-hexagonal model, with continuity and connectivity for all constituent units of the matter. This proposal indeed permits to extrapolate the hypothetical elements of the G-block and H-block in the same model."

New submitter BrokenHalo writes "Google has revealed that it has 30 balloons floating over New Zealand in a project to bring free Wi-Fi to earthquake-stricken, rural or poor areas. They're calling it Project Loon. '[W]e’ve built a system that uses balloons, carried by the wind at altitudes twice as high as commercial planes, to beam Internet access to the ground at speeds similar to today’s 3G networks or faster. As a result, we hope balloons could become an option for connecting rural, remote, and underserved areas, and for helping with communications after natural disasters.' Eventually, as the balloons move across the stratosphere, consumers in participating countries along the 40th parallel in the Southern Hemisphere could tap into the service. The technology will be trialled in Australia next year, possibly in Tasmania. If the latter happens to be true, then you'll probably hear the telcos' screams in New York."

larry bagina writes "You can't make this stuff up — 'Cameras, recording devices, and other electronic devices, such as smart phones, will not be permitted at the [2013 annual shareholder] meeting.' Maybe it runs afoul of their rules on sexually explicit material?"

New submitter einar2 writes "German hoster Hetzner informed customers that login data for their admin surface might have been compromised (Google translation of German original). At the end of last week, a backdoor in a monitoring server was found. Closer examination led to the discovery of a rootkit residing in memory. The rootkit does not touch files on storage but patches running processes in memory. Malicious code is directly injected into running processes. According to Hetzner the attack is surprisingly sophisticated."

theodp writes "It was the best of movies; it was the worst of movies. GeekWire reports that The Internship — the new comedy starring Vince Vaughn and Owen Wilson as two 40-something guys who get internships at Google — is getting high praise from Googlers but low marks from movie critics. Google CEO Larry Page called the movie 'a lot of fun' in his Google+ post, while fellow Google exec Vic Gundotra gushed, 'I laughed a lot while watching this movie!' After screening a sneak preview with Google companions, Wired's Steven Levy wrote, 'From Google's point of view, the movie could not possibly be better.' USA Today's take, on the other hand, is that 'Google has never looked lamer thanks to The Internship.' And the NY Daily News calls the movie 'an unfunny valentine to Google.' But perhaps the unkindest cut of all comes from the NY Post, who suggests that 'maybe The Internship was secretly funded by Bing.' Ouch." Update: 06/07 20:02 GMT by T : Peter Wayner saw the movie (a "harmless bit of summer fluff"), and his full-length take below takes on some of the tech-company misconceptions that the film-makers gleefully adopted as script material. While there have been a handful of movies about hacking (“War Games”, “Hackers”) and every heist movie seems to stick at least one programmer on the team, there are few films devoted to craft of building software. Who would want to spend two hours staring at beautiful actors stuck in cubicles staring at lines of code? “The Internship”, thankfully, isn’t that movie, although it is set at Google’s mothership where the average day is filled with days staring at lines of code. It’s a harmless bit of summer fluff that sails blithely along in its own carefully edited version of reality pretending that building software is anything but staring at screens. It’s a nice journey to a happy ending with only a few veiled hints of darker trends and deeper issues buried underneath the fun.

The movie is a buddy comedy pairing Owen Wilson and Vince Vaughn, the dynamic duo who were last seen together in “The Wedding Crashers” as fast-talking scammers sneaking into receptions. This time, they’re washed up watch salesmen fast-talking their way into a job at Google. Someone finally noticed that mobile phones took over the job of telling time. The Hollywood executives who develop movies with lambda expressions probably called it “The Google Crashers.”

The two actors are likeable rogues that are playing the same game. They may be older but they understand people, unlike the nerds at the Googleplex. They’ve got an answer for everything and that answer is usually something that will keep them afloat in the rapidly changing economy. It’s sort of “Glengarry Glen Ross” or “Death of a Salesman” without the adultery or the kind of lefty talk that attracts the attention of the House Un-American Activities Committee.

For them, Google is the promised land, the Emerald City, the Big Rock Candy Mountain, a role that the company plays happily, almost too happily. The company reportedly traded access to the Googleplex for some control of the script and they reportedly wielded this knife to slice away a scene showing a crash of their now famous self-driving cars. Claire Cain Miller at the NY Times reported that the company even created the credits and packed them full of ads for Google’s famous and not-so-famous products. There’s only a bit of irony in the way that the company that once made its name by creating tasteful, small and very focused ads could put its name on such an endless, loud and extravagant act of branding.

Naturally, the list of which Google features makes the closing credits is highly selective. There’s no mention of the direct link that the US Government claims to have to Google’s huge files on all of us or any discussion of the ongoing morass of the lawsuit from the book authors. There is also no questioning of Google’s vision of the social compact where you and I do the work of creating the content and they enjoy the fruits of the advertising that pays for most of the luxuries seen in the movie. It’s not “Enemy of the State” and certainly not “Office Space.” The pro-business crowd that is always asking Hollywood for some good corporate characters has finally gotten its wish.

But Slashdot readers will be a bit disappointed because the Google shown in the movie is just another company from central casting. There are occasional references to HTML5, CSS3 and “building an app” but most of the audience will walk away thinking that answer to creating software is eating pizza, going to a strip club, or drinking alcohol. Just as Hollywood injected scenes of drunken programming into “The Social Network”, Hollywood can’t seem to believe that software is made with logic, precision and concentration. The secret of success, at least according to the movie, is the same as the secret to diabetes: plenty of carbs and plenty of alcohol.

It may be too much to expect Hollywood to confront some of the deeper issues about Google’s work place because the movie is a comedy, not a remake of “Norma Rae”. The characters make a brief reference the downside and the brutal, winner-take-all game that they’re playing. 95% of the interns won’t get a paying job and most people who get paying jobs won’t get stock options worth very much. It’s like “The Hunger Games” but played for laughs.

Sitting around moaning about the way that Google (and the Internet) is destroying so many jobs wouldn’t make for a fun movie. Instead the characters revel in the free food and the non-stop buffet without recognizing that the benefits are a bit of a clever trap. Feeding someone $20 in food is a good deal if it keeps them working for three to six more hours.

The script writers apparently didn’t get the memo that the company has slowly been cutting back on the fancy extras. In 2008, the IPO millionaires boosted the cost of day care so high that there was open sobbing from the post-IPO engineers who couldn’t afford it. While many outsiders think movies like this are accurate, insiders complain that they can’t afford the day care which costs thousands of dollars per kid per month. It’s a not-so-subtle message that kids are a high cost that get in the way of software development.

And then in 2009 Google started clamping down on the free food, especially the clever employees who would take home big containers of food on Friday to make it through the weekend without a trip to the office. Larry Page told reporters at a news conference then, “I think it’s important to reset the culture from time to time. we decided to, for example, we significantly cut down all the snacks that had been available.” This new version made the film because Vaughn learns, to his chagrin, that he can’t take home the seven bagels he got for free. Once again, the food is just a carrot to keep people in front of the screens.

The movie certainly suggests that Google, like “Logan’s Run”, is filled with 20-somethings on an extended summer camp sleepover with fat salaries to make it even more fun. One of the managers is said to be 23 and already seasoned because he’s spent 4 years with the company.

Is this really accurate or just another bit of Hollywood frosting on the free cookie? Alas, Google has endured at least one high-profile age discrimination lawsuit from a manager who lost millions in stock options after being fired. The ex-employee’s lawyers dug up incriminating emails saying, among other things, that the guy was an “old man”, an “old guy” and an “old fuddy-duddy”. That attitude is heard again and again here although with less precision.

When I’ve spoken with people who’ve worked there, they have cautiously suggested that age discrimination is a real issue, especially to anyone who grows up, has kids, and starts working shorter hours. Somehow, the older folks seem to get replaced by someone who is young. Then, when their contract ends, they’re given a “severance deal” that effectively buys their silence. They’ll only mention the issue of age discrimination in bars far away from any Glassholes wearing Google Glass recording everything.

Still, this view doesn’t jibe with my experiences. Many of the people I’ve met at Google are older and some even sport grey beards. The engineering teams and some of the development teams are run by seasoned veterans with years of experience in the valley. For every 22 year old twerp in the movie, I’ve met some 40-somethings who know a thing or two and work at Google.

Indeed, the founders of Google are now about as old as Vaughn and Wilson. Larry Page turned 40 on March 26th and Sergey Brin joins him on August 21st. Long ago, the founders joked that their first corporate jet was going to be a “party plane” with king-sized beds, but today they are married and live in the suburbs. One equally old Googler told me about how touched he was to have one of the founders roll up to a party in a Honda Odyssey driven by the founder, not a robot. In other words, they were very normal, they just happened to have plenty of money.

This fiction that Silicon Valley is powered by youth is an old game played by Silicon Valley. Almost every startup run by a teenage sensation has a greyhaired venture capitalist pulling the puppet strings. Arthur Rock, Mike Markkula and Andy Grove put up plenty of money to fund Apple Computer but somehow the story was always about Jobs and Wozniak. In most cases, the youth are run ragged on the hamster wheels with stock options dangled in front of them.

It’s a nice story that sells so well that Google and Vince Vaughn decided to repackage it as a movie. The kids do okay. They get fancy meals and decent salaries. But the movie doesn’t want to spend too much time dwelling upon the accuracy of this fiction. Just as Alfred Hitchcock said, “For me, the cinema is not a slice of life, but a piece of cake.” This movie takes that aphorism and improves it by making the cake free. If only life were that simple.

Bio: Peter Wayner is the author of more than dozen books and his latest are a history of "Death of a Salesman" and a forward-looking exploration of the impact of the self-driving car.

An anonymous reader writes "The next time a bear hits a car on a Russian highway, the video might be in high definition. A new wave of dashcams, on show at this week's Computex expo in Taipei, feature multiple enhancements on first-generation models that will probably be welcomed by law enforcement, insurance companies and the millions of people who browse YouTube looking at some of the amazing scenes captured from the front of a car. One of the current popular videos is of a May 2013 collision between a bear and a car (video). The accident, reportedly in Russia, sees the bear hit the front of the car and bounce off the car's windscreen before rolling several times to the side of the road. The video, and thousands of others like it, are typically shot in 480-line 'standard resolution,' but most of the new dashcams on show in Taipei this week offer 720 and 1080-line high definition." It's also becoming more common to repurpose old smartphones as dashcams using software like DailyRoads Voyager. If you've done so, what's your setup?

darthcamaro writes "One year ago today was the the official 'Launch Day' of IPv6. The idea was that IPv6 would get turned on and stay on at major carriers and website. So where are we now? Only 1.27% of Google traffic comes from IPv6 and barely 12 percent of the Alexa Top 1000 sites are even accessible via IPv6. In general though, the Internet Society is pleased with the progress over the last year. '"The good news is that almost everywhere we look, IPv6 is increasing," Phil Roberts,technology program manager at the Internet Society said. "It seems to be me that it's now at the groundswell stage and it all looks like everything is up and to the right."'"

It's not called Google Grand Canyon View, but Street View can show you what the canyon looks like even though there are no streets there -- or in the Meteor Crater or thousands of other places Google Street View Cars or tricycles or other vehicles can't go. How? With a 40 pound, human-carried version of the camera rig in the cars, complete with GPS and a "pause" button in case the human motive power system needs to take a break. But, asks Slashdot's Tim Lord, what about new, small cameras? Like GoPro? Don't they make the Trekker rig kind of obsolete? Well... Google's always working on "new and improved" everything, so the next version of the Trekker is likely to be kind of interesting.

It's not called Google Grand Canyon View, but Street View can show you what the canyon looks like even though there are no streets there -- or in the Meteor Crater or thousands of other places Google Street View Cars or tricycles or other vehicles can't go. How? With a 40 pound, human-carried version of the camera rig in the cars, complete with GPS and a "pause" button in case the human motive power system needs to take a break. But, asks Slashdot's Tim Lord, what about new, small cameras? Like GoPro? Don't they make the Trekker rig kind of obsolete? Well... Google's always working on "new and improved" everything, so the next version of the Trekker is likely to be kind of interesting.

It's not called Google Grand Canyon View, but Street View can show you what the canyon looks like even though there are no streets there -- or in the Meteor Crater or thousands of other places Google Street View Cars or tricycles or other vehicles can't go. How? With a 40 pound, human-carried version of the camera rig in the cars, complete with GPS and a "pause" button in case the human motive power system needs to take a break. But, asks Slashdot's Tim Lord, what about new, small cameras? Like GoPro? Don't they make the Trekker rig kind of obsolete? Well... Google's always working on "new and improved" everything, so the next version of the Trekker is likely to be kind of interesting.

sagecreek writes "You can judge this book, at least in part, by the lengthy tagline on its cover: 'Learn to make practical, unique, real-world sites that span a variety of industries and technologies with the world's most popular mobile development library.' jQuery might not be your favorite framework on the long, long list of JavaScript possibilities. But Shane Gliser unabashedly describes himself as a jQuery 'fanboy...if it's officially jQuery, I love it.' Gliser is an experienced mobile developer and blogger who operates Roughly Brilliant Digital Studios. He also has some background in mobile UX (user experience), and both qualities show in this smoothly written, well-illustrated, 234-page how-to book that focuses on jQuery Mobile, a 'touch-optimized' web framework for smartphones and tablets." Read below for the rest of sagecreek's review. Creating Mobile Apps With JQuery Mobile author Shane Gliser pages 234 pages publisher Packt Publishing rating 9/10 reviewer sagecreek ISBN 9781782160069 summary Takes the reader from mobile prototyping and creating templates to mobile development and creating versatile mobile sites, with a project in each chapter. Don't be surprised when you extract the book's code examples and related items from a ZIP file that is almost 100MB in size. Gliser covers a lot of ground, and he covers it well in his 10 chapters. And each chapter contains a project.

The first thing you don't do in Chapter 1, "Prototyping jQuery Mobile," is work at a computer. In the true spirit of UX, Gliser briefly has you work with a pen and some 3x5 note cards. (Remember those?) Your initial goal is to roughly sketch out some designs for a jQuery Mobile website for a new pizzeria. But why the ancient technology? "We are more willing to simply throw out a drawing that took less than 30 seconds to create," Gliser writes. And: "Actually sketching by hand uses a different part of the brain and unlocks our creative centers." Furthermore, those on your team who are not coders can contribute comments, suggestions, and corrections to the emerging design.

In Chapter 2, "A Mom-and-Pop Mobile Website," you step over to your computer with Chapter 1's paper prototype in hand. You start converting the sketched design "into an actual jQuery Mobile (jQM) site that acts responsively and looks unique." You also begin building "a configurable server-side PHP template," and you work with custom fonts, page curl effects using CSS, and other aspects of creating and optimizing a mobile site.

"Mobile is a very unforgiving environment," Gliser cautions, "and some of the tips in this section will make more difference than any of the 'best coding practices.'" Indeed, he wants you to be aware of optimization "at the beginning. You are going to do some awesome work and I don't want you or your stakeholders to think it's any less awesome, or slow, or anything else because you didn't know the tricks to squeeze the most performance out of your systems. It's never too early to impress people with the performance of your creations."

Chapter 3, "Analytics, Long forms, and Front-end Validation," moves beyond "dynamically link[ing] directly into the native GPS systems of iOS and Android." Instead, Gliser introduces how to work with Google static maps, Google Analytics, long and multi-page forms, and jQuery Validate. As for static maps, he says, "Remember to always approach things from the user's perspective. It's not always about doing the coolest thing we can." Indeed, a static map may be all the user needs to decide whether to drive to a business, such as a pizzeria, or just call for delivery. And, as for Google Analytics: "Every website should have analytics. If not, it's difficult to say how many people are hitting your site, if we're getting people through our conversion funnels, or what pages are causing people to leave our site."

Meanwhile, desktop users are familiar with (and frequently irritated by) long forms and multi-page forms. Lengthy forms can be real deal-breakers for users trying to negotiate them on mobile devices. The author presents some ways to shorten long forms and break them "into several pages using jQuery Mobile." And he emphasizes the importance of using the jQuery Validate plug-in to add validation to any page that has a form, so the user can see quickly and clearly that an entry has a problem.

The focus in Chapter 4, "QR Codes, Geolocation, Google Maps API, and HTML5 Video," is on handling concepts that can be "applied to any business that has multiple physical locations." Gliser uses a local movie theater chain as his development example. It is "considering throwing its hat into the mobile ring," so a site is created that makes use of QR codes, geolocation, Google Maps, and linking to YouTube movie previews. Then, he shows how to use embedded video to keep users on the movie chain's site rather than sending them off to YouTube.

In Chapter 5, the goal is "to create an aggregating news site based off social media." So the emphasis shifts to "Client-side Templating, JSON APIs, and HTML5 Web Storage." Notes Gliser: "Honestly, from a purely pragmatic perspective, I believe that the template is the perfect place for code. The more flexible, the better. JSON holds the data and the templates are used to transform it. To draw a parallel, XML is the data format and XSL templates are used to transform. Nobody whines about logic in XSL; so I don't see why it should be a problem in JS templates."

Next, he shows how to patch into Twitter's JSON API to get "the very latest set of trending topics" and "whittle down the response to only the part we want...and pass that array into JsRender for...well...rendering" in a manner that will be "a lot cleaner to read and maintain" than looping through JSON and using string concatenation to make the output.

Other topics in Chapter 5 include programmatically changing pages in jQuery Mobile, understanding how jQuery Mobile handles generated pages and Document Object Model (DOM) weight management, and working with RSS feeds. Gliser points out that there is still "a lot more information out there being fed by RSS feeds than by JSON feeds." The chapter concludes with looks at how to use HTML5 web storage (it's simple, yet it can get "especially tricky on mobile browsers"), and how to leverage the Google Feed API. Explains Gliser: "The Google Feeds (sic) API can be fed several options, but at its core, it's a way to specify an RSS or ATOM feed and get back a JSON representation."

Chapter 6 jumps into "the music scene. We're going to take the jQuery Mobile interface and turn it into a media player, artist showcase, and information hub that can be saved to people's home screens," Gliser writes. He proceeds to show how "ridiculously simple it can be to bring audio into your jQuery Mobile pages." And he explains how to use HTML5 manifest "and a few other meta tags" to save an app to the home screen. Furthermore, he discusses how to test mobile sites using "Google Chrome (since its WebKit) or IE9 (for the Windows Phone)" as browsers that are shrunken down to mobile size. "Naturally, this does not substitute for real testing," he cautions. "Always check your creations on real devices. That being said, the shrunken browser approach will usually get you 97.5 percent of the way there. Well...HTML5 Audio throws that operating model right out the window."

Since "mobile phones are quickly becoming our photo albums," Gliser's Chapter 7, "Fully Responsive Photography," begins with creating a basic gallery using Photoswipe. Then, in a section focused on "supporting the full range of device sizes," he shows how to start using responsive web design (RWD), "the concept of making a single page work for every device size." The issues, of course, range from image sizes and resolutions to text sizes and character counts per line, on screens as small as smart phones and tablets, or larger.

In Chapter 8, "Integrating jQuery Mobile into Existing Sites," three topics are key: (1) "Detecting mobile — server-side, client-side, and the combination of the two"; (2) "Mobilizing full site pages — the hard way"; and (3) Mobilizing full site pages — the easy way." Gliser avoids some potential "geek war" controversies over "browser sniffing versus feature detection" when detecting mobile devices. He zeroes in first on detection using WURFL for "server-side database-driven browser sniffing." He also shows how to do JavaScript-based browser sniffing, which he concedes may be "the worst possible way to detect mobile but it does have its virtues," especially if your budget is small and you want to exclude older devices that can't handle some new JavaScript templating. He also describes JavaScript-based feature detection using Modernizer, plus some other feature-detection methods.

As for mobilizing full-site pages "the hard way," he states that there is really "only one good reason: to keep the content on the same page so that the user doesn't have one page for mobile and one page for desktop. When emails and tweets and such are flying around, the user generally doesn't care if they're sending out the mobile view or the desktop view and they shouldn't." He focuses on how "it's pretty easy to tell what parts of a site would translate to mobile" and how to add data attributes to existing tags "to mobilize them. When jQuery's libraries are not present on the page, these attributes will simply sit there and cause no harm. Then you can use one of our many detection techniques to decide when to throw the jQM libraries in."

Mobilizing full-size pages "the easy way" involves, in his view, "nothing easier and cleaner than just creating a standalone jQuery Mobile page...and simply import the page we want with AJAX. We can then pull out the parts we want and leave the rest." His code samples show how to do this.

Chapter 9, "Content Management Systems and jQM" looks at the pros and cons of using three different content management systems (CMS) with jQuery Mobile: WordPress, Drupal, and Adobe Experience Manager. "The key to get up and running quickly with any CMS is, realizing which plugins and themes to use," Gliser writes. "For WordPress, I would not recommend a jQuery Mobile plugin. As I was experimenting for this chapter, it broke the admin interface and was, in general, a miserable experience. However, there are several jQuery Mobile themes that will serve you well. Some are free, some paid." He explains how to use mobile theme switchers.

Meanwhile, Drupal offers some standard plugins that provide contact forms, CAPTCHA, and custom database tables and forms, and enable you to "create full blown web apps, not just brochureware sites." But: "The biggest downside to Drupal is that it has a bit of a learning curve if yo want to tap its true power, Also, without some tuning, it can be a little slow and can really bloat your page's code," he says.

As for Adobe Experience Manager (AEM), Gliser merely introduces it as a "premier corporate CMS" and a "major CMS player that comes with complete jQuery Mobile examples." He doesn't show "how to install, configure, or code for AEM. That's a subject for several training manuals the size of this book." He adds: "If you work for a company that can afford AEM, you'll already be well-versed in the mobile implementation. The power this platform gives to content authors is astounding."

Chapter 10, the final chapter, is titled "Putting It All Together — Flood.FM." Using what you've learned in the book, including paper prototyping the interfaces, you create "a website where listeners will be greeted with music from local, independent bands across several genres and geographic regions."

Along the way, Gliser introduces Balsamiq, "a very popular UX tool for rapid prototyping." He discusses using Model-View-Controller (MVC), Model-View-ViewModel (MVVM), and Model-View-Whatever (MV*) development structures with jQuery Mobile. He introduces how to work with the Web Audio API , and he illustrates how to prompt users to download the Flood.FM app to their home screens. He finishes up with brief discussions of accelerometers, cameras, "APIs on the horizon," plus "To app or not to app, that is the question" and whether you should compile an app or not. Finally, he shows PhoneGap Build, the "cloud-based build service for PhoneGap."

Shane Gliser's book does indeed cover a lot of ground, clearly and with good examples. If you truly demand that some nits must be picked, I can report that an occasional dash is missing or a comma sometimes shows up out of place, such as this example in Chapter 2: "A practice is only best until a new practice, [misplaced comma] comes along that is better." In the printed book's table of contents, there are style and spelling glitches in the heading for Chapter 3. "Analytics, long forms, and frontend validation" should be "Analytics, Long Forms, and Front-end Validation." And, in Chapter 5, Gliser refers to the "Google Feeds API" when it's actually "Google Feed API." But the term "Google Feeds API" commonly is misused by developers on Stack Overflow and other sites.

I am not a mobile developer. I am a tech writer, frequent book reviewer, and occasional coder. I have played with some of the code examples in this book, but I have not tried them all. So I can't say if there are code glitches. However, the book was reviewed before publication by at least four software professionals with impressive resumes.

Aside from occasional spots where the text needed tighter editing, this book is, in my view, well written and rich with information, examples, sources, and tips for working effectively with jQuery Mobile. I intend to put it to good use as I continue learning.

You can purchase Creating Mobile Apps with jQuery Mobile from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page.

sagecreek writes "You can judge this book, at least in part, by the lengthy tagline on its cover: 'Learn to make practical, unique, real-world sites that span a variety of industries and technologies with the world's most popular mobile development library.' jQuery might not be your favorite framework on the long, long list of JavaScript possibilities. But Shane Gliser unabashedly describes himself as a jQuery 'fanboy...if it's officially jQuery, I love it.' Gliser is an experienced mobile developer and blogger who operates Roughly Brilliant Digital Studios. He also has some background in mobile UX (user experience), and both qualities show in this smoothly written, well-illustrated, 234-page how-to book that focuses on jQuery Mobile, a 'touch-optimized' web framework for smartphones and tablets." Read below for the rest of sagecreek's review. Creating Mobile Apps With JQuery Mobile author Shane Gliser pages 234 pages publisher Packt Publishing rating 9/10 reviewer sagecreek ISBN 9781782160069 summary Takes the reader from mobile prototyping and creating templates to mobile development and creating versatile mobile sites, with a project in each chapter. Don't be surprised when you extract the book's code examples and related items from a ZIP file that is almost 100MB in size. Gliser covers a lot of ground, and he covers it well in his 10 chapters. And each chapter contains a project.

The first thing you don't do in Chapter 1, "Prototyping jQuery Mobile," is work at a computer. In the true spirit of UX, Gliser briefly has you work with a pen and some 3x5 note cards. (Remember those?) Your initial goal is to roughly sketch out some designs for a jQuery Mobile website for a new pizzeria. But why the ancient technology? "We are more willing to simply throw out a drawing that took less than 30 seconds to create," Gliser writes. And: "Actually sketching by hand uses a different part of the brain and unlocks our creative centers." Furthermore, those on your team who are not coders can contribute comments, suggestions, and corrections to the emerging design.

In Chapter 2, "A Mom-and-Pop Mobile Website," you step over to your computer with Chapter 1's paper prototype in hand. You start converting the sketched design "into an actual jQuery Mobile (jQM) site that acts responsively and looks unique." You also begin building "a configurable server-side PHP template," and you work with custom fonts, page curl effects using CSS, and other aspects of creating and optimizing a mobile site.

"Mobile is a very unforgiving environment," Gliser cautions, "and some of the tips in this section will make more difference than any of the 'best coding practices.'" Indeed, he wants you to be aware of optimization "at the beginning. You are going to do some awesome work and I don't want you or your stakeholders to think it's any less awesome, or slow, or anything else because you didn't know the tricks to squeeze the most performance out of your systems. It's never too early to impress people with the performance of your creations."

Chapter 3, "Analytics, Long forms, and Front-end Validation," moves beyond "dynamically link[ing] directly into the native GPS systems of iOS and Android." Instead, Gliser introduces how to work with Google static maps, Google Analytics, long and multi-page forms, and jQuery Validate. As for static maps, he says, "Remember to always approach things from the user's perspective. It's not always about doing the coolest thing we can." Indeed, a static map may be all the user needs to decide whether to drive to a business, such as a pizzeria, or just call for delivery. And, as for Google Analytics: "Every website should have analytics. If not, it's difficult to say how many people are hitting your site, if we're getting people through our conversion funnels, or what pages are causing people to leave our site."

Meanwhile, desktop users are familiar with (and frequently irritated by) long forms and multi-page forms. Lengthy forms can be real deal-breakers for users trying to negotiate them on mobile devices. The author presents some ways to shorten long forms and break them "into several pages using jQuery Mobile." And he emphasizes the importance of using the jQuery Validate plug-in to add validation to any page that has a form, so the user can see quickly and clearly that an entry has a problem.

The focus in Chapter 4, "QR Codes, Geolocation, Google Maps API, and HTML5 Video," is on handling concepts that can be "applied to any business that has multiple physical locations." Gliser uses a local movie theater chain as his development example. It is "considering throwing its hat into the mobile ring," so a site is created that makes use of QR codes, geolocation, Google Maps, and linking to YouTube movie previews. Then, he shows how to use embedded video to keep users on the movie chain's site rather than sending them off to YouTube.

In Chapter 5, the goal is "to create an aggregating news site based off social media." So the emphasis shifts to "Client-side Templating, JSON APIs, and HTML5 Web Storage." Notes Gliser: "Honestly, from a purely pragmatic perspective, I believe that the template is the perfect place for code. The more flexible, the better. JSON holds the data and the templates are used to transform it. To draw a parallel, XML is the data format and XSL templates are used to transform. Nobody whines about logic in XSL; so I don't see why it should be a problem in JS templates."

Next, he shows how to patch into Twitter's JSON API to get "the very latest set of trending topics" and "whittle down the response to only the part we want...and pass that array into JsRender for...well...rendering" in a manner that will be "a lot cleaner to read and maintain" than looping through JSON and using string concatenation to make the output.

Other topics in Chapter 5 include programmatically changing pages in jQuery Mobile, understanding how jQuery Mobile handles generated pages and Document Object Model (DOM) weight management, and working with RSS feeds. Gliser points out that there is still "a lot more information out there being fed by RSS feeds than by JSON feeds." The chapter concludes with looks at how to use HTML5 web storage (it's simple, yet it can get "especially tricky on mobile browsers"), and how to leverage the Google Feed API. Explains Gliser: "The Google Feeds (sic) API can be fed several options, but at its core, it's a way to specify an RSS or ATOM feed and get back a JSON representation."

Chapter 6 jumps into "the music scene. We're going to take the jQuery Mobile interface and turn it into a media player, artist showcase, and information hub that can be saved to people's home screens," Gliser writes. He proceeds to show how "ridiculously simple it can be to bring audio into your jQuery Mobile pages." And he explains how to use HTML5 manifest "and a few other meta tags" to save an app to the home screen. Furthermore, he discusses how to test mobile sites using "Google Chrome (since its WebKit) or IE9 (for the Windows Phone)" as browsers that are shrunken down to mobile size. "Naturally, this does not substitute for real testing," he cautions. "Always check your creations on real devices. That being said, the shrunken browser approach will usually get you 97.5 percent of the way there. Well...HTML5 Audio throws that operating model right out the window."

Since "mobile phones are quickly becoming our photo albums," Gliser's Chapter 7, "Fully Responsive Photography," begins with creating a basic gallery using Photoswipe. Then, in a section focused on "supporting the full range of device sizes," he shows how to start using responsive web design (RWD), "the concept of making a single page work for every device size." The issues, of course, range from image sizes and resolutions to text sizes and character counts per line, on screens as small as smart phones and tablets, or larger.

In Chapter 8, "Integrating jQuery Mobile into Existing Sites," three topics are key: (1) "Detecting mobile — server-side, client-side, and the combination of the two"; (2) "Mobilizing full site pages — the hard way"; and (3) Mobilizing full site pages — the easy way." Gliser avoids some potential "geek war" controversies over "browser sniffing versus feature detection" when detecting mobile devices. He zeroes in first on detection using WURFL for "server-side database-driven browser sniffing." He also shows how to do JavaScript-based browser sniffing, which he concedes may be "the worst possible way to detect mobile but it does have its virtues," especially if your budget is small and you want to exclude older devices that can't handle some new JavaScript templating. He also describes JavaScript-based feature detection using Modernizer, plus some other feature-detection methods.

As for mobilizing full-site pages "the hard way," he states that there is really "only one good reason: to keep the content on the same page so that the user doesn't have one page for mobile and one page for desktop. When emails and tweets and such are flying around, the user generally doesn't care if they're sending out the mobile view or the desktop view and they shouldn't." He focuses on how "it's pretty easy to tell what parts of a site would translate to mobile" and how to add data attributes to existing tags "to mobilize them. When jQuery's libraries are not present on the page, these attributes will simply sit there and cause no harm. Then you can use one of our many detection techniques to decide when to throw the jQM libraries in."

Mobilizing full-size pages "the easy way" involves, in his view, "nothing easier and cleaner than just creating a standalone jQuery Mobile page...and simply import the page we want with AJAX. We can then pull out the parts we want and leave the rest." His code samples show how to do this.

Chapter 9, "Content Management Systems and jQM" looks at the pros and cons of using three different content management systems (CMS) with jQuery Mobile: WordPress, Drupal, and Adobe Experience Manager. "The key to get up and running quickly with any CMS is, realizing which plugins and themes to use," Gliser writes. "For WordPress, I would not recommend a jQuery Mobile plugin. As I was experimenting for this chapter, it broke the admin interface and was, in general, a miserable experience. However, there are several jQuery Mobile themes that will serve you well. Some are free, some paid." He explains how to use mobile theme switchers.

Meanwhile, Drupal offers some standard plugins that provide contact forms, CAPTCHA, and custom database tables and forms, and enable you to "create full blown web apps, not just brochureware sites." But: "The biggest downside to Drupal is that it has a bit of a learning curve if yo want to tap its true power, Also, without some tuning, it can be a little slow and can really bloat your page's code," he says.

As for Adobe Experience Manager (AEM), Gliser merely introduces it as a "premier corporate CMS" and a "major CMS player that comes with complete jQuery Mobile examples." He doesn't show "how to install, configure, or code for AEM. That's a subject for several training manuals the size of this book." He adds: "If you work for a company that can afford AEM, you'll already be well-versed in the mobile implementation. The power this platform gives to content authors is astounding."

Chapter 10, the final chapter, is titled "Putting It All Together — Flood.FM." Using what you've learned in the book, including paper prototyping the interfaces, you create "a website where listeners will be greeted with music from local, independent bands across several genres and geographic regions."

Along the way, Gliser introduces Balsamiq, "a very popular UX tool for rapid prototyping." He discusses using Model-View-Controller (MVC), Model-View-ViewModel (MVVM), and Model-View-Whatever (MV*) development structures with jQuery Mobile. He introduces how to work with the Web Audio API , and he illustrates how to prompt users to download the Flood.FM app to their home screens. He finishes up with brief discussions of accelerometers, cameras, "APIs on the horizon," plus "To app or not to app, that is the question" and whether you should compile an app or not. Finally, he shows PhoneGap Build, the "cloud-based build service for PhoneGap."

Shane Gliser's book does indeed cover a lot of ground, clearly and with good examples. If you truly demand that some nits must be picked, I can report that an occasional dash is missing or a comma sometimes shows up out of place, such as this example in Chapter 2: "A practice is only best until a new practice, [misplaced comma] comes along that is better." In the printed book's table of contents, there are style and spelling glitches in the heading for Chapter 3. "Analytics, long forms, and frontend validation" should be "Analytics, Long Forms, and Front-end Validation." And, in Chapter 5, Gliser refers to the "Google Feeds API" when it's actually "Google Feed API." But the term "Google Feeds API" commonly is misused by developers on Stack Overflow and other sites.

I am not a mobile developer. I am a tech writer, frequent book reviewer, and occasional coder. I have played with some of the code examples in this book, but I have not tried them all. So I can't say if there are code glitches. However, the book was reviewed before publication by at least four software professionals with impressive resumes.

Aside from occasional spots where the text needed tighter editing, this book is, in my view, well written and rich with information, examples, sources, and tips for working effectively with jQuery Mobile. I intend to put it to good use as I continue learning.

You can purchase Creating Mobile Apps with jQuery Mobile from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page.

Dawn Kawamoto writes "Twitter's free social media video app Vine is now on Android. But while the app rocked on the iOS platform, especially among teens, its move to Android has...dare I say...been a bit of a tangled mess. It launched on Google play without the capability for the two apps to sync, nor does it have such features as front-facing camera, search, mentions and hashtags. Another biggie is it doesn't yet allow users to post their six-second videos to Facebook. Vine says it's working on these features and all should be good soon. For now, however, a swing on the vine may not be a robust experience."