Street view is like someone snapping a photo of your house as they drive by every few months (or years).
The LIDAR information coming together now, is every few minutes (when we have lots of autonomous cars) having high accuracy 3d streetview being pushed. If you move a brick, google* will know. If you cut back a tree, google* will know. If you have a new car, google* will know. And google* will know within a few hours of you having changed your visible frontage.
Although it could be used harmlessly and for good use, the instantaneous nature of the data is what moves the needle from ultra-cool to kinda-scary.
But as a low-modded replier said, you can call me grandpa... (Still a bit young, but yeah).
GPS location information has revolutionized mapping. Google and Apple get high quality position data for cars traveling. Any non-mobile platform system have many barriers to entry (cars traveling around taking photos), verifying road information. Google gets to validate incredibly accurate maps under the guise of providing traffic, location services and so on the the mobile phone users.
LIDAR, particularly those paired with accurate color mapping information for those point clouds are going to be creating high accuracy, full color 3d meshes of the pretty much anywhere that cars go near. The small snippet of video just after https://www.youtube.com/watch?... (from the previous slashdot article about autonomous golf carts) shows some of the power of LIDAR. Just after the car flyby it shows the point map being updated by every pass through an area. Incrementally correcting the 3D view of the area. The example is just a few passes by the same car.
Imagine 1000s or 100,000s of automonous vehicles with LIDAR pushing data to a vendor for "navigation experience", but still building a 100% model of everything line of site to the LIDAR. And then imagine 100s of drones flying overhead, doing virtually the same thing.
Throw in some AR like Magic Leap being able to deal with that 3d Mesh. Pretty amazing things that our kids will grow up, pretty scary for everyone else..
There are some unexpected impacts of this law (I haven't read the full law).
A non-commercial area of drone use that is currently not possible, and will not be possible under this law (assuming there are no exemptions) is around search and rescue. Drones fitted with cameras help with visual scanning, with heat sensing equipment they can be sued for far more effective search and rescue.
This made me chuckle. I recently crossed the "this new college grad could be my first child threshold" and the "damn, I can't focus close enough on this ultra-tiny low contrast font on this power supply, I need someone with young eyes to read it". I'm still continually asking the young peers "has anyone seen this technology before", "or does anyone know of any alternative approach". Most of the time, it's cricket sounds in response.
I don't think age is an issue at all, you can have 30 year olds that are stagnant and rely on depth and stability. At any age, breadth, engagement and awareness really helps.
One challenge at any stage is really around outside distractions (married since young, 3 kids) really puts a dent in the volume or breadth or absolute depth that can be acquired, but it's not that hard to get on the right side of the bell curve.
Google has a strong interest in having a large number of Google derived WiFi out in the market.
Project Fi handsoff between different carriers and WiFi. With WiFi they don't have carrier charges.
I wouldn't be too surprised if Google somehow ties Project Fi into the "OnHub" effort. I'd also expect google making lots of loss-leader agreements with companies to offer lots of Google managed WiFi that will make the backhaul for Project Fi free.
10W is incredibly hot for any sort of passively cooled, enclosed device.
The machine would be quite warm (almost hot) to the touch unless they use some inventive cooling. The current Gen Apple TV is about 6W, and your typical smartphone is around 2-3 W.
There is a reason that NV has only really been able to get a foothold in tablets, android TV, cars and their own shield product. Quite simply put, they have historically been fast and hot. Great as a SOC within certain markets.
1) a way to repeat the benchmarks as described in the article see page 4 - 'phoronix-test-suite benchmark 1507285-BE-POWERLOW159'.
2) The compiler options are included
Armed with those two pieces of information, you can go and "prove" that the benchmark is, as you called it - bullshit. Although rarely, if ever that I am aware of, does anyone respond to an article with those two pieces of information and say - "here, if you run it in this mode, you will see a marked difference in performance".
As Bert64 says in the response to the grandparent, 99% of end users will be running the software - either pre-compiled by their distribution vendor in this way, or compiled by the benchmark author's defaults. If you really want to prove that the benchmark is crap, then by all means make meaningful suggestions to _any_ of the existing machine benchmarks.
Michael (Phoronix) and I had some interesting discussions with Sun (pre Oracle) about 64 vs 32. They argued that the benchmarks were misleading because they did not use the Sun Studio (IIRC) compiler for 64 bit. In the discussions, it became clear to even the Sun people that it was quite difficult for even the Sun people to configure and use the platform in the way they wanted Phoronix to. Out of the box, gcc compiling for 32 bit - was how they configured the systems. And guess what, the './configure;make;make install' triplet would compile the same way we did.
Full disclosure, I have a long history with Phoronix, and have been involved in work that they have done in the past.
JAVA (Dalvik) the ideal ISA, dex2oat converts the java bytecode to native ISA (intel or ARM).
Similar to pNaCL in Chrome, where at least historically the LLVM IR (effectively the ISA) would be pushed to the chrome devices which would then complete the conversion to native code.
The general belief (unfortunately google doesn't provide many non-tin foil links) is that it isn't the fracturing process itself that is inducing siesmicity it is the presurrized injection of the waste slurry that is loosening the stresses and creating the swarm earthquakes.
The risk in your suggestion is that you will reduce risk and stresses in some areas which may increase acute stress in other areas. One unexpected area that becomes the hinge point for a large stress could trigger a larger issues in an unexpected.
I agree fully. Having tried to get my mind around d3.js, there are *a lot* of leaps of understanding in coming to up to speed. Watching someone who provides a narrative how they get from a to d by verbalizing b and c will help immensely. The docs really go just from a to g.
As a viewer, it's about learning technique and thought processes. Identifying issues, attempting a particular thought process, only those that provide a strong narrative to the work they are doing will be likely "stars". Watching how good programmers (assumption) deal with their environment and the typical problems they face. Seeing how people top down or bottom up write code is very interesting (within limits).
As a broadcasting coder, it takes a fair amount of personal confidence to do it, particular in this field. Having to verbalize what you are thinking and how you are considering the problems in front of you is actually quite challenging. Those that do well in the broadcasting scene will most likely be strong professionally as well.
That said, I personally don't understand the fandom about broadcast games to the level that it has taken. I get the benefits, but I don't get the market.
Google has recently released Project Fi. A project/product (is project a codeword for beta now?) that will allow seamless transition between 2G/3G/LTE and *WiFi* for increased coverage and strength.
Project Fi is bandwidth charged, independent of data link being used - so while the underlying carriers (T-Mobile & Sprint) may charge wholesale for data, google will effectively get the bandwidth at "Google WiFi" for free - meaning that the data charges are a lot more profitable when going past a Starbucks, in NYC, etc. Although unproven, google might actually have meaningful alternate revenue sources from this model.
This is not fundamentally different than Xfinity's wifi sharing - except google is going for the Free WiFi in the Starbucks, NYC, etc. B2B is a lot more pragmatic, and a lot easier to enable.
Now if only Project Fi worked in a phone that was in the $2-300 range, I'd probably give it a go. But the Nexus 6 is too big and too expensive. Hopefully the invite won't expire.
The fact that they have a design patent aside, Blackberry has been iterating on the fret + rounded keys design since the blackberry bold. It's what makes a "modern" blackberry recognizable.
From TFA, it is a design patent - aka Trade Dress.
From http://www.theglobeandmail.com... , the actual complain seems with merit. The frets (metal lines), key shape (rounded corners) and space bar seem to be pulled entirely from the Blackberry Q10. It's as blatant as the typical Chinese typo-based (Sony vs Somy) ripoffs.
If you saw a phone with a the Typo keyboard, it would be reasonable to assume that its an extra tall Q10. That's what Blackberry has sued about.
EU privacy laws are fairly painful for US companies to comply with. To do business with EU individuals, Personal Identifiable Information needs to be handled according to a set of rules - http://ec.europa.eu/justice/da...
It is often simpler for Amazon deployed companies to set up in the Ireland AWS zone.
As others have mentioned, most foreign SIGINT/COMINT agencies can't gather intelligence domestically, so it lowers barriers. Ironically US companies that want to deal with EU customers may end up moving everything to Ireland. However this allows the NSA to gather intelligence indirectly on US citizens.
If your router enables IPv6, your devices have IPv6 access - no endpoint changes necessary. Current versions of most Operating Systems actually prefer IPv6 but fallback quickly. So it is likely to be turned on transparently.
There is no INTERNAL_IP6_ADDRESS, there is just an IP6_ADDRESS. The firewall blocks or permits dynamically (likely stateful connection management). The/64 subnet that is routed to your network is expected to be routed to the endpoint by your router if needed (modulo firewall rules).
The biggest issue for home networking is the lack of management of the router/firewall itself. You can't port forward (no config UI), you can't permit specific ports in most current home router implementations. However, configuration of ports and so on are not something that the vast majority of users know or care about.
2: Attackers can view your entire IP space. A simple nmap scan, then choosing what zero days to use... instant pwn-ership.
Hmm... Non-direct allocated IP on your subnet, 64 bit subnet, pwn-ership aint that trivial. Scanning a 64-bit address space (AT&T allocates a full/64 to me at home) is going to be pretty obvious at the firewall.
Welcome back to the internet of the early 1990's we all lived on the internet with real IPs, but were protected from firewalls... This whole concept of everyone on a Class C/B/A private subnet thing has only been around for a couple of decades.
Slashdot Mirror
I'll give an analogy.
Street view is like someone snapping a photo of your house as they drive by every few months (or years).
The LIDAR information coming together now, is every few minutes (when we have lots of autonomous cars) having high accuracy 3d streetview being pushed. If you move a brick, google* will know. If you cut back a tree, google* will know. If you have a new car, google* will know. And google* will know within a few hours of you having changed your visible frontage.
Although it could be used harmlessly and for good use, the instantaneous nature of the data is what moves the needle from ultra-cool to kinda-scary.
But as a low-modded replier said, you can call me grandpa... (Still a bit young, but yeah).
GPS location information has revolutionized mapping. Google and Apple get high quality position data for cars traveling. Any non-mobile platform system have many barriers to entry (cars traveling around taking photos), verifying road information. Google gets to validate incredibly accurate maps under the guise of providing traffic, location services and so on the the mobile phone users.
LIDAR, particularly those paired with accurate color mapping information for those point clouds are going to be creating high accuracy, full color 3d meshes of the pretty much anywhere that cars go near. The small snippet of video just after https://www.youtube.com/watch?... (from the previous slashdot article about autonomous golf carts) shows some of the power of LIDAR. Just after the car flyby it shows the point map being updated by every pass through an area. Incrementally correcting the 3D view of the area. The example is just a few passes by the same car.
Imagine 1000s or 100,000s of automonous vehicles with LIDAR pushing data to a vendor for "navigation experience", but still building a 100% model of everything line of site to the LIDAR. And then imagine 100s of drones flying overhead, doing virtually the same thing.
Throw in some AR like Magic Leap being able to deal with that 3d Mesh. Pretty amazing things that our kids will grow up, pretty scary for everyone else..
Is there a difference between a coder, a programmer, a computer scientist, software engineer and a computer engineer?
Is there a difference between a programmer, a computer scientist and a software engineer?
There are some unexpected impacts of this law (I haven't read the full law).
A non-commercial area of drone use that is currently not possible, and will not be possible under this law (assuming there are no exemptions) is around search and rescue. Drones fitted with cameras help with visual scanning, with heat sensing equipment they can be sued for far more effective search and rescue.
This made me chuckle. I recently crossed the "this new college grad could be my first child threshold" and the "damn, I can't focus close enough on this ultra-tiny low contrast font on this power supply, I need someone with young eyes to read it". I'm still continually asking the young peers "has anyone seen this technology before", "or does anyone know of any alternative approach". Most of the time, it's cricket sounds in response.
I don't think age is an issue at all, you can have 30 year olds that are stagnant and rely on depth and stability. At any age, breadth, engagement and awareness really helps.
One challenge at any stage is really around outside distractions (married since young, 3 kids) really puts a dent in the volume or breadth or absolute depth that can be acquired, but it's not that hard to get on the right side of the bell curve.
Assuming that these Home Robots are fusion powered, they of course will always be 20 years away...
Google has a strong interest in having a large number of Google derived WiFi out in the market.
Project Fi handsoff between different carriers and WiFi. With WiFi they don't have carrier charges.
I wouldn't be too surprised if Google somehow ties Project Fi into the "OnHub" effort. I'd also expect google making lots of loss-leader agreements with companies to offer lots of Google managed WiFi that will make the backhaul for Project Fi free.
10W is incredibly hot for any sort of passively cooled, enclosed device.
The machine would be quite warm (almost hot) to the touch unless they use some inventive cooling. The current Gen Apple TV is about 6W, and your typical smartphone is around 2-3 W.
There is a reason that NV has only really been able to get a foothold in tablets, android TV, cars and their own shield product. Quite simply put, they have historically been fast and hot. Great as a SOC within certain markets.
This is exactly why the benchmarks include
1) a way to repeat the benchmarks as described in the article see page 4 - 'phoronix-test-suite benchmark 1507285-BE-POWERLOW159'.
2) The compiler options are included
Armed with those two pieces of information, you can go and "prove" that the benchmark is, as you called it - bullshit. Although rarely, if ever that I am aware of, does anyone respond to an article with those two pieces of information and say - "here, if you run it in this mode, you will see a marked difference in performance".
As Bert64 says in the response to the grandparent, 99% of end users will be running the software - either pre-compiled by their distribution vendor in this way, or compiled by the benchmark author's defaults. If you really want to prove that the benchmark is crap, then by all means make meaningful suggestions to _any_ of the existing machine benchmarks.
Michael (Phoronix) and I had some interesting discussions with Sun (pre Oracle) about 64 vs 32. They argued that the benchmarks were misleading because they did not use the Sun Studio (IIRC) compiler for 64 bit. In the discussions, it became clear to even the Sun people that it was quite difficult for even the Sun people to configure and use the platform in the way they wanted Phoronix to. Out of the box, gcc compiling for 32 bit - was how they configured the systems. And guess what, the './configure;make;make install' triplet would compile the same way we did.
Full disclosure, I have a long history with Phoronix, and have been involved in work that they have done in the past.
Ideal was a reference to the "ideal" in the original post. There was no comment on it being ideal. I doubt there is an ideal.
That is how Android is dealing with ART. https://source.android.com/dev...
JAVA (Dalvik) the ideal ISA, dex2oat converts the java bytecode to native ISA (intel or ARM).
Similar to pNaCL in Chrome, where at least historically the LLVM IR (effectively the ISA) would be pushed to the chrome devices which would then complete the conversion to native code.
IANASS (I am not a seismic scientist)
The general belief (unfortunately google doesn't provide many non-tin foil links) is that it isn't the fracturing process itself that is inducing siesmicity it is the presurrized injection of the waste slurry that is loosening the stresses and creating the swarm earthquakes.
The risk in your suggestion is that you will reduce risk and stresses in some areas which may increase acute stress in other areas. One unexpected area that becomes the hinge point for a large stress could trigger a larger issues in an unexpected.
+1
I agree fully. Having tried to get my mind around d3.js, there are *a lot* of leaps of understanding in coming to up to speed. Watching someone who provides a narrative how they get from a to d by verbalizing b and c will help immensely. The docs really go just from a to g.
As a viewer, it's about learning technique and thought processes. Identifying issues, attempting a particular thought process, only those that provide a strong narrative to the work they are doing will be likely "stars". Watching how good programmers (assumption) deal with their environment and the typical problems they face. Seeing how people top down or bottom up write code is very interesting (within limits).
As a broadcasting coder, it takes a fair amount of personal confidence to do it, particular in this field. Having to verbalize what you are thinking and how you are considering the problems in front of you is actually quite challenging. Those that do well in the broadcasting scene will most likely be strong professionally as well.
That said, I personally don't understand the fandom about broadcast games to the level that it has taken. I get the benefits, but I don't get the market.
Tin foil hat on. It came to me last week.
Google has recently released Project Fi. A project/product (is project a codeword for beta now?) that will allow seamless transition between 2G/3G/LTE and *WiFi* for increased coverage and strength.
Project Fi is bandwidth charged, independent of data link being used - so while the underlying carriers (T-Mobile & Sprint) may charge wholesale for data, google will effectively get the bandwidth at "Google WiFi" for free - meaning that the data charges are a lot more profitable when going past a Starbucks, in NYC, etc. Although unproven, google might actually have meaningful alternate revenue sources from this model.
This is not fundamentally different than Xfinity's wifi sharing - except google is going for the Free WiFi in the Starbucks, NYC, etc. B2B is a lot more pragmatic, and a lot easier to enable.
Now if only Project Fi worked in a phone that was in the $2-300 range, I'd probably give it a go. But the Nexus 6 is too big and too expensive. Hopefully the invite won't expire.
The fact that they have a design patent aside, Blackberry has been iterating on the fret + rounded keys design since the blackberry bold. It's what makes a "modern" blackberry recognizable.
https://www.google.com/search?...
https://www.google.com/search?...
They look quite similar.
From TFA, it is a design patent - aka Trade Dress.
From http://www.theglobeandmail.com... , the actual complain seems with merit. The frets (metal lines), key shape (rounded corners) and space bar seem to be pulled entirely from the Blackberry Q10. It's as blatant as the typical Chinese typo-based (Sony vs Somy) ripoffs.
If you saw a phone with a the Typo keyboard, it would be reasonable to assume that its an extra tall Q10. That's what Blackberry has sued about.
From TFA...
tricked into viewing a piece of American culture ruined and rewritten right in front of their very eyes.
.
It's an Australian movie, set in Australia, with Australian actors, Australian Director, Australian Writers.
Piece of co-opted Australian culture... They even drive on the left side of the road - check out IMDb for shots of the yellow interceptors...
Hollywood never co-opts other cultures do they...
EU privacy laws are fairly painful for US companies to comply with. To do business with EU individuals, Personal Identifiable Information needs to be handled according to a set of rules - http://ec.europa.eu/justice/da...
It is often simpler for Amazon deployed companies to set up in the Ireland AWS zone.
As others have mentioned, most foreign SIGINT/COMINT agencies can't gather intelligence domestically, so it lowers barriers. Ironically US companies that want to deal with EU customers may end up moving everything to Ireland. However this allows the NSA to gather intelligence indirectly on US citizens.
AT&T does - phone support has their playbook, which doesn't go very far. Their online customer support actually was very helpful.
My story getting IPV6 on AT&T - http://use-cases.org/2015/01/1...
If your router enables IPv6, your devices have IPv6 access - no endpoint changes necessary. Current versions of most Operating Systems actually prefer IPv6 but fallback quickly. So it is likely to be turned on transparently.
There is no INTERNAL_IP6_ADDRESS, there is just an IP6_ADDRESS. The firewall blocks or permits dynamically (likely stateful connection management). The /64 subnet that is routed to your network is expected to be routed to the endpoint by your router if needed (modulo firewall rules).
The biggest issue for home networking is the lack of management of the router/firewall itself. You can't port forward (no config UI), you can't permit specific ports in most current home router implementations. However, configuration of ports and so on are not something that the vast majority of users know or care about.
With the current incantation of Amazon Web Services (VPC),
IPv6 support is currently not available for load balancers in Amazon VPC (EC2-VPC).
http://docs.aws.amazon.com/Ela...
So there goes lots of the internet....
2: Attackers can view your entire IP space. A simple nmap scan, then choosing what zero days to use... instant pwn-ership.
Hmm... Non-direct allocated IP on your subnet, 64 bit subnet, pwn-ership aint that trivial. Scanning a 64-bit address space (AT&T allocates a full /64 to me at home) is going to be pretty obvious at the firewall.
Welcome back to the internet of the early 1990's we all lived on the internet with real IPs, but were protected from firewalls... This whole concept of everyone on a Class C/B/A private subnet thing has only been around for a couple of decades.