Slashdot Mirror

theodp writes On Tuesday, the State of Washington heard public testimony on House Bill 1813 (video), which takes aim at boy's historical over-representation in K-12 computer classes. To allow them to catch flights, representatives of Microsoft and Microsoft-bankrolled Code.org were permitted to give their testimony before anyone else ("way too many young people, particularly our girls...simply don't have access to the courses at all," lamented Jane Broom, who manages Microsoft's philanthropic portfolio), so it's unclear whether they were headed to the airport when a representative of the WA State Superintendent of Public Instruction voiced the sole dissent against the Bill. "The Superintendent strongly believes in the need to improve our ability to teach STEM, to advance computer science, to make technology more available to all students," explained Chris Vance. "Our problem, and our concern, is with the use of the competitive grant program...just providing these opportunities to a small number of students...that's the whole basic problem...disparity of opportunity...if this is a real priority...fund it fully" (HB 1813, like the White House K-12 CS plan, counts on philanthropy to make up for tax shortfalls). Hey, parents of boys are likely to be happy to see another instance of educators striving to be more inclusive than tech when it comes to encouraging CS participation!

hypnosec writes The European Space Agency has successfully completed the first test flight of its Intermediate eXperimental Vehicle (IXV), as planned, wherein it saw the wingless spaceplane land in one piece in the Pacific Ocean. A Vega VV04 rocket took the IXV to an altitude of 340 km, from which it separated and continued up to 412 km. Reentering from this suborbital path, it recorded a vast amount of data from more than 300 advanced and conventional sensors. According to ESA the spaceplane few east around the globe during its descent and finally landed safely in the the Pacific Ocean west of the Galapagos Islands at about 15:20 GMT.

jjohn24680 writes There are several sources who are reporting layoffs at Daybreak Games (formerly Sony Online Entertainment) today. Notable layoffs include Linda "Brasse" Carlson (former Global Community Relations Lead) and Dave Georgeson (former Director of Development / Franchise Director for Everquest, EverQuest II, and EverQuest Next / Landmark). This post from Daybreak Games has some additional information as well.

hypnosec writes: Artificial leaf techology made waves the moment it was announced by Daniel Nocera back in 2011. His latest research, published in PNAS, involves gathering hydrogen from this artificial leaf, carbon dioxide from another source, and feeding it to Ralstonia eutropha bacteria to create liquid fuel. Once the materials are fed to the bacteria, "An enzyme takes the hydrogen back to protons and electrons, then combines them with carbon dioxide to replicate—making more cells. Next, ... new pathways in the bacterium are metabolically engineered to make isopropanol." Researchers say the same process could be used to make vitamins.

hypnosec writes: Artificial leaf techology made waves the moment it was announced by Daniel Nocera back in 2011. His latest research, published in PNAS, involves gathering hydrogen from this artificial leaf, carbon dioxide from another source, and feeding it to Ralstonia eutropha bacteria to create liquid fuel. Once the materials are fed to the bacteria, "An enzyme takes the hydrogen back to protons and electrons, then combines them with carbon dioxide to replicate—making more cells. Next, ... new pathways in the bacterium are metabolically engineered to make isopropanol." Researchers say the same process could be used to make vitamins.

mpicpp sends this news from CNET: Reports are emerging that Samsung smart TVs have begun inserting short advertisements directly into video streaming apps, with no influence from the third-party app providers. The news comes just days after Samsung made headlines for another incursion into users' lounge rooms, when it was revealed that its TV voice recognition software is capable of capturing personal information and transmitting it to third parties. ... The issue has been reported on the Plex streaming service — a brand of media player that allows users to stream their own video from a personal library or hard drive and push it to a smart TV. Samsung says this was not intentional, and that they've fixed it so the ads should no longer show up.

eldavojohn writes: If you didn't partake in the DDOS attack on Dragonmount as fans tried to figure out just what the %&#% was going on last night, you should probably prepare yourself for Billy Zane filled disappointment and watch a curious pilot covering the prologue of The Eye of the World by Robert Jordan that apparently aired around 01:30 AM Eastern time on FXX. The reviews of said pilot are unkind and appear to contain question marks all the way down starting with Jordan's Widow disavowing its authorization.

The world of film and TV development is a confusing one, but it appears that NBC initially bought options to turn it into a mini series which were then optioned by Universal/Red Eagle Entertainment in conjunction with Red Eagle Games to do a coordinated release. Red Eagle games announced a combined effort with Jet Set games and around 2012 began releasing information on an "Aiel War" project to target mobile gaming platforms. But that appeared to die with its failed kickstarter attempt. It is suspected that Red Eagle Entertainment is behind the odd FXX airing last night. Was this an eleventh hour "use it or lose it" move by Red Eagle Entertainment without Universal's knowledge? In any case, it was a secretive, odd, low-budget, disappointing start to The Wheel of Time in film.

MicroHex writes: Boston Dynamics, creators of "Big Dog" recently unveiled their newest creation, "Spot." Originally funded by DARPA to develop the technology behind Big Dog, Boston Dynamics is currently owned by Google and continues its robotics research. From the video: "Spot is a four-legged robot designed for indoor and outdoor operation. It is electrically powered and hydraulically actuated. Spot has a sensor head that helps it navigate and negotiate rough terrain. Spot weighs about 160 lbs."

A few days ago, we posted a story that asked whether posting horrific videos online served a legitimate journalistic purpose; some images that are shocking in their violence are now routinely available, including and especially the recent video of Jordanian pilot Muath al-Kaseasbeh being burned alive. Matthew Ingram writes at GigaOm that, whatever you think of the motives or results of the traditional news media showing such videos or choosing not to, there's good reason for social media sites not to reflexively remove such content.

The SpaceX two-fer launch that was scheduled for today has been scrubbed. NBC News reports that the launch was postponed until Monday at the earliest due to a problem with the range-tracking system in Florida. That means an ambitious second attempt to land the Falcon 9 rocket's first stage on an oceangoing platform will also have to be delayed. ... Satellites such as the Advanced Composition Explorer and Solar and Heliospheric Observatory, which are already located at the L1 point, can provide up to an hour's warning of major storms. Both those satellites are well past their anticipated lifetimes, however, and DSCOVR is designed to provide a much-needed backup. SpaceX's two-stage Falcon 9 rocket will boost DSCOVR into a preliminary orbit, but it will take 110 days of in-space maneuvers to get the probe into the right position. This launch would mark the first time that SpaceX has sent a spacecraft so far, and it will be judged a success if DSCOVR reaches its intended orbit. The delayed launch could take place as soon as tomorrow (Monday) evening.

The New York Times reports that SpaceX will again attempt to recover a Falcon 9 launch vehicle, after the recent unsuccessful try; the company believes the lessons from the earlier launch have been learned, and today's launch will be loaded with more hydraulic fluid. This evening, the rocket is to loft the satellite nicknamed "GoreSat," after Al Gore, who envisioned it as a sort of permanent eye in space beaing back pictures of Earth from afar. The purpose of the satellite has evolved, though: Writes the Times: The observatory, abbreviated as Dscovr and pronounced “discover,” is to serve as a sentinel for solar storms: bursts of high-energy particles originating from the sun. The particles from a gargantuan solar storm could induce electrical currents that might overwhelm the world’s power grids, possibly causing continent-wide blackouts. Even a 15-minute warning could let power companies take actions to limit damage.

A few days ago, Fast Company reviewer Jay Cassano was enthusiastic about Ubuntu's approach to apps for its new phone OS: namely, not relying on them, and instead interfacing seamlessly with existing websites and protocols. Now, new submitter ablutions (4006541) writes with a less than glowing review at The Daily Dot of the actual hardware that the OS is launching on. A sample that conveys the gist: Let's start with the good stuff: It sports a 4.5-inch multi-touch screen and a respectable 8-megapixel rear camera and 5-megapixel lens on the front. That's pretty much it. The list of negatives is a bit longer.

0x2A (548071) writes BMW recently fixed a security hole in their ConnectedDrive software, which left 2.2 million cars open to remote attacks. Security expert Dieter Spaar reverse engineered the system and found some serious flaws [note: if you'd prefer English to German, try this translation], including using the same symmetric keys in all vehicles, not encrypting messages between the car and the BMW backend or using the outdated DES.

An anonymous reader writes: You may recall last September when Mozilla and a new company named Matchstick announced a Kickstarter project for a new device that would compete with Google's Chromecast. It was an HDMI dongle for streaming media that runs on Firefox OS. They easily quadrupled their $100,000 funding goal, and estimated a ship date of February, 2015. Well, they emailed backers today to say that the Matchstick's release is being pushed back to August. They list a few reasons for the delay. For one, they want to upgrade some of the hardware: they're swapping the dual-core CPU for a quad-core model, and they're working on the Wi-Fi antenna to boost reception. But on the software side, the biggest change they mention is that they're adding support for DRM. This is a bit of a surprise, since all they said on the Kickstarter about DRM was that they hoped it would be handled "either via the playback app itself or the OS." Apparently this wasn't possible, so they're implementing Microsoft PlayReady tech on the Matchstick.

jones_supa writes: Soon after the poor state of the GnuPG was unveiled, the online community has rallied to help Werner Koch. He wanted to hire a full-time programmer to work on the project alongside him and to ensure that he's not living on the brink of bankruptcy all the time. Immediately after the article was published, it was revealed that he got a one-time grant of $60,000 from the Linux Foundation's Core Infrastructure Initiative. Also, the community donated over $150,000, and Facebook and Stripe have each pledged to provide $50,000 per year. All in all, it looks like Werner Koch won't be worried about funding for quite some time. The problem remains: it's very likely that other projects just as important as this one are probably facing the same kind of issues, but it would be nice to hear about them before they get in trouble, and not after.

theodp writes: Cereal and fast food companies found cartoons an effective way to market to children. Google is apparently hoping to find the same, as it teams with Disney Junior on a cartoon to help solve its computer science "pipeline" problem. The LA Times reports the tech giant worked with the children's channel on the new animated preschool series Miles From Tomorrowland, in an effort to get kids — particularly girls — interested in computer science. The program, which premieres Friday, introduces the preschool crowd to Miles Callisto, a young space adventurer, and his family — big sister (and coder extraordinaire) Loretta and their scientist parents Phoebe and Leo. Google engineers served as consultants (YouTube video) on the show. "When we did our computer science research, we found the No. 2 reason why girls in particular are not pursuing it as a career is because their perception was fairly negative and they associated it as a field for boys," said Julie Ann Crommett, Google's program manager for computer science in media. Can't wait for the episode where Google and Disney conspire to suppress Loretta's wages!

gemtech writes RadioShack has declared bankruptcy today. As reported Monday, the company has struck a deal to sell up to 2,400 of its approximately 4,000 stores to Sprint. From the article: "RadioShack said the remaining stores are expected to close. The company's franchise locations, as well as stores in Mexico and Asia, are not included in the deal. The bankruptcy announcement is no surprise. The New York Stock Exchange suspended trading of its shares on Monday. And RadioShack workers have told CNNMoney that some locations have already been converted to clearance stores."

Nerval's Lobster writes Developers assume that Swift, Apple's newish programming language for iOS and Mac OS X apps, will become extremely popular over the next few years. According to new data from RedMonk, a tech-industry analyst firm, Swift could reach that apex of popularity sooner rather than later. While the usual stalwarts—including JavaScript, Java, PHP, Python, C#, C++, and Ruby—top RedMonk's list of the most-used languages, Swift has, well, swiftly ascended 46 spots in the six months since the firm's last update, from 68th to 22nd. RedMonk pulls data from GitHub and Stack Overflow to create its rankings, due to those sites' respective sizes and the public nature of their data. While its top-ranked languages don't trade positions much between reports, there's a fair amount of churn at the lower end of the rankings. Among those "smaller" languages, R has enjoyed stable popularity over the past six months, Rust and Julia continue to climb, and Go has exploded upwards—although CoffeeScript, often cited as a language to watch, has seen its support crumble a bit.

McGruber writes The same Georgia State University art project responsible for Monday's shutdown of Atlanta's Downtown Connector (Interstates 75 & 85), caused authorities in the south Fulton County, Georgia town of Hapeville to evacuate businesses and call in a bomb squad Tuesday.

According to Georgia State University spokesman Don Hale, the devices are pinhole camera being used in a solargraphy project to track the rising and setting of the sun over a three-month period. "Students were instructed to take their cameras home and to place them in locations that would provide interesting scenes with bright sunlight," Hale said. "The locations were selected by the students."

It was up to each of the 18 students in the class to find a spot for their own project, the university said. The university was made aware of the art project Tuesday morning and, through its police department, immediately informed the Atlanta Police Department, Hale said.

A while ago you had a chance to ask Executive Director of the Tor project Andrew Lewman about fighting laws and technology that threaten anonymity and the importance of privacy. Below you'll find his answers to your questions. The NSA TrueCrypt Ploy Again?
by TechForensics

How can we ever be sure Tor has not morphed into an eviscerated TrueCrypt and that at some point, after achieving their means of compromise, the NSA won't force a version they can easily backdoor on the public?

They like to compromise software and then put it back, so it becomes an intelligence asset. In my understanding only a legal technicality allowed TrueCrypt to issue a cryptic public announcement which effectively let the public know TrueCrypt was potentially compromised. I wonder whether the NSA will even allow Tor to recommend a transparently ineffective alternative.

Lewman: No agency has ever asked Tor to put in lawful intercept access, also known as a “backdoor.” Tor is not subject to the same legal requirements as other Internet service providers or content providers to incorporate that into the system. Our FAQ answer states this clearly.

How can strategies be drawn so if Tor is easily, possibly undetectably breached, the public will have some inkling of it?

Lewman: Tor maintains an open community and believes in transparency. We always strive to report out as quickly as we can about any issues affecting the Tor network.



Cryptowall 2.0
by Anonymous Coward

Cryptowall 2.0 is using state of the art cryptographic services like Tor, Bitcoin, and file encryption, combined with standard exploits to hold data ransom. I think it's among the more sophisticated attacks I've ever seen. How do you think more malware of this type will pressure you to change the service?

Lewman: Tor is used by millions of people for legitimate purposes and certainly anytime someone uses technology in a way that harms other people, we are disheartened. Our approach to this is, and has been, to work with malware researchers and law enforcement to help people remove the malware or to change the incentives behind including Tor in the malware at all.



Tor connections
by Anonymous Coward

Why hasn't TOR moved towards a connectionless routing between the client and the exit node? A permanent connection is being established each time with the same pattern: computer -> entry node -> middle node -> exit node -> website. This can lead to a traffic pattern analysis, given an observer with enough "peer exchange nodes" under his monitoring. In some cases all the connections could be monitored with only country/continent level entry points. Wouldn't a bunch of state-less P2P like connections between the client and the exit node be better suited against such traffic inspection?

Lewman: We would love to get to the point that Tor could provide a connectionless routing between client and exit node that does not compromise anonymity. It is something that we have thought about for a while and started research on a while back. More research on this needs to be done in order to roll it out to the Tor network. We would love for someone to help further study that and help us figure out how to make that happen.



Have you used I2P...
by Anonymous Coward

And what are your thoughts on its design compared to Tor and as a complement to it?

Lewman: We try to keep up with any new technology that emerges and have tried many of the different online privacy products and software out there- I2P, Freenet, Retroshare, GNUNet and others certainly have some interesting work and research about online privacy. We are open to collaborating with anyone that shares our mission of protecting online security and anonymity for users.



Balance between simple privacy and lawlessness
by TWX

Tor can be used for good and for evil. How do you go about attempting to design the features of Tor to maximize one and minimize the other?

Lewman: The Tor network is designed to provide protection online for ordinary citizens, victims of abuse, and individuals in dangerous parts of the world share information over public networks without compromising their anonymity. Most of the people that use Tor have legitimate uses for wanting privacy such as activists or reporters that need to keep their locations private. Criminals can already do bad things and there are certainly lots of options available to them for breaking the laws.



Re:Balance between simple privacy and lawlessness
by mlts

Along the lines to this question, how can Tor's PR be helped? As of now, part of an IT person's job is to block Tor's exit nodes, on the application, kernel, and router level, because those nodes to be a source of many attacks. So, because of the bad reputation, it gets entirely locked out of many websites. This can be fixed by running a VPN over Tor so the exit comes from the VPN's servers, but there goes the anonymity for the most part.

Lewman: With so much concern these days about people’s privacy being compromised online, I would love more businesses to take a look at how Tor could help them protect their confidential documents like patents, product development ideas, or financial documents. Even in some situations when a company is doing competitive intelligence research online and it's important that the competitor does not know, it keeps the competitor from knowing that someone is looking at them online.



What is your biggest fear?
by AmiMoJo

What is your biggest fear? After the TrueCrypt developers were apparently threatened or otherwise convinced to abandon development, does the NSA worry you? The FBI has been complaining about encryption lately too, as have law enforcement agencies in other countries. Or is there something else that concerns you?

Lewman: My biggest concern is making sure that the 2.5 million people around the world that currently use Tor and the thousands of new people that download it every day, have a safe, reliable way to protect their privacy online.



Tor has been compromised
by kheldan

News stories I've read lately seem to indicate that the Tor exit nodes have been and still are being compromised by organizations and some oppressive governments. What are you doing about this?

Lewman: The Tor network has been around for 10 years and it has never been successfully hacked. Many have tried and many more will try. We work with researchers all the time to improve the network.



Darknet takedowns.
by brokenin2

Do you know how the takedown of so many "darknet" sites was accomplished recently, or do you at least have some suspicions? The government seems to by lying about how they took down the original Silk Road site, and I'm wondering if you believe this is to: a) Hide a technical solution that they have at their disposal, or b) Hide the egregiously illegal/inadmissable things they did to accomplish this, or c) some of each.

Lewman: We have no knowledge of how the agencies working together "took down” silkroad and other darknet sites but news reports vary widely on the actual number of sites that were taken down. We've been watching carefully to try and learn if there are any flaws with Tor that we need to correct. Nothing so far about this case makes us think they found a way to compromise the Tor software or network. The FBI says that their suspect made mistakes in operational security and was found through actual detective work.

An anonymous reader writes: As part of Microsoft's continuing project to open source the .NET framework, the company has announced that CoreCLR, the execution engine for .NET Core, is now available on GitHub. CoreCLR handles things like garbage collection, compilation to machine code, and IL byte code loading. The .NET team said, "We have released the complete and up-to-date CoreCLR implementation, which includes RyuJIT, the .NET GC, native interop and many other .NET runtime components. ... We will be adding Linux and Mac implementations of platform-specific components over the next few months. We already have some Linux-specific code in .NET Core, but we're really just getting started on our ports. We wanted to open up the code first, so that we could all enjoy the cross-platform journey from the outset."

itwbennett writes: The Federal Aviation Administration has issued eight more commercial drone licenses, the latest approvals for several hundred applications it has received. The newest licenses went to companies planning to use drones for video and TV production, aerial photography and surveying and inspecting flare stacks in the oil, natural gas and petro-chemical industry. Other readers sent in followups to last week's stories about an enthusiast's drone that crashed onto the White House grounds, and the subsequent firmware update from the drone's manufacturer to enforce a no-fly zone in that area. The EFF argues that this is a shortsighted solution and only serves to highlight how the concept of ownership is increasingly being pulled out of users' hands. Meanwhile, such "no-fly zone" updates give rise to a host of liability issues for manufacturers and enthusiasts alike.

itwbennett writes: The Federal Aviation Administration has issued eight more commercial drone licenses, the latest approvals for several hundred applications it has received. The newest licenses went to companies planning to use drones for video and TV production, aerial photography and surveying and inspecting flare stacks in the oil, natural gas and petro-chemical industry. Other readers sent in followups to last week's stories about an enthusiast's drone that crashed onto the White House grounds, and the subsequent firmware update from the drone's manufacturer to enforce a no-fly zone in that area. The EFF argues that this is a shortsighted solution and only serves to highlight how the concept of ownership is increasingly being pulled out of users' hands. Meanwhile, such "no-fly zone" updates give rise to a host of liability issues for manufacturers and enthusiasts alike.

MojoKid writes: With limited choice and often dismal upstream speeds, it's no wonder many people are excited to hear that newcomers like Google Fiber are expanding super-fast gigabit internet across the country. But some Americans also have access to other high-speed fiber internet options that compete with the big guys like Comcast and Time Warner Cable: municipal internet. In the case of the small town of Wilson, NC, town officials first approached Time Warner Cable and Embarq, requesting faster Internet access for their residents and businesses. Both companies, likely not seeing a need to "waste" resources on a town of just 47,000 residents, rebuffed their demands. So what did Wilson do? It spent $28 million dollars to build its own high-speed Internet network, Greenlight, for its residents, offering faster speeds and lower prices than what the big guys could offer. And wouldn't you know it; that finally got the big telecoms to respond.

However, the response wasn't to build-out infrastructure in Wilson or compete on price; it was to try and kill municipal broadband efforts altogether in NC, citing unfair competition. NC's governor at the time, Bev Perdue, had the opportunity to veto the House bill that was introduced, but instead allowed it to become law. However, a new report indicates that the FCC is prepared to side with these smaller towns that ran into roadblocks deploying and maintaining their own high-speed Internet networks. The two towns in question include aforementioned Wilson, and Chattanooga, TN. Action by the FCC would effectively strike down the laws — like those that strangle Greenlight in Wilson — which prevent cities from undercutting established players on price. The FCC is also expected to propose regulating internet service as a utility later this week.

eldavojohn writes Core HTML5 2D Game Programming details a journey through creating Snail Bait in well defined steps. This simple two dimensional platform game works as a great starting point for anyone interested in making their very first game targeting many desktop and mobile platforms. This incremental process is expertly segmented into logical lessons with the only prerequisite being fluency in JavaScript. One of the most attractive aspects of this book is that the core concepts of this book don't rely on some flavor of the week JavaScript library or framework. Read below for the rest of eldavojohn's review. Core HTML5 2D Game Programming author David Geary pages 615 pages publisher Prentice Hall rating 9/10 reviewer eldavojohn ISBN 9780133564242 summary An exercise in 2D game development and mechanics in HTML5 and JavaScript. First, this book isn't for people who do not recognize HTML5 and JavaScript as a valid development platform for games. I know you're out there, you can stop reading here and move on to the next article. This book isn't for you. If you have no programming experience this book is likely not for you either. This book dives into concepts faster than Geary's last book on game development in Canvas. You should also be familiar with JavaScript if you want to effortlessly start on this book. Throughout the book, Geary utilizes object's JavaScript prototypes to add functions, uses anonymous functions and refers to common programming patterns.

It is worth repeating that the implementation in this book does not rely on a framework or library that could change or go defunct. The game runs entirely on code covered in the book accessing W3C standard specifications like requestAnimationFrame(). As long as JavaScript interpreters don't change core things like timing control, this book should be relevant to developers for years to come.

The reason this book gets a nine is it accomplishes everything it sets out to do and Geary does a great job dividing up task after incremental task of setting sprite sheets and backgrounds into motion. The reason it doesn't get a ten is that I was personally disappointed with the the author devoting little time to physics and their simulations.

The book is laid out to enable its use as two kinds of resources: cover to cover and chapter specific topics. Reading this straight through, there were only a few times where it felt like I was needlessly being reminded of where I had already read about tangential topics. On the plus side if you ever want to see how Snail Bait implemented something like sound, you need only spend time on the chapter devoted to sound sprites. One mild annoyance I had with the text was that the author seems to always refer to Snail Bait as "Snail Bait" which leads to a Ralph Wiggum-like aversion to pronouns or saying "the game" instead occasionally. It might only be me but it can become tiresome to read "Snail Bait" five or six times on the same page.

You can read a sample chapter here that shows how to implement sprite behaviors.

The first two chapters of the book focus on a set of basic guidelines to follow when doing game development in HTML5 and JavaScript — like keeping certain UI display elements in CSS instead of rendering them as paths or objects in the Canvas. Geary also covers the very absolute simplest concepts of how graphics are going to be displayed and how the background is going to move. He also spends time in Chapter Two showing how to best set up the development environment. It is demonstrated how shortening your cycle of deployment saves you tons of time and the author does a great job on letting you know what tools to use to debug throughout the whole text.

The third chapter delves into draw and rendering graphics in the canvas as well as introducing the reader to the game loop. It spends a good amount of time explaining the use of animation frame control in a browser to keep animations running smoothly. It also begins the auditing of frame rates so that the game can respond to and display things normalized at the rate the user is experiencing them. It also touches on how parallax can be employed to show things closer up moving faster than those further back in the background. This illusion of depth has long been popular and is even finding its way into scrolling on blogs and I wish that Geary would have spent more time on this perhaps in a later chapter but offer the reader more on how to do multiple levels of depth.

The next chapter tackles the core infrastructure of Snail Bait and discusses at length encapsulation of certain functionalities (instead of globals) in the source code as well as Snail Bait's 2300 line prototype. It bothers me that one file is 2300 lines and I wish there was a better way to do this but as a learning tool, it works even if it is daunting to scroll through. The book adds some helpful pointers about how utterly confusing the "this" keyword can be in JavaScript. Chapter Four really sets the pace for the rest of the book by introducing the use of event listeners and illustrating how the game loop is going to continually be extrapolated.

The next three chapters cover the use of loading screens, sprites and their behaviors. Snail Bait uses all its graphics from an open source game (Replica Island). But if you were to design your own graphics for your game, these chapters do a great job of showing how to construct sprite sheets and how to use tools to construct metadata in the code so that the sprites are usable by the sprite artists. Using the flyweight pattern, Geary sets the stage for more complex behaviors and actions to come in the following chapters.

The next three chapters cover time, stopwatches and their effects on motions and behaviors within the game. The author starts and works from linear motion to non-linear motion and then using transducer functions to affect the time system. The game now has bouncing coins, a jumping player and Geary does a good job of showing the reader how to emulate behaviors in the code.

Naturally what follows next is collision detection and gravity. The collision detection strategies were adequate but I wish that there was more depth at least referenced in the text. This isn't a simple problem and I did like how Geary referenced back to chapter two's profile and showed how collision detection performance as you implement and refine and optimize your algorithm. The nice thing about this book is that it often tackles problems with a general solution in the code (runner/sprite collision) and then provides the edge case solutions.

In the fourteenth chapter, the author tackles something that has long been a plague in HTML5 games: sound and music. The author doesn't sugarcoat this citing the long history of problems the vendors have had trying to support this in browsers. There's a great explanation of how to create and handle "sound sprites" (similar to sprite sheets) so that there is only one download for background music and one download for audio sprites.

Next Geary covers the problem of multiple viewport sizes with a focus on mobile devices. Of course this is one of the biggest issues with mobile gaming today. The chapter is lengthy and deals with the many intricacies of scaling, sizing and touch events. This chapter is long but the highly detailed support of multiple platforms and resolutions is a justified discussion point.

In sixteen, the reader gets a treatment of utilizing sprites and their artists to simulate sparks and smoking holes. The book calls this chapter "particle systems" but I don't think that's a very good title as the code isn't actually dealing with things at the particle level. Instead this chapter focuses on using sprites to simulate those behaviors via animation. This is completely necessary on a computation inexpensive platform but it is misleading to call these particle systems.

Now that the game looks and functions appropriately, the book covers UI elements like player scores and player lives. The auditing of these metrics are covered in the code as well as warnings when the game begins to run to slowly. It also covers the 'edge' condition of winning in the game and the routine that is followed when the user wins the game.

The next chapter introduces the concept of a developer backdoor so that the reader can manually speed up or slow down the game while playing it or even test special cases of the runner sprite interacting with other elements. It's a useful trick for debugging and playing around but does devote a lot of time to the specialized UI like the speed slider and other things that won't (or rather shouldn't) be seen by a common player.

Chapter nineteen really felt out of place and very inadequate on important details. It's a blind rush through using node.js and socket.io to implement server side high scores. The way it's implemented would make it trivial for someone to submit a high score of MAX_INT or whatever to the server. The metrics reporting is done in a manner that (in my opinion) breaks from long established logging structure one would be familiar with. While it covers important things to record from your users in order to tweak your game, the inadequacy of discussions about shortcomings makes it feel out of place in this text. It's a topic of great depth and I have no problem with an author touching on something briefly in one chapter — this chapter does lack the warnings and caveats found in other chapters though.

Contrary to the previous chapter, the final chapter is a fast application of the entire book's principles applied to a new game (Bodega's Revenge). Geary gives a final run through showing how the lengthy prior discussions quickly translate to a new set of sprite sheets and game rules. If this book is ever expanded, I think it would be great to include additional chapters like this although I would pick a more distinct and popular two dimensional game format like a tower defense game or a bejeweled knockoff.

Overall, Core HTML5 2D Game Programming is a great book for a JavaScript developer looking to dabble in game development. You can purchase Core HTML5 2D Game Programming 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. If you'd like to see what books we have available from our review library please let us know.

eldavojohn writes Core HTML5 2D Game Programming details a journey through creating Snail Bait in well defined steps. This simple two dimensional platform game works as a great starting point for anyone interested in making their very first game targeting many desktop and mobile platforms. This incremental process is expertly segmented into logical lessons with the only prerequisite being fluency in JavaScript. One of the most attractive aspects of this book is that the core concepts of this book don't rely on some flavor of the week JavaScript library or framework. Read below for the rest of eldavojohn's review. Core HTML5 2D Game Programming author David Geary pages 615 pages publisher Prentice Hall rating 9/10 reviewer eldavojohn ISBN 9780133564242 summary An exercise in 2D game development and mechanics in HTML5 and JavaScript. First, this book isn't for people who do not recognize HTML5 and JavaScript as a valid development platform for games. I know you're out there, you can stop reading here and move on to the next article. This book isn't for you. If you have no programming experience this book is likely not for you either. This book dives into concepts faster than Geary's last book on game development in Canvas. You should also be familiar with JavaScript if you want to effortlessly start on this book. Throughout the book, Geary utilizes object's JavaScript prototypes to add functions, uses anonymous functions and refers to common programming patterns.

It is worth repeating that the implementation in this book does not rely on a framework or library that could change or go defunct. The game runs entirely on code covered in the book accessing W3C standard specifications like requestAnimationFrame(). As long as JavaScript interpreters don't change core things like timing control, this book should be relevant to developers for years to come.

The reason this book gets a nine is it accomplishes everything it sets out to do and Geary does a great job dividing up task after incremental task of setting sprite sheets and backgrounds into motion. The reason it doesn't get a ten is that I was personally disappointed with the the author devoting little time to physics and their simulations.

The book is laid out to enable its use as two kinds of resources: cover to cover and chapter specific topics. Reading this straight through, there were only a few times where it felt like I was needlessly being reminded of where I had already read about tangential topics. On the plus side if you ever want to see how Snail Bait implemented something like sound, you need only spend time on the chapter devoted to sound sprites. One mild annoyance I had with the text was that the author seems to always refer to Snail Bait as "Snail Bait" which leads to a Ralph Wiggum-like aversion to pronouns or saying "the game" instead occasionally. It might only be me but it can become tiresome to read "Snail Bait" five or six times on the same page.

You can read a sample chapter here that shows how to implement sprite behaviors.

The first two chapters of the book focus on a set of basic guidelines to follow when doing game development in HTML5 and JavaScript — like keeping certain UI display elements in CSS instead of rendering them as paths or objects in the Canvas. Geary also covers the very absolute simplest concepts of how graphics are going to be displayed and how the background is going to move. He also spends time in Chapter Two showing how to best set up the development environment. It is demonstrated how shortening your cycle of deployment saves you tons of time and the author does a great job on letting you know what tools to use to debug throughout the whole text.

The third chapter delves into draw and rendering graphics in the canvas as well as introducing the reader to the game loop. It spends a good amount of time explaining the use of animation frame control in a browser to keep animations running smoothly. It also begins the auditing of frame rates so that the game can respond to and display things normalized at the rate the user is experiencing them. It also touches on how parallax can be employed to show things closer up moving faster than those further back in the background. This illusion of depth has long been popular and is even finding its way into scrolling on blogs and I wish that Geary would have spent more time on this perhaps in a later chapter but offer the reader more on how to do multiple levels of depth.

The next chapter tackles the core infrastructure of Snail Bait and discusses at length encapsulation of certain functionalities (instead of globals) in the source code as well as Snail Bait's 2300 line prototype. It bothers me that one file is 2300 lines and I wish there was a better way to do this but as a learning tool, it works even if it is daunting to scroll through. The book adds some helpful pointers about how utterly confusing the "this" keyword can be in JavaScript. Chapter Four really sets the pace for the rest of the book by introducing the use of event listeners and illustrating how the game loop is going to continually be extrapolated.

The next three chapters cover the use of loading screens, sprites and their behaviors. Snail Bait uses all its graphics from an open source game (Replica Island). But if you were to design your own graphics for your game, these chapters do a great job of showing how to construct sprite sheets and how to use tools to construct metadata in the code so that the sprites are usable by the sprite artists. Using the flyweight pattern, Geary sets the stage for more complex behaviors and actions to come in the following chapters.

The next three chapters cover time, stopwatches and their effects on motions and behaviors within the game. The author starts and works from linear motion to non-linear motion and then using transducer functions to affect the time system. The game now has bouncing coins, a jumping player and Geary does a good job of showing the reader how to emulate behaviors in the code.

Naturally what follows next is collision detection and gravity. The collision detection strategies were adequate but I wish that there was more depth at least referenced in the text. This isn't a simple problem and I did like how Geary referenced back to chapter two's profile and showed how collision detection performance as you implement and refine and optimize your algorithm. The nice thing about this book is that it often tackles problems with a general solution in the code (runner/sprite collision) and then provides the edge case solutions.

In the fourteenth chapter, the author tackles something that has long been a plague in HTML5 games: sound and music. The author doesn't sugarcoat this citing the long history of problems the vendors have had trying to support this in browsers. There's a great explanation of how to create and handle "sound sprites" (similar to sprite sheets) so that there is only one download for background music and one download for audio sprites.

Next Geary covers the problem of multiple viewport sizes with a focus on mobile devices. Of course this is one of the biggest issues with mobile gaming today. The chapter is lengthy and deals with the many intricacies of scaling, sizing and touch events. This chapter is long but the highly detailed support of multiple platforms and resolutions is a justified discussion point.

In sixteen, the reader gets a treatment of utilizing sprites and their artists to simulate sparks and smoking holes. The book calls this chapter "particle systems" but I don't think that's a very good title as the code isn't actually dealing with things at the particle level. Instead this chapter focuses on using sprites to simulate those behaviors via animation. This is completely necessary on a computation inexpensive platform but it is misleading to call these particle systems.

Now that the game looks and functions appropriately, the book covers UI elements like player scores and player lives. The auditing of these metrics are covered in the code as well as warnings when the game begins to run to slowly. It also covers the 'edge' condition of winning in the game and the routine that is followed when the user wins the game.

The next chapter introduces the concept of a developer backdoor so that the reader can manually speed up or slow down the game while playing it or even test special cases of the runner sprite interacting with other elements. It's a useful trick for debugging and playing around but does devote a lot of time to the specialized UI like the speed slider and other things that won't (or rather shouldn't) be seen by a common player.

Chapter nineteen really felt out of place and very inadequate on important details. It's a blind rush through using node.js and socket.io to implement server side high scores. The way it's implemented would make it trivial for someone to submit a high score of MAX_INT or whatever to the server. The metrics reporting is done in a manner that (in my opinion) breaks from long established logging structure one would be familiar with. While it covers important things to record from your users in order to tweak your game, the inadequacy of discussions about shortcomings makes it feel out of place in this text. It's a topic of great depth and I have no problem with an author touching on something briefly in one chapter — this chapter does lack the warnings and caveats found in other chapters though.

Contrary to the previous chapter, the final chapter is a fast application of the entire book's principles applied to a new game (Bodega's Revenge). Geary gives a final run through showing how the lengthy prior discussions quickly translate to a new set of sprite sheets and game rules. If this book is ever expanded, I think it would be great to include additional chapters like this although I would pick a more distinct and popular two dimensional game format like a tower defense game or a bejeweled knockoff.

Overall, Core HTML5 2D Game Programming is a great book for a JavaScript developer looking to dabble in game development. You can purchase Core HTML5 2D Game Programming 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. If you'd like to see what books we have available from our review library please let us know.

A while ago you had a chance to ask former Navy officer, professor, and famed ocean explorer Robert Ballard about shipwrecks, his work with the Ocean Exploration Trust, his learning programs, and what he's found on his expeditions. Below you'll find his answers to your questions. Autonomous robotic vehicles
by kalpol

I've always imagined fleets of tiny, relatively inexpensive autonomous vehicles exploring the oceans, sending their data back to be aggregated and mapped. Are there any projects of this sort happening?

Dr. Ballard: Yes there are. Go here to learn more.



Most interesting problem
by overThruster

First, thank you for taking time to answer our questions and for the amazing work you have done both as an explorer and an author! My favorite book of yours to date is The Discovery of the Bismarck.

I have two questions:
What is the most interesting underwater engineering problem you've had to solve in your career?

Dr. Ballard: When we lost the HUGO/JASON system on its first lowering in the Mediterranean in 1989 and had to recover them from 3,000 feet of water and be back in the water for our live JASON Project shows to 250,000 students waiting for the broadcasts in less than a week.

What are the unsolved underwater engineering problems that you think are most important?

Dr. Ballard: Solving engineering problems are much easier than convincing “the community” to accept a new way (technology) of doing something.



SOSUS
by dciman

Loved the show you hosted a number of years about about the development and implementation of the SOSUS system. Can you speculate or comment on the types of next generation technologies that could potentially fill in some of the gaps we now have with the reduction in traditional SOSUS effectiveness against quiet(er) ships from other nations? Presumably we still have to keep track of other countries missile and attack subs, is that much harder now than in the past?

Dr. Ballard: Ocean bottom observations are spreading across the ocean floor and will eventually be commonplace making it difficult for submarines and unmanned vehicle to sneak up on us.



Pollution
by Anonymous Coward

Dr. Ballard --thank you for your exploration work, and for making science and oceanography exciting to all of us!

A question: during your exploration of the deep sea, how prevalent or visible are the effects of human activity, i.e pollution, noise from ships, increased acidity due to more CO2 on the atmosphere, and the like? Do we even know enough to see if we are affecting as a species these ecosystems as critically as those on the surface of the planet?

Thank you and best for you and your crew in future expeditions!

Dr. Ballard: It is not so much what we can see (plastic, coke cans, etc.) which is not that much in the deep remote areas we explore, it is what we cannot see like acidification of the ocean water, its increased temperature, and the presences of other chemicals we continue to dump into the sea that concerns me.



Iron Bottom Sound; Kirishima
by Shakrai

Dr. Ballard: You're probably better known for the discoveries of Titanic and Bismarck, but I've always been more fascinated by your expeditions in the Pacific, specifically Iron Bottom Sound. Would a follow up expedition with more modern technology be a worthwhile endeavor? I would most interested in seeing another exploration of Kirishima, since the circumstances of her battle damage and loss have recently come into dispute.

Dr. Ballard: We plan to return to Iron Bottom Sound in the 2018 timeframe so stay tuned.



Electronic still camera
by fnj

Are any of the Marine Imaging Systems deep submergence electronic still cameras (circa mid 1980s) still in operation? With or without the original Heurikon based topsides?

Please accept my appreciation for your enabling an important part of my career. My work with MIS and Marquest Group was a happy time of fond memory.

Dr. Ballard: To my knowledge those Marquest camera systems have been replaced but once you are “signed out” of a world you lose contact with what follows.



Danger
by Major Blud

I know that quite a bit of the exploration that you've done has been with ROV's, but you've also been down in the deep yourself in the Alvin submersible. Was there ever a time during one of your expeditions where you feared for your life?

Thanks for taking the time to answer our questions, and for helping to inspire my interest in science. I was a young when the Titanic and Bismarck were found, and I can still remember the excitement and wonder I felt during those two events.

Dr. Ballard: There were several times when I was diving in submersibles and bathyscaphe when I feared for my life of those of others when they were diving and I was topside – when the fire broke out in the ARCHIMEDE bathyscaphe during Project Famous in 1973, when ALVIN got stuck in a fissure in 1974, when we crashed into the side of a fault scarp in the Mid-Cayman Rise in 20,000 feet of water in the bathyscaphe TRIESTE II I 1977, and when the DELTA submersible became entangled in fishing nets while diving on the LUSITANIA.



Space
by GoCrazy

You've probably heard about NASA's potential exploration of planetary bodies with water (yes! real water!) such as Europa, which is known to have solid ice water on the surface, but possible liquid water beneath. Would you consider moving your expertise on oceanography to more space based programs, with the possibility that your discoveries on Earth could be the same on these other planets?

Dr. Ballard: I have been asked to help in the design of the Europa vehicle system and plan to visit JPL in the next month of so.

theodp writes Boys' over-representation in K-12 computer classes has perplexed educators for 30+ years. Now, following on the heels of Code.org's and Google's attempts to change the game with boys-don't-count gender-based CS teacher funding schemes, Washington State lawmakers have introduced House Bill 1813, legislation that requires schools seeking K-12 computer education funding to commit to preventing boys from ruling the computer class roost. Computer science and education grant recipients, HB 1813 explains, "must demonstrate engaged and committed leadership in support of introducing historically underrepresented students [including girls, low-income students, and minority students]" and "demonstrate a plan to engage historically underrepresented students with computer science." Calling it "a bold new bill that we hope more states will follow," corporate and tech billionaire-backed Code.org tweeted its support for the bill.

theodp writes Boys' over-representation in K-12 computer classes has perplexed educators for 30+ years. Now, following on the heels of Code.org's and Google's attempts to change the game with boys-don't-count gender-based CS teacher funding schemes, Washington State lawmakers have introduced House Bill 1813, legislation that requires schools seeking K-12 computer education funding to commit to preventing boys from ruling the computer class roost. Computer science and education grant recipients, HB 1813 explains, "must demonstrate engaged and committed leadership in support of introducing historically underrepresented students [including girls, low-income students, and minority students]" and "demonstrate a plan to engage historically underrepresented students with computer science." Calling it "a bold new bill that we hope more states will follow," corporate and tech billionaire-backed Code.org tweeted its support for the bill.

ConstantineM writes: OpenSSH developer Damien Miller has posted about a new feature he implemented and committed for the next upcoming 6.8 release of OpenSSH — hostkeys@openssh.com — an OpenSSH extension to the SSH protocol for sshd to automatically send all of its public keys to the client, and for the client to automatically replace all keys of such server within ~/.ssh/known_hosts with the fresh copies as supplied (provided the server is trusted in the first place, of course). The protocol extension is simple enough, and is aimed to make it easier to switch over from DSA to the OpenSSL-free Ed25519 public keys. It is also designed in such a way as to support the concept of spare host keys being stored offline, which could then seamlessly replace main active keys should they ever become compromised.

New submitter cbiltcliffe writes: About a month ago, we discussed news that the Pirate Bay domain name was back online. This story mentioned a timer, which supposedly showed the time since the police raid. I didn't notice at the time, but a more recent check showed this counter was counting down, not up, with a time set to reach zero at the end of January. Sometime around a week ago, the waving pirate flag video changed to a graphic of an orange phoenix, and a disabled search box showed up. I've been watching the site since, and now, about 12 hours before the timer was to reach zero, the site is back up, complete with searches.

MojoKid writes: In all of its iterations, NVIDIA's Maxwell architecture has proven to be a good performing, power-efficient GPU thus far. At the high-end of the product stack is where some of the most interesting products reside, however. When NVIDIA launches a new high-end GPU, cards based on the company's reference design trickle out first, and then board partners follow up with custom solutions packing unique cooling hardware, higher clocks, and sometimes additional features. With the GeForce GTX 970 and GTX 980, NVIDIA's board partners were ready with custom solutions very quickly. These three custom GeForce cards, from enthusiast favorites EVGA, MSI, and Zotac represent optimization at the high-end of Maxwell. Two of the cards are GTX 980s: the MSI GTX 980 Gaming 4G and the Zotac GeForce GTX 980 AMP! Omgea, the third is a GTX 970 from EVGA, their GeForce GTX 970 FTW with ACX 2.0. Besides their crazy long names, all of these cards are custom solutions, that ship overclocked from the manufacturer. In testing, NVIDIA's GeForce GTX 980 was the fastest, single-GPU available. The custom, factory overclocked MSI and Zotac cards cemented that fact. Overall, thanks to a higher default GPU-clock, the MSI GTX 980 Gaming 4G was the best performing card. EVGA's GeForce GTX 970 FTW was also relatively strong, despite its alleged memory bug. Although, as expected, it couldn't quite catch the higher-end GeForce GTX 980s, but occasionally outpaced the AMD's top-end Radeon R9 290X.

MojoKid writes: In all of its iterations, NVIDIA's Maxwell architecture has proven to be a good performing, power-efficient GPU thus far. At the high-end of the product stack is where some of the most interesting products reside, however. When NVIDIA launches a new high-end GPU, cards based on the company's reference design trickle out first, and then board partners follow up with custom solutions packing unique cooling hardware, higher clocks, and sometimes additional features. With the GeForce GTX 970 and GTX 980, NVIDIA's board partners were ready with custom solutions very quickly. These three custom GeForce cards, from enthusiast favorites EVGA, MSI, and Zotac represent optimization at the high-end of Maxwell. Two of the cards are GTX 980s: the MSI GTX 980 Gaming 4G and the Zotac GeForce GTX 980 AMP! Omgea, the third is a GTX 970 from EVGA, their GeForce GTX 970 FTW with ACX 2.0. Besides their crazy long names, all of these cards are custom solutions, that ship overclocked from the manufacturer. In testing, NVIDIA's GeForce GTX 980 was the fastest, single-GPU available. The custom, factory overclocked MSI and Zotac cards cemented that fact. Overall, thanks to a higher default GPU-clock, the MSI GTX 980 Gaming 4G was the best performing card. EVGA's GeForce GTX 970 FTW was also relatively strong, despite its alleged memory bug. Although, as expected, it couldn't quite catch the higher-end GeForce GTX 980s, but occasionally outpaced the AMD's top-end Radeon R9 290X.

hypnosec writes: The European Space Agency has made a joint analysis of data gathered by the ground-based BICEP2 and Keck Array experiments and its own Planck satellite to try to verify previous reports of BICEP2's primordial gravitational wave detection. However, the ESA was unable to find evidence of primordial gravitational waves, and they think the earlier report was simply based on an outdated model that didn't take interstellar dust into account.

"The Milky Way is pervaded by a mixture of gas and dust shining at similar frequencies to those of the CMB, and this foreground emission affects the observation of the most ancient cosmic light. Very careful analysis is needed to separate the foreground emission from the cosmic background. Critically, interstellar dust also emits polarized light, thus affecting the CMB polarization as well. ... The BICEP2 team had chosen a field where they believed dust emission would be low, and thus interpreted the signal as likely to be cosmological. However, as soon as Planck’s maps of the polarized emission from Galactic dust were released (PDF), it was clear that this foreground contribution could be much higher than previously expected."

theodp writes: Yes, folks, there are blind programmers. There's Ed Summers, for one, who lost his vision at age 30 and now ghostblogs for Willie the Seeing Eye Dog. And if you've ever wondered how the blind can code, Florian Beijers, who has been blind since birth, explains that all he needs is a normal Dell Inspiron 15r SE notebook and his trusty open source NVDA screen reader software, and he's good-to-go. "This is really all the adaptation a blind computer user needs," Beijers adds, but he does ask one small favor: "If you're writing the next big application, with a stunning UI and a great workflow, I humbly ask you to consider accessibility as part of the equation. In this day and age, there's really no reason not to use the UI toolkits available."

New submitter ferro lad sends a story about Verizon's so-called supercookie, a unique identifier they add to web traffic going across their network to help advertisers target their ads better. A new article at Slate demonstrates how Verizon could fix the identifier so that ad companies would have a harder time misusing it — something they've already been shown to do. "...with just a tiny amount of effort, Verizon could maintain its current business while substantially preventing the misuse of its UID headers." Of course, for privacy-conscious users, the ability to get rid of them altogether would be preferable. Fortunately, Verizon now says users will soon have the ability to opt out of the identifiers. Previously, users could opt out of having their data shared with advertisers, but the unique identifier itself remained with their web traffic. It's not a complete solution — the tracking should be opt-in to begin with — but it's a step in the right direction.

New submitter ferro lad sends a story about Verizon's so-called supercookie, a unique identifier they add to web traffic going across their network to help advertisers target their ads better. A new article at Slate demonstrates how Verizon could fix the identifier so that ad companies would have a harder time misusing it — something they've already been shown to do. "...with just a tiny amount of effort, Verizon could maintain its current business while substantially preventing the misuse of its UID headers." Of course, for privacy-conscious users, the ability to get rid of them altogether would be preferable. Fortunately, Verizon now says users will soon have the ability to opt out of the identifiers. Previously, users could opt out of having their data shared with advertisers, but the unique identifier itself remained with their web traffic. It's not a complete solution — the tracking should be opt-in to begin with — but it's a step in the right direction.

You may have read a few weeks ago about the new materials that MakerBot has introduced for its 3-D printers; earlier this month, I got a chance to see some of them in person, and have them explained by MakerBot VP of Product Anthony Moschella in a cramped demo closet — please excuse the lighting — at the company's booth at CES. Moschella had some things to say about materials, timelines, and what MakerBot is doing to try to salvage its open-source cred, despite being a very willing part of a corporate conspiracy to sell boxes of Martha Stewart-branded extruder filament — as well as a few unremarkable things that the company's ever-vigilant PR overseer decreed Moschella couldn't answer on the record for reasons like agreements between MakerBot parent Stratasys and their suppliers. The good news for owners of recent MakerBot models: they'll be upgradeable to use the new and interesting materials with a part swap, rather than a whole-machine swap (it takes a "smart extruder" rather than the current, dumber one). And the pretty good news for fans of open source, besides that the current generation of MakerBots are all Linux-based computers themselves, is that MakerBot's open API provides a broad path for 3-D makers to interact with the printers. (The bad news is that there's no move afoot to return the machines' guts to open source hardware, like the early generations of MakerBots, but STL files at least don't care whether you ship them to an FSF-approved printer to be made manifest.)

You may have read a few weeks ago about the new materials that MakerBot has introduced for its 3-D printers; earlier this month, I got a chance to see some of them in person, and have them explained by MakerBot VP of Product Anthony Moschella in a cramped demo closet — please excuse the lighting — at the company's booth at CES. Moschella had some things to say about materials, timelines, and what MakerBot is doing to try to salvage its open-source cred, despite being a very willing part of a corporate conspiracy to sell boxes of Martha Stewart-branded extruder filament — as well as a few unremarkable things that the company's ever-vigilant PR overseer decreed Moschella couldn't answer on the record for reasons like agreements between MakerBot parent Stratasys and their suppliers. The good news for owners of recent MakerBot models: they'll be upgradeable to use the new and interesting materials with a part swap, rather than a whole-machine swap (it takes a "smart extruder" rather than the current, dumber one). And the pretty good news for fans of open source, besides that the current generation of MakerBots are all Linux-based computers themselves, is that MakerBot's open API provides a broad path for 3-D makers to interact with the printers. (The bad news is that there's no move afoot to return the machines' guts to open source hardware, like the early generations of MakerBots, but STL files at least don't care whether you ship them to an FSF-approved printer to be made manifest.)

Tyketto writes Following up on a previous story about its replacement, the US Air Force has selected the Boeing 747-8 to replace the aging Presidential fleet of two VC-25s, which are converted B747-200s. With the only other suitable aircraft being the Airbus A380, the USAF cited Boeing's 50-year history of building presidential aircraft as their reason to skip competition and opt directly for the aircraft, which due to dwindling sales and prospects, may be the last 747s to be produced.

New submitter rsanford, apropos of today's FCC announcement about what is officially consided "broadband" speed by that agency, asks In the early and middle 90's I recall spending countless hours on IRC 'Trout-slapping' people in #hottub and engaging in channel wars. The people from Europe were always complaining about how slow their internet was and there was no choice. This was odd to me, who at the time had 3 local ISPs to choose from, all offering the fastest modem connections at the time, while living in rural America 60 miles away from the nearest city with 1,000 or more people. Was that the reality back then? If so, what changed, and when?

MojoKid writes Dell's 2015 XPS 13 notebook made a splash out at CES this year with its near bezel-less 13-inch QHD+ (3200X1800) display and Intel's new 5th Gen Core series Broadwell-U processor. At 2.8 pounds, the 2015 XPS 13 isn't the absolute lightest 13-inch ultrabook book out there but it's lighter than a 13-inch MacBook Air and only a few ounces heavier than Lenovo's Core M-powered Yoga 3 Pro. The machine's Z dimensions are thin, at .33" up front to .6" at its back edge. However, its 11.98" width almost defies the laws of physics, squeezing a 13.3" (diagonal) display into an 11.98-inch frame making it what is essentially the smallest 13-inch ultrabook to hit the market yet. Performance-wise, this review shows its benchmarks numbers are strong and Intel's Broadwell-U seems to be an appreciable upgrade versus the previous generation architecture, along with lower power consumption.

An anonymous reader writes A recent incident at the White House showed that small aerial vehicles (drones) present a specific security problem. Rahul Sasi, a security engineer at Citrix R&D, created MalDrone, the first backdoor malware for the AR drone ARM Linux system to target Parrot AR Drones, but says it can be modified to target others as well. The malware can be silently installed on a drone, and be used to control the drone remotely and to conduct remote surveillance. Meanwhile, the Chinese company that created the drone that crashed on the White House grounds has announced a software update for its "Phantom" series that will prohibit flight within 25 kilometers of the capital.

benrothke writes Many organizations are overwhelmed by the onslaught of security data from disparate systems, platforms and applications. They have numerous point solutions (anti-virus, firewalls, IDS/IPS, ERP, access control, IdM, single sign-on, etc.) that can create millions of daily log messages. In addition to directed attacks becoming more frequent and sophisticated, there are regulatory compliance issues that place increasing burden on security, systems and network administrators. This creates a large amount of information and log data without a formal mechanism to deal with it. This has led to many organizations creating a security operations center (SOC). A SOC in its most basic form is the centralized team that deals with information security incidents and related issues. In Designing and Building a Security Operations Center, author David Nathans provides the basics on how that can be done. Keep reading for the rest of Ben's review Designing and Building a Security Operations Center author David Nathans pages 276 publisher Syngress rating 8/10 reviewer Ben Rothke ISBN 978-0128008997 summary Good introduction to those looking to build their own security operations center An effective SOC provides the benefit of speed of response time to a security incident. Be it a DDoS attack or malware which can spread throughout a corporate network in minutes, and potentially knock out the network, every second counts in identifying these attacks and negating them before they can cause additional damage. Having a responsive SOC can make all the difference in how a firms deals with these security issues.

The book notes that the SOC is akin to an enterprise nervous system that can gather and normalize vast amounts of log and related data. This can provide continuous prevention, protection and detection by providing response capabilities against threats, remotely exploitable vulnerabilities and real-time incidents on the monitored network.

The 11 chapters provide a start for anyone considering building out their own SOC. Topics include required infrastructure, organizational structure, staffing and daily operations, to training, metrics, outsourcing and more.

When building a SOC, the choices are for the most part doing it yourself (DIY) or using an outsourced managed security service provider (MSSP). The book focuses primarily on the DIY approach, while chapter 10 briefly details the issues and benefits of using a MSSP. The book provides the pros and cons of each approach. Some firms have a hybrid approach where they perform some SOC activities and outsource others. But the book doesn't details that approach.

The book provides a large amount of details on the many tasks needed to create an internal SOC. The truth is that many firms simply don't have the staff and budget needed to support an internal SOC. They also don't have the budget for an MSSP. With that, Mike Rothman of Securosis noted that these firms are "trapped on the hamster wheel of pain, reacting without sufficient visibility, but without time to invest in gaining that much-needed visibility into threats without diving deep into raw log files".

One important topic the book does not cover is around SIM/SIEM/SEM software. SIEM software can provide a firm with real-time analysis of security alerts generated by network and security hardware, software and other applications.

Many benefits come from an effective SIEM tool being the backbone of the SOC. A SIEM tool consolidates all data and analyzes it intelligently and provides visualization into the environment. But selecting the appropriate SIEM and correctly deploying it is not a trivial endeavor.

Those looking for a good reference on SIEM should read: Security Information and Event Management (SIEM) Implementation, which I reviewed on Slashdot. That book does provide an excellent overview of the topic and will be of value to those reading looking for answer around SIEM. Those looking for a solid introduction to the world of SIEM should definitely get a copy.

The book notes that the most important part of a SOC, and often the most overlooked, is that of the SOC analyst. And with that, the book writes how it's important to be cognizant of the fact of SOC analyst burnout. SOC analysts can burnout and it's important for an organization to have a plan to address this, including aspects of training, management opportunities and job rotation.

Building an in-house SOC takes significant planning an attention to detail and the book details a lot of the particulars that are required for an effective SOC design.

The implementation of a SOC will cost a significant amount of money and management will often want to have metrics to let them know what the SOC is doing. The book spends a brief amount of time on SOC metrics; which is a topic that warrants a book in its own right. There are many metrics that can be created to measure SOC efficacy. Effective SOC metrics will measure how quickly incidents are handled by the SOC, and how incident are identified, addressed and handled.

The downside to metrics is that they must be used judiciously. It's important not to measure base performance of a SOC analyst simply on the number of events analyzed or recommendations written. Metrics used in that manner are akin to help desk where analysts are only concerned about getting calls finished, in order to meet their calls completed metrics.

As important as a SOC is, this is surprisingly the first book written on the topic. At under 250 pages, the book provides an introduction to the topic, but is not a comprehensive work on the topic. There are areas in SOC management that the book doesn't cover, such as SOC documentation, creating and using SOC operation run books, and more.

But even with those missing areas, Designing and Building a Security Operations Center is a good reference to start with. A SOC is a security component most organizations are in dire need of, and the book is a good way to get them started on that effort.

Reviewed by Ben Rothke.

You can purchase Designing and Building a Security Operations Center 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. If you'd like to see what books we have available from our review library please let us know.

benrothke writes Many organizations are overwhelmed by the onslaught of security data from disparate systems, platforms and applications. They have numerous point solutions (anti-virus, firewalls, IDS/IPS, ERP, access control, IdM, single sign-on, etc.) that can create millions of daily log messages. In addition to directed attacks becoming more frequent and sophisticated, there are regulatory compliance issues that place increasing burden on security, systems and network administrators. This creates a large amount of information and log data without a formal mechanism to deal with it. This has led to many organizations creating a security operations center (SOC). A SOC in its most basic form is the centralized team that deals with information security incidents and related issues. In Designing and Building a Security Operations Center, author David Nathans provides the basics on how that can be done. Keep reading for the rest of Ben's review Designing and Building a Security Operations Center author David Nathans pages 276 publisher Syngress rating 8/10 reviewer Ben Rothke ISBN 978-0128008997 summary Good introduction to those looking to build their own security operations center An effective SOC provides the benefit of speed of response time to a security incident. Be it a DDoS attack or malware which can spread throughout a corporate network in minutes, and potentially knock out the network, every second counts in identifying these attacks and negating them before they can cause additional damage. Having a responsive SOC can make all the difference in how a firms deals with these security issues.

The book notes that the SOC is akin to an enterprise nervous system that can gather and normalize vast amounts of log and related data. This can provide continuous prevention, protection and detection by providing response capabilities against threats, remotely exploitable vulnerabilities and real-time incidents on the monitored network.

The 11 chapters provide a start for anyone considering building out their own SOC. Topics include required infrastructure, organizational structure, staffing and daily operations, to training, metrics, outsourcing and more.

When building a SOC, the choices are for the most part doing it yourself (DIY) or using an outsourced managed security service provider (MSSP). The book focuses primarily on the DIY approach, while chapter 10 briefly details the issues and benefits of using a MSSP. The book provides the pros and cons of each approach. Some firms have a hybrid approach where they perform some SOC activities and outsource others. But the book doesn't details that approach.

The book provides a large amount of details on the many tasks needed to create an internal SOC. The truth is that many firms simply don't have the staff and budget needed to support an internal SOC. They also don't have the budget for an MSSP. With that, Mike Rothman of Securosis noted that these firms are "trapped on the hamster wheel of pain, reacting without sufficient visibility, but without time to invest in gaining that much-needed visibility into threats without diving deep into raw log files".

One important topic the book does not cover is around SIM/SIEM/SEM software. SIEM software can provide a firm with real-time analysis of security alerts generated by network and security hardware, software and other applications.

Many benefits come from an effective SIEM tool being the backbone of the SOC. A SIEM tool consolidates all data and analyzes it intelligently and provides visualization into the environment. But selecting the appropriate SIEM and correctly deploying it is not a trivial endeavor.

Those looking for a good reference on SIEM should read: Security Information and Event Management (SIEM) Implementation, which I reviewed on Slashdot. That book does provide an excellent overview of the topic and will be of value to those reading looking for answer around SIEM. Those looking for a solid introduction to the world of SIEM should definitely get a copy.

The book notes that the most important part of a SOC, and often the most overlooked, is that of the SOC analyst. And with that, the book writes how it's important to be cognizant of the fact of SOC analyst burnout. SOC analysts can burnout and it's important for an organization to have a plan to address this, including aspects of training, management opportunities and job rotation.

Building an in-house SOC takes significant planning an attention to detail and the book details a lot of the particulars that are required for an effective SOC design.

The implementation of a SOC will cost a significant amount of money and management will often want to have metrics to let them know what the SOC is doing. The book spends a brief amount of time on SOC metrics; which is a topic that warrants a book in its own right. There are many metrics that can be created to measure SOC efficacy. Effective SOC metrics will measure how quickly incidents are handled by the SOC, and how incident are identified, addressed and handled.

The downside to metrics is that they must be used judiciously. It's important not to measure base performance of a SOC analyst simply on the number of events analyzed or recommendations written. Metrics used in that manner are akin to help desk where analysts are only concerned about getting calls finished, in order to meet their calls completed metrics.

As important as a SOC is, this is surprisingly the first book written on the topic. At under 250 pages, the book provides an introduction to the topic, but is not a comprehensive work on the topic. There are areas in SOC management that the book doesn't cover, such as SOC documentation, creating and using SOC operation run books, and more.

But even with those missing areas, Designing and Building a Security Operations Center is a good reference to start with. A SOC is a security component most organizations are in dire need of, and the book is a good way to get them started on that effort.

Reviewed by Ben Rothke.

You can purchase Designing and Building a Security Operations Center 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. If you'd like to see what books we have available from our review library please let us know.

alphadogg writes: The FCC on Tuesday warned that it will no longer tolerate hotels, convention centers or others intentionally interfering with personal Wi-Fi hotspots. This issue grabbed headlines last fall when Marriott International was fined $600,000 for blocking customer Wi-Fi hotspots, presumably to encourage the guests to pay for pricey Internet access from the hotel.

bearhuntz writes: Riot Games has been using League of Legends as a psychology lab to run scientific experiments and reduce toxic player behavior for a while now. This article explains some of the experiments they're doing, and what the results have been. "For example, one product is a restricted chat mode that limits the number of messages abusive players can type per match. It’s a temporary punishment that has led to a noticeable improvement in player behavior afterward —on average, individuals who went through a period of restricted chat saw 20 percent fewer abuse reports filed by other players. The restricted chat approach also proved 4 percent more effective at improving player behavior than the usual punishment method of temporarily banning toxic players. Even the smallest improvements in player behavior can make a huge difference in an online game that attracts 67 million players every month."

MojoKid writes: In Microsoft's latest Windows 10 preview build released last week, Cortana made an entrance, but the much-anticipated Spartan browser did not. However, little did we realize that some of Spartan made the cut, in the form of an experimental rendering engine hidden under IE's hood. Microsoft has separated its Trident rendering engine into two separate versions: one is for Spartan, called EdgeHTML, while the other remains under its legacy naming with Internet Explorer. The reason Microsoft doesn't simply forego the older version is due to compatibility concerns. If you're running the Windows 10 9926 build, chances are good that you're automatically taking advantage of the new EdgeHTML engine in IE. To check, you can type 'about:flags' into the address bar. "Automatic" means that the non-Spartan Trident engine will be called-upon only if needed. In all other cases, you'll be taking advantage of the future Spartan web rendering engine. Performance-wise, the results with IE are like night and day in certain spots. Some of the improvements are significant. IE's Sunspider result already outperforms the competition, but it has been further improved. And with Kraken, the latency with the Spartan-powered Trident engine dropped 40%. Similar results are seen with a boost in the Octane web browser test as well.

First we look at Skiva Technology and their Octofire 8-port USB charger that pulled in nearly five times the requested amount from a Kickstarter campaign. (The 'pulled in X times the requested Kickstarter amount' is becoming a common product boast, isn't it?) Then, for MacBook owners who are tired of having their chargers or charger cords break, we take a brief look at the Juiceboxx Charger Case. These two power-oriented products and WakaWaka, which we posted about on January 9, are just a tiny, random sample of the many items in this category that were on display at CES 2015. Timothy was the only Slashdot person working CES, so it's shocking that he managed to cover as many (hopefully interesting) products as he did, considering that even the biggest IT journo mills don't come close to total coverage of the overwhelming muddle CES has become in recent years. (Alternate Video Link)

First we look at Skiva Technology and their Octofire 8-port USB charger that pulled in nearly five times the requested amount from a Kickstarter campaign. (The 'pulled in X times the requested Kickstarter amount' is becoming a common product boast, isn't it?) Then, for MacBook owners who are tired of having their chargers or charger cords break, we take a brief look at the Juiceboxx Charger Case. These two power-oriented products and WakaWaka, which we posted about on January 9, are just a tiny, random sample of the many items in this category that were on display at CES 2015. Timothy was the only Slashdot person working CES, so it's shocking that he managed to cover as many (hopefully interesting) products as he did, considering that even the biggest IT journo mills don't come close to total coverage of the overwhelming muddle CES has become in recent years. (Alternate Video Link)