Its a good thing the Military has been using this technology since the 70's or Apple would be trying to ban the importation of any device using anything that even resembled their solution based on nothing more than the same of the corners.
It looks to me like they stole technology from the F35 helmet system.
The point of this exercise is to provide unique documents to people authorized to have them and then see (by looking for the uniqueness) which ones were leaked. No one is proposing to dream up dozens of scenarios of gloom doom death and destruction just to be able to say it was all just a joke.
Meh. Just be sure to grab someone elses copy and leak that. They;ll trace it back to the other person, not you.
Well then they would get the original leaker wouldn't they? That is the point.
There is nothing new here, other than the apparent plan to plug leaks in government, (or should I say inconvenient government leaks).
Copies of physical documents of sensitive information have often contained minor typos or subtle wording changes in critical and likely to be leaked passages. Churchill ordered this during WWII to see which of his subordinates was leaking.
Depends on the GPL version; the iOS App Store is perfectly GPL 2.0 compliant, as long as a distributor of software provides their source upon demand, they are fulfilling their terms under Section 3, paragraph b. Several iOS developers distribute GPL software, such as Doom, this way. VLC is distributed under GPL 2.0.
The issue is that the third party conversion of VLC in the Apple App Store imposed DRM on VLC. That was in violation of the GPL. One of the developers of VLC, Rémi Denis-Courmont objected.
He did not object when the very same binary was distributed free on Cydia, because there was no additional DRM imposed. He did the right thing. It had nothing to do with Paragraph 6.
I always imagined self-driving vehicles would "track" based on some sort of magnetic strips embedded in the roads. It now appears everyone working on these systems is attempting to make them work with radar, cameras, etc. so as not to add any special requirements for the road design.
I'm not so sure that's the optimal way to go about things, and your snowplow example is probably just one scenario that makes this point.
If you really want to trust peoples' lives to self-driving cars and trucks on the roads, I think it'd be wise to modify the roadways with some sort of standardized system of markers that these vehicles could easily follow along with.
I suspect it will come down to some passive RFID embedded in the next repaving job for lane guidance, and all the other onboard stuff for collision avoidance.
You could even use glue down RFID tags for temporary detours, and they could indicate speeds, upcoming turns, stops, etc. A downward facing RFID transponder is a hell of a lot cheaper than LIDAR and all sorts of optical equipment that gets confused the first time a bug goes splat.
You could tie this into existing GPS turn by turn units and just verbally warn the driver when then the route takes them to roads that don't yet have this embedded.
People are still going to want to steer, change lanes. When we are too lazy to do that we will take the train.
Although I recall reading somewhere that the adaptive cruise control won't be sold in the US due to issues with insuring a car with systems like that.
First you say you have it, then you say it won't be sold due to insurance?
I assure you its already sold in the US, and has been for many years, even if Ford is just catching up now.
Maybe talking about lane assist? No, that's already sold on some high end euro imports as well as high end domestic models.
ACC, Blind Spot monitoring, collision warning, backup cameras, park assist features actually LOWER your insurance. These packages almost pay for themselves in lower insurance rates over the first 5 years. After we replaced an Accord with a Chrysler 300 loaded with all the safety tech, the insurance change was almost nothing, even when the new car was twice the sticker price.
I don't think anyone here is a luddite. We just don't glibly assume into existence all of the infrastructure improvements you mention as if they were easy.
With over 4,067,000 miles of road in the US, how is any of this stuff supposed to be brought up to a standard that you can trust a machine to navigate? And who pays that bill?
Asserting on slashdot that road markings need to be fixed ASAP is easy. Paying for it year after year is hard. After all we have just signed up our kids for a 14 trillion dollar debt load. There won't be money to pay for any extensive infrastructure upgrades. We can't afford to keep our potholes filled as it is, and nobody is going to pay for LIDAR in every car, and even if we did, real-time guesswork as to where the road really goes
What ever system is built is going to be a collection of individual sub-systems, adaptive cruise control, anti-collision radars, turn by turn GPS guidance. All separately proven, then much later integrated. But none of this comes without infrastructure changes, and making the cars emulate people is just silly and overly complex.
To me its a toss up whether you improve the cars or improve the roads. And chances are it will take a combination. You can never keep your maps up to date with every little detour for road repair, but two guys on a truck can lay glue-down RFID tags to guide vehicles thru ever-changing construction zones almost as quickly as they can lay down the traffic cones and move the jersey barriers. All road can have location and information devices embedded in each lane on the next repaving. And you can add these to every back road in the country over time. Most roads get paved every 30 to 40 years even in the most benign of climates.
Any fool who syncs their phone with Facebook deserves all the pain they are likely to get. The sad part is they inflict some of this pain on innocent bystanders who they happen to have in their phone books.
Its only the lane tracking part that I see as not currently practical. And you doesn't have to be in snow country to see this as a problem. Its probably un-workable with anything other than a guide wire embedded in the roadway, because as you point out simple wear and tear removes paint quickly.
Radio advertising of braking would probably also not work, just due to the nut jobs that would hack it, but it would also be very useful if they could solve that.
But I have Adaptive Cruise Control now, and I absolutely love it. My car uses a Bosch radar-based system, but there are multiple technologies already deployed. Its been around for about 10 years, and its still in its infancy, but from my experience it works very well. Works in fog too.
Small subtle differences in the speed holding capability of vehicles running cruise control no longer drive me nuts. The car follow the one ahead at a set distance (adjustable), and its pretty reliable. The only problem with it is you may find yourself following the slowest guy on the road. But as long as there is one guy somewhere paying attention to speed limits or safe driving speeds it works great. Throw in Blind Spot monitoring and things become far less stressful.
(This is where everybody is going to jump in and say how dumb this is due to people becoming less vigilant, and lecture me on being an idiot for relying on technology to do my driving for me. I drive the same way when I have this technology or not, as I switch vehicles frequently. I would never take off on a cross country trip without Cruise Control, and having Adaptive Cruise Control is even better. Try it before you knock it. We've heard all the nay-saying we need to hear).
I find it interesting that the industry is finally adopting some of the very same techniques that Jim Beaty was so soundly criticized for back in 1998 when he posted his Traffic Wave and Jam Busting experiments. Although now they are putting it into the vehicles.
Plays all files, in all formats, like the classic VLC. Audio and video media library, with full search. Support for network streams, including HLS. Supports Android from version 2.1 (platform-7). Supports ARMv6, ARMv7 and ARMv7+NEON. Subtitles support, embedded and external, including ASS and DVD subtitles. Multi audio or subtitles tracks selection. Multi-core decoding, for Cortex-A7 A9 and A15 chips. Experimental hardware decoding. Gestures, headphones control.
I sincerely doubt its due to an unavailability of US/Canadian test devices because late model GSM HSPA/UMTS devices from all the major manufacturers are pretty much the same world wide. I actually prefer buying unlocked international versions of these devices rather than carrier models.
I suspect this is really another patent fight over Codecs used or worked around by VLC, and the Google Market (play store) is making sure they don't end up on the wrong side of the MPAA, (not to mention trying to keep Google's YOUTube ox from being gored.
It does work, but won't necessarily play everything the desktop version plays just yet. The software decoding is slow and jerky for videos recorded on the android device it self, and the sound is out of sync, where as the embedded video player, or the desktop version works perfectly playing the same files.
It has a hard time of finding media on External_SD or attached USB storage on some tablets. Still its a beta. And its nice to see progress,
The targeted users of this service actually have a clue. Unlike web hosting service users. You get a bare bones Linux Virtual Machine with a remote console. The clueless will soon disappear.
You'd be well advised to go get your own dd-wrt rather than accepting one from the router manufacturer. Sort of defeats the purpose of dd-wrt and puts the fox on guard at the hen house door to use their version.
Sticking with a duopoly brand is no assurance of them being secure. This story should have made that patently obvious to you.
Moving everything off the router except the secure wifi functionality and putting it into my Linux machine running IPTables means that I can use any of these cheap routers that is able to function as an Access Point, and never expose them to the internet.
I've found the internal wireless NICs have a range equal to the radius of a swung cat.
This has forced me to get a cheap wifi access point, (or a router that can be told to just run as an access point) and use it for its radio only. I run my own DHCPD, DNS, Nat and IPTables, NTP, (etc) in a Linux box, and bridge my network onto a cheap ($25) ap that can do WPA2.
Since I run it in access point mode, it does nothing but handle wifi authentication and wifi access, it remains rather simple, and I really need only watch for bug fixes to WPA2.
I've been looking into various Open Router distributions for the radio side of things, but most are overkill for what I do.
there's no guarantee they'll make a profit (otherwise Google App Engine would be expanding),
Wait, they just introduced this last week, and you already know that its NOT expanding? Clairvoyance?
The pricing is not all that dissimilar than EC2. Its less, but not orders of magnitude less. This is not the sort of thing that requires a huge customer base up front. They have the luxury of throwing a few hundred virtual cores at this, or maybe a million. They have the hardware sitting around. Sunk costs already spent. If it turns out to be as self managing as most of Google's system, it will require a few administrative employees to collect the money, provision the virtual machines, and a few techs to deal with problems. But I suspect they have been running this in-house for years.
Google shuts down projects that have no clear path to making money, like Wave, Buzz and Others.
As far as I know none of these had any monitization mechanism other than pushing ads in your face.
Compute has a price schedule published right up front, and its about the twice the cost of the electricity to power a comparable computer, but with zero capital investment. Their data storage prices and bandwidth prices are also published, and are reasonable. You really couldn't afford to even put your legacy machines into production at these prices.
Clearly they expect this project to cover its own costs, and make use of excess capacity in their data centers.
Google can build a processor in house cheaper than Dell or any white-box company. With a gazillion of them on hand, they can provision them fast, swap them in when there is trouble, and they do it day in and day out. So chances are they are simply reselling the in house expertise they already have. None of this is going away any time soon, and they always need to maintain excess capacity for their own needs, so why not market that.
With a clear path to making money on this project baked in at the start, the only thing that would kill it is lack of customers. Hell I'm thinking of renting a couple cores just for playing around with.
So let's just go ahead and assume that the security people have already reviewed this and have green-lit it with the appropriate restrictions. They are, afterall, highly trained professionals. -_-
And yet they come here to slashdot to ask for advice?
I'm amazed that people really trust the OP is in a US Navy ship.
He said he is using a local ISP for bandwidth. So clearly he is not talking about ON the ship while at sea.
He is probably talking about dock side encrypted wifi (perhaps bridged to some place onboard).
He's probably stationed on a tug or service boat, oilers, replenishment ships, repair ship, because it would be pointless to set up something like this on a war ship which doesn't spend all that much time in port.
100 to 500 devices indicates (think cell phones and tablets and the occasional lap top) a crew of something much smaller than a Frigate. Even Coast Guard national security cutters tend to have a crew greater than 100.
100 devices (probably mostly phones and tablets) is not particularly difficult. In fact its no more difficult than providing a vpn for a single device.
Any one of a half dozen models of off the shelf routers (consumer grade) will do this out of the box for you and any number of ISP's offering VPN services are compatible with all of these and usually say so in their advertising.
Bandwidth is the only issue, but 100 or 200 wifi devices checking email instant messages once every 15 to 30 minutes presents no particular load. The OP is already aware of the need to limit concurrent VOIP or video sessions, but again, this is merely a bandwidth issue and nothing to do with the VPN.
A regional list for small states could work, but you have to be able to get to the organ location/meet the organ halfway/etc within a pretty short span of time. If you're a resident of Maine, and an organ became available in California, it's not going to do you much good.
Really?
Jobs bought his house several days prior to his operation, then flew to Tennessee from California. There appeared to be plenty of time for that.
Are you saying there isn't enough time to put an organ on a Leer jet for a direct flight?
Slashdot Mirror
Sigh. Another AC that can't read past the first paragraph.
Scroll All The Way down and read about the F35 helmet system and notice two projection heads.
Two. Count them. They project on the back side of the full face mask.
Its s full HUD in a Helmet, because the plane doesn't have a
UD.
Go fan boy somewhere else.
Its a good thing the Military has been using this technology since the 70's or Apple would be trying to ban the importation of any device using anything that even resembled their solution based on nothing more than the same of the corners.
It looks to me like they stole technology from the F35 helmet system.
No you've got it all wrong.
The point of this exercise is to provide unique documents to people authorized to have them and then see (by looking for the uniqueness) which ones were leaked. No one is proposing to dream up dozens of scenarios of gloom doom death and destruction just to be able to say it was all just a joke.
Meh. Just be sure to grab someone elses copy and leak that. They;ll trace it back to the other person, not you.
Well then they would get the original leaker wouldn't they? That is the point.
There is nothing new here, other than the apparent plan to plug leaks in government, (or should I say inconvenient government leaks).
Copies of physical documents of sensitive information have often contained minor typos or subtle wording changes in critical and likely to be leaked passages. Churchill ordered this during WWII to see which of his subordinates was leaking.
IBM applied for a patent on this process in the digital world back in 2009.
Depends on the GPL version; the iOS App Store is perfectly GPL 2.0 compliant, as long as a distributor of software provides their source upon demand, they are fulfilling their terms under Section 3, paragraph b. Several iOS developers distribute GPL software, such as Doom, this way. VLC is distributed under GPL 2.0.
The issue is that the third party conversion of VLC in the Apple App Store imposed DRM on VLC. That was in violation of the GPL.
One of the developers of VLC, Rémi Denis-Courmont objected.
He did not object when the very same binary was distributed free on Cydia, because there was no additional DRM imposed.
He did the right thing. It had nothing to do with Paragraph 6.
See: http://arstechnica.com/apple/2011/01/vlc-for-ios-vanishes-2-months-after-eruption-of-gpl-dispute/
I always imagined self-driving vehicles would "track" based on some sort of magnetic strips embedded in the roads. It now appears everyone working on these systems is attempting to make them work with radar, cameras, etc. so as not to add any special requirements for the road design.
I'm not so sure that's the optimal way to go about things, and your snowplow example is probably just one scenario that makes this point.
If you really want to trust peoples' lives to self-driving cars and trucks on the roads, I think it'd be wise to modify the roadways with some sort of standardized system of markers that these vehicles could easily follow along with.
I suspect it will come down to some passive RFID embedded in the next repaving job for lane guidance, and all the other onboard stuff for collision avoidance.
You could even use glue down RFID tags for temporary detours, and they could indicate speeds, upcoming turns, stops, etc. A downward facing RFID transponder is a hell of a lot cheaper than LIDAR and all sorts of optical equipment that gets confused the first time a bug goes splat.
You could tie this into existing GPS turn by turn units and just verbally warn the driver when then the route takes them to roads that don't yet have this embedded.
People are still going to want to steer, change lanes. When we are too lazy to do that we will take the train.
Although I recall reading somewhere that the adaptive cruise control won't be sold in the US due to issues with insuring a car with systems like that.
First you say you have it, then you say it won't be sold due to insurance?
I assure you its already sold in the US, and has been for many years, even if Ford is just catching up now.
Maybe talking about lane assist? No, that's already sold on some high end euro imports as well as high end domestic models.
ACC, Blind Spot monitoring, collision warning, backup cameras, park assist features actually LOWER your insurance. These packages almost pay for themselves in lower insurance rates over the first 5 years. After we replaced an Accord with a Chrysler 300 loaded with all the safety tech, the insurance change was almost nothing, even when the new car was twice the sticker price.
I don't think anyone here is a luddite. We just don't glibly assume into existence all of the infrastructure improvements you mention as if they were easy.
With over 4,067,000 miles of road in the US, how is any of this stuff supposed to be brought up to a standard that you can trust a machine to navigate? And who pays that bill?
Asserting on slashdot that road markings need to be fixed ASAP is easy. Paying for it year after year is hard. After all we have just signed up our kids for a 14 trillion dollar debt load. There won't be money to pay for any extensive infrastructure upgrades. We can't afford to keep our potholes filled as it is, and nobody is going to pay for LIDAR in every car, and even if we did, real-time guesswork as to where the road really goes
What ever system is built is going to be a collection of individual sub-systems, adaptive cruise control, anti-collision radars, turn by turn GPS guidance. All separately proven, then much later integrated. But none of this comes without infrastructure changes, and making the cars emulate people is just silly and overly complex.
To me its a toss up whether you improve the cars or improve the roads. And chances are it will take a combination. You can never keep your maps up to date with every little detour for road repair, but two guys on a truck can lay glue-down RFID tags to guide vehicles thru ever-changing construction zones almost as quickly as they can lay down the traffic cones and move the jersey barriers. All road can have location and information devices embedded in each lane on the next repaving. And you can add these to every back road in the country over time. Most roads get paved every 30 to 40 years even in the most benign of climates.
Any fool who syncs their phone with Facebook deserves all the pain they are likely to get.
The sad part is they inflict some of this pain on innocent bystanders who they happen to have in their phone books.
Its only the lane tracking part that I see as not currently practical. And you doesn't have to be in snow country to see this as a problem. Its probably un-workable with anything other than a guide wire embedded in the roadway, because as you point out simple wear and tear removes paint quickly.
Radio advertising of braking would probably also not work, just due to the nut jobs that would hack it, but it would also be very useful if they could solve that.
But I have Adaptive Cruise Control now, and I absolutely love it. My car uses a Bosch radar-based system, but there are multiple technologies already deployed. Its been around for about 10 years, and its still in its infancy, but from my experience it works very well. Works in fog too.
Small subtle differences in the speed holding capability of vehicles running cruise control no longer drive me nuts. The car follow the one ahead at a set distance (adjustable), and its pretty reliable. The only problem with it is you may find yourself following the slowest guy on the road. But as long as there is one guy somewhere paying attention to speed limits or safe driving speeds it works great. Throw in Blind Spot monitoring and things become far less stressful.
(This is where everybody is going to jump in and say how dumb this is due to people becoming less vigilant, and lecture me on being an idiot for relying on technology to do my driving for me. I drive the same way when I have this technology or not, as I switch vehicles frequently. I would never take off on a cross country trip without Cruise Control, and having Adaptive Cruise Control is even better. Try it before you knock it. We've heard all the nay-saying we need to hear).
I find it interesting that the industry is finally adopting some of the very same techniques that Jim Beaty was so soundly criticized for back in 1998 when he posted his Traffic Wave and Jam Busting experiments. Although now they are putting it into the vehicles.
)
Please release us from ACs.
Queue the Borg posts in 3, 2, 1,,,,
You can always download it from the Nighties
http://nightlies.videolan.org/build/android-v7-neon/VLC-debug.apk
or for Tegra 2:
http://nightlies.videolan.org/build/android-v7-tegra2/VLC-debug.apk
Plays all files, in all formats, like the classic VLC.
Audio and video media library, with full search.
Support for network streams, including HLS.
Supports Android from version 2.1 (platform-7).
Supports ARMv6, ARMv7 and ARMv7+NEON.
Subtitles support, embedded and external, including ASS and DVD subtitles.
Multi audio or subtitles tracks selection.
Multi-core decoding, for Cortex-A7 A9 and A15 chips.
Experimental hardware decoding.
Gestures, headphones control.
I sincerely doubt its due to an unavailability of US/Canadian test devices because late model GSM HSPA/UMTS devices from all the major manufacturers are pretty much the same world wide. I actually prefer buying unlocked international versions of these devices rather than carrier models.
I suspect this is really another patent fight over Codecs used or worked around by VLC, and the Google Market (play store) is making sure they don't end up on the wrong side of the MPAA, (not to mention trying to keep Google's YOUTube ox from being gored.
It does work, but won't necessarily play everything the desktop version plays just yet. The software decoding is slow and jerky for videos recorded on the android device it self, and the sound is out of sync, where as the embedded video player, or the desktop version works perfectly playing the same files.
It has a hard time of finding media on External_SD or attached USB storage on some tablets.
Still its a beta. And its nice to see progress,
The user target is not the same,
Exactly.
The targeted users of this service actually have a clue. Unlike web hosting service users.
You get a bare bones Linux Virtual Machine with a remote console. The clueless will
soon disappear.
You'd be well advised to go get your own dd-wrt rather than accepting one from the router manufacturer. Sort of defeats the purpose of dd-wrt and puts the fox on guard at the hen house door to use their version.
Sticking with a duopoly brand is no assurance of them being secure. This story should have made that patently obvious to you.
Moving everything off the router except the secure wifi functionality and putting it into my Linux machine running IPTables means that I can use any of these cheap routers that is able to function as an Access Point, and never expose them to the internet.
You still need a wireless radio.
I've found the internal wireless NICs have a range equal to the radius of a swung cat.
This has forced me to get a cheap wifi access point, (or a router that can be told to just run as an access point) and use it for
its radio only. I run my own DHCPD, DNS, Nat and IPTables, NTP, (etc) in a Linux box, and bridge my network onto a cheap ($25) ap that can do WPA2.
Since I run it in access point mode, it does nothing but handle wifi authentication and wifi access, it remains rather simple, and I really need only watch for bug fixes to WPA2.
I've been looking into various Open Router distributions for the radio side of things, but most are overkill for what I do.
Duopoly?
There are at least 30 brands listed at Best Buy and New Egg. Some of these may be re-badged, but there are far more than two or three alternatives.
there's no guarantee they'll make a profit (otherwise Google App Engine would be expanding),
Wait, they just introduced this last week, and you already know that its NOT expanding? Clairvoyance?
The pricing is not all that dissimilar than EC2. Its less, but not orders of magnitude less.
This is not the sort of thing that requires a huge customer base up front. They have the luxury of throwing a few hundred virtual cores at this, or maybe a million. They have the hardware sitting around. Sunk costs already spent. If it turns out to be as self managing as most of Google's system, it will require a few administrative employees to collect the money, provision the virtual machines, and a few techs to deal with problems. But I suspect they have been running this in-house for years.
Actually, its not a valid concern.
Google shuts down projects that have no clear path to making money, like Wave, Buzz and Others.
As far as I know none of these had any monitization mechanism other than pushing ads in your face.
Compute has a price schedule published right up front, and its about the twice the cost of the electricity to power a comparable computer, but with zero capital investment. Their data storage prices and bandwidth prices are also published, and are reasonable. You really couldn't afford to even put your legacy machines into production at these prices.
Clearly they expect this project to cover its own costs, and make use of excess capacity in their data centers.
Google can build a processor in house cheaper than Dell or any white-box company. With a gazillion of them on hand, they can provision them fast, swap them in when there is trouble, and they do it day in and day out. So chances are they are simply reselling the in house expertise they already have. None of this is going away any time soon, and they always need to maintain excess capacity for their own needs, so why not market that.
With a clear path to making money on this project baked in at the start, the only thing that would kill it is lack of customers. Hell I'm thinking of renting a couple cores just for playing around with.
So let's just go ahead and assume that the security people have already reviewed this and have green-lit it with the appropriate restrictions. They are, afterall, highly trained professionals. -_-
And yet they come here to slashdot to ask for advice?
Come on.
I'm amazed that people really trust the OP is in a US Navy ship.
He said he is using a local ISP for bandwidth. So clearly he is not talking about ON the ship while at sea.
He is probably talking about dock side encrypted wifi (perhaps bridged to some place onboard).
He's probably stationed on a tug or service boat, oilers, replenishment ships, repair ship, because it would be pointless to set up something like
this on a war ship which doesn't spend all that much time in port.
100 to 500 devices indicates (think cell phones and tablets and the occasional lap top) a crew of something much smaller than a Frigate.
Even Coast Guard national security cutters tend to have a crew greater than 100.
100 devices (probably mostly phones and tablets) is not particularly difficult. In fact its no more difficult than providing a vpn for a single device.
Any one of a half dozen models of off the shelf routers (consumer grade) will do this out of the box for you and any number of ISP's offering VPN services are compatible with all of these and usually say so in their advertising.
Bandwidth is the only issue, but 100 or 200 wifi devices checking email instant messages once every 15 to 30 minutes presents no particular load. The OP is already aware of the need to limit concurrent VOIP or video sessions, but again, this is merely a bandwidth issue and nothing to do with the VPN.
A regional list for small states could work, but you have to be able to get to the organ location/meet the organ halfway/etc within a pretty short span of time. If you're a resident of Maine, and an organ became available in California, it's not going to do you much good.
Really?
Jobs bought his house several days prior to his operation, then flew to Tennessee from California. There appeared to be plenty of time for that.
Are you saying there isn't enough time to put an organ on a Leer jet for a direct flight?
Single state list in this instance means you only need sign up in your state of residence to be on a nation wide list.