It sounds like we're due for a protocol change where these addresses are updated to prevent long-term tracking. Give the operator the choice of static or randomized. Some work would have to be done to ensure devices would continue to correctly identify a network they've previously connected to. But some of those details ignored, I think everyone gets my point here. The thing here is which I don't get is that the broadcast id of these routers isn't typically available to anyone intercepting your IP traffic. So this database won't help someone find you unless your machine has been compromised. Perhaps one solution is to have network hardware watch for the Ids but hide them from the OS. That would prevent a compromised machine from revealing its location while at the same time allowing for the broadcast Id to useful for assisted GPS. I'd be a little sad if we lost the awesome navigational benefits due to privacy concerns without first considering protocol/implementation fixes to address the concerns.
One great example is indoor maps. You can get maps for the inside of a mall now as part of your smartphone's map app. You just zoom in on the mall and it turns into an indoor map. Without the wifi, you're not going to have an accurate location marker inside.
There are plenty of phones which do a great job with security. Blackberry being the primary example. Even the iphone now supports full-disk encryption and remote wipe. Just because most android devices are horrible doesn't mean all phones are.. To counter your desktop point, I doubt most linux desktops are put together with full drive encryption by default..
Different frequencies affect things differently. eg microwave radiation is absorbed easily and heats our food. xrays mostly go straight through tissue. Different frequencies will have different penetrating capabilities. One could potentially be more damaging to our skin/brain than the other.
The recent riot in Vancouver is an excellent example of this. The police probably caught a good hundred people directly thanks to social media. Maybe they would have found most of those people by other means.. but they basically had the worst offenders all identified within hours thanks to social media.
Hardly true. Example: my SSD (intel 320 line) encrypts everything on disk. It stores the encryption key in a secured portion of the hardware. And that key is encrypted/decrypted with a user-entered string on bootup via the bios.
The phone could easily require the user to enter the PIN once on boot-up to unlock a key which is used to store passwords. That would prevent your phone from downloading email until the first time you've unlocked it after boot. It would still be a huge step up in security over storing it in plain-text with the rest of the user data.
I think that plate numbers can already be flagged. They're just not tracked. So this doesn't really affect the uninsured case. I sure got pulled over quick when my registration expired. I rather doubt it was the super tiny sticker which the cops noticed at night. It was probably flagged as recently expired. The difference here would be that you could look back for sightings of a car that was just reported stolen or silently track someone without a warrant, eg anti-terrorism. But I honestly think that we need more of this, not less. I'm constantly annoyed by blatantly illegal driving. It annoys me that chronic speeders and such aren't flagged by stationary plate readers along the highway, etc. Seems like a small investment would make things a whole lot safer if people stopped crying because they got a ticket..
It seems silly to expect larger v1 apps to be approved as quickly as the average shovelware. It's obviously going to contain a lot more new code and functionality than the average app.
There are multiple UI targets for the single OS platform. You can develop a native, rich, highly optimized, and awesome interface for the phone, xbox, or desktop if you want. The advantage is that everything else doesn't have to be rewritten. Simple apps will be more of a lowest-common-denominator with HTML/jscript-based UIs. That's more of your typical smartphone weather app example. On your desktop, you could just pin it in the sidebar. Developers would also want to think about touch and mouse/keyboard differently. If you want a gaming example, the Unreal engine is available on a ton of platforms: desktop, xbox, ps3, iOS.. In this case, they'd only need one main rendering path to target the 360, windows desktop, windows phone phone, etc. That's why everyone always says the 360 is the easiest to develop for. Not only is it familiar to PC developers, it's easy to try stuff out on PC hardware. But hopefully you'd see other things like your xbox friends list, voice chat support, etc on the phone and desktop as well. Give developers more free stuff on more platforms.
Same OS doesn't mean the same UI. Examples: iOS = OSX, Android = Linux. This is more in reference to MS dropping the windows CE platform which I believe was the base for the 360 and WP7. You don't have to expect every edition to support the same features. The phone wouldn't have the 'standard' windows desktop for example. But at the same time, you'd want the phone to support the same audio, video, usb, etc drivers for simplicity. Then when you put an ATI chip in your phone, they don't need to rewrite everything. The games would all go through directx, etc.
Bluetooth has always been a known attack vector. I remember one that affected symbian phones for example. I used to get the odd file transfer request on my phone from other people who were infected. I think this might have been it.. http://www.f-secure.com/v-descs/cabir.shtml
I don't think they've shown much in regards to their desktop enhancements. At this point, I think the focus has been entirely on the tablet. And for that, you'd get the OS with the hardware as you say.
I can't think of a single piece of legacy software I'd want to run on a tablet. Maybe there's some game from the 90s which doesn't get recompiled and won't work on ARM. I'm okay with that. Everything I actually use is maintained. Even the proprietary stuff I use at work can be recompiled. It would be different if you were upgrading an existing machine and lost functionality. There are pros and cons to every platform and hardware choice. But win8 on ARM will surely be supported by major software vendors. And the app-store XAP apps (see windows phone's app model) will be hardware agnostic from the start..
That's touch+stylus. If that loses to touch-only, I think you failed math.
PhotoShop? On a "tablet-class CPU"? Yes. The biggest slowdown in photoshop is disk IO. That's MUCH faster on an SSD. Adobe is constantly working to improve their hardware acceleration, etc. Another example: the ipad companion app. Adobe clearly likes touch and stylus (watcom). It's what graphical artists crave.
Sure, use gmail. It won't work for anyone with an exchange account. It's okay if that isn't you. But let's accept that it's a huge market. After all, that's why android supports it. Outlook is the work horse of the corporate office though.
Sweet. I didn't know iphones can be wirelessly synced to android tablets.:P
iOS and Android were both developed from full desktop OSes and are both still full desktop OSes at their core. Android is linux. iOS is OSX (which was mostly freebsd). They each simply added a new UI for touch and a sandboxed app model. Neither were "designed to be a tablet OS." They were designed to be appropriate for multiple platforms. That's the exact same model as win 8.
But also have the advantages of an SSD. You get to disable background fragmenting, prefetch, etc.. Even with a slow cpu, an ssd can make a machine feel a lot faster with more consistent behavior (fewer disk thrashing 'hangs').
But still... you gotta admit it would make for a nice feature-add for a tablet/laptop. Even the ability to log into xbox live and play the live arcade titles with a controller would be a cool feature. We see lots of xbox live integration on the phone.. I would have to assume the model/design for win 8 will be similar to wp7 until I hear differently, just replace mobile games with PC and possibly some xbox ports.
I think most of the speculation includes an "xbox-compatible" graphics processor which won't run an unlicensed xbox game. I agree though, it's a stretch and doesn't seem to make a lot of sense. However, if it's on a game-by-game basis, older titles could have PC-support added later without ever hurting the all-important launch sales.
Stylus input for OneNote and PhotoShop maybe? Outlook for email? Safari for web browsing? Itunes to sync your iphone? The javascript/html5 app platform? I don't know, maybe all you do check the weather. Regardless, it'll add choice and alternatives into the marketplace and drive UI enhancements.
Of course most users won't change from one OS to the other. They'll keep whatever comes with it when they buy it.
Apps can be recompiled for different target architectures without being rewritten. There is as much reason to run windows on ARM as there is to run it on x86. A computer needs an OS. At the moment, ARM chips offer a huge power savings when compared to x86 chips. An ARM-based laptop/tablet is going to last a lot longer than an i3.
If it's a pay service, maybe the main executable is recompiled for x86? You just need the disc for copy-protection? It seems reasonable from a technical perspective. The 360 is around five years old. Modern PCs can smoke it in terms of performance. A recompiled executable is probably enough on any modern gaming rig. The tough part would be building the infrastructure to enable/deploy/integrate it all.
Slashdot Mirror
It sounds like we're due for a protocol change where these addresses are updated to prevent long-term tracking. Give the operator the choice of static or randomized. Some work would have to be done to ensure devices would continue to correctly identify a network they've previously connected to. But some of those details ignored, I think everyone gets my point here. The thing here is which I don't get is that the broadcast id of these routers isn't typically available to anyone intercepting your IP traffic. So this database won't help someone find you unless your machine has been compromised. Perhaps one solution is to have network hardware watch for the Ids but hide them from the OS. That would prevent a compromised machine from revealing its location while at the same time allowing for the broadcast Id to useful for assisted GPS. I'd be a little sad if we lost the awesome navigational benefits due to privacy concerns without first considering protocol/implementation fixes to address the concerns.
One great example is indoor maps. You can get maps for the inside of a mall now as part of your smartphone's map app. You just zoom in on the mall and it turns into an indoor map. Without the wifi, you're not going to have an accurate location marker inside.
There are plenty of phones which do a great job with security. Blackberry being the primary example. Even the iphone now supports full-disk encryption and remote wipe. Just because most android devices are horrible doesn't mean all phones are.. To counter your desktop point, I doubt most linux desktops are put together with full drive encryption by default..
Different frequencies affect things differently. eg microwave radiation is absorbed easily and heats our food. xrays mostly go straight through tissue. Different frequencies will have different penetrating capabilities. One could potentially be more damaging to our skin/brain than the other.
Excellent point good sir. I mean, um, wait a second, wtf are you talking about?
The recent riot in Vancouver is an excellent example of this. The police probably caught a good hundred people directly thanks to social media. Maybe they would have found most of those people by other means.. but they basically had the worst offenders all identified within hours thanks to social media.
Hardly true. Example: my SSD (intel 320 line) encrypts everything on disk. It stores the encryption key in a secured portion of the hardware. And that key is encrypted/decrypted with a user-entered string on bootup via the bios.
The phone could easily require the user to enter the PIN once on boot-up to unlock a key which is used to store passwords. That would prevent your phone from downloading email until the first time you've unlocked it after boot. It would still be a huge step up in security over storing it in plain-text with the rest of the user data.
I think that plate numbers can already be flagged. They're just not tracked. So this doesn't really affect the uninsured case. I sure got pulled over quick when my registration expired. I rather doubt it was the super tiny sticker which the cops noticed at night. It was probably flagged as recently expired. The difference here would be that you could look back for sightings of a car that was just reported stolen or silently track someone without a warrant, eg anti-terrorism. But I honestly think that we need more of this, not less. I'm constantly annoyed by blatantly illegal driving. It annoys me that chronic speeders and such aren't flagged by stationary plate readers along the highway, etc. Seems like a small investment would make things a whole lot safer if people stopped crying because they got a ticket..
I think you have that backwards..
I blocked their apps so long ago I barely even remember what their spam looks like...
It seems silly to expect larger v1 apps to be approved as quickly as the average shovelware. It's obviously going to contain a lot more new code and functionality than the average app.
There are multiple UI targets for the single OS platform. You can develop a native, rich, highly optimized, and awesome interface for the phone, xbox, or desktop if you want. The advantage is that everything else doesn't have to be rewritten. Simple apps will be more of a lowest-common-denominator with HTML/jscript-based UIs. That's more of your typical smartphone weather app example. On your desktop, you could just pin it in the sidebar. Developers would also want to think about touch and mouse/keyboard differently. If you want a gaming example, the Unreal engine is available on a ton of platforms: desktop, xbox, ps3, iOS.. In this case, they'd only need one main rendering path to target the 360, windows desktop, windows phone phone, etc. That's why everyone always says the 360 is the easiest to develop for. Not only is it familiar to PC developers, it's easy to try stuff out on PC hardware. But hopefully you'd see other things like your xbox friends list, voice chat support, etc on the phone and desktop as well. Give developers more free stuff on more platforms.
Same OS doesn't mean the same UI. Examples: iOS = OSX, Android = Linux. This is more in reference to MS dropping the windows CE platform which I believe was the base for the 360 and WP7. You don't have to expect every edition to support the same features. The phone wouldn't have the 'standard' windows desktop for example. But at the same time, you'd want the phone to support the same audio, video, usb, etc drivers for simplicity. Then when you put an ATI chip in your phone, they don't need to rewrite everything. The games would all go through directx, etc.
Bluetooth has always been a known attack vector. I remember one that affected symbian phones for example. I used to get the odd file transfer request on my phone from other people who were infected. I think this might have been it.. http://www.f-secure.com/v-descs/cabir.shtml
I don't think they've shown much in regards to their desktop enhancements. At this point, I think the focus has been entirely on the tablet. And for that, you'd get the OS with the hardware as you say.
I can't think of a single piece of legacy software I'd want to run on a tablet. Maybe there's some game from the 90s which doesn't get recompiled and won't work on ARM. I'm okay with that. Everything I actually use is maintained. Even the proprietary stuff I use at work can be recompiled. It would be different if you were upgrading an existing machine and lost functionality. There are pros and cons to every platform and hardware choice. But win8 on ARM will surely be supported by major software vendors. And the app-store XAP apps (see windows phone's app model) will be hardware agnostic from the start..
That's touch+stylus. If that loses to touch-only, I think you failed math.
PhotoShop? On a "tablet-class CPU"? Yes. The biggest slowdown in photoshop is disk IO. That's MUCH faster on an SSD. Adobe is constantly working to improve their hardware acceleration, etc. Another example: the ipad companion app. Adobe clearly likes touch and stylus (watcom). It's what graphical artists crave.
Sure, use gmail. It won't work for anyone with an exchange account. It's okay if that isn't you. But let's accept that it's a huge market. After all, that's why android supports it. Outlook is the work horse of the corporate office though.
Sweet. I didn't know iphones can be wirelessly synced to android tablets. :P
iOS and Android were both developed from full desktop OSes and are both still full desktop OSes at their core. Android is linux. iOS is OSX (which was mostly freebsd). They each simply added a new UI for touch and a sandboxed app model. Neither were "designed to be a tablet OS." They were designed to be appropriate for multiple platforms. That's the exact same model as win 8.
The sad thing is, you'd have been +5 funny if you had left out the bit in parenthesis :)
They need a quick release to get into the ipad market. Win7 isn't doing too well there..
But also have the advantages of an SSD. You get to disable background fragmenting, prefetch, etc.. Even with a slow cpu, an ssd can make a machine feel a lot faster with more consistent behavior (fewer disk thrashing 'hangs').
But still... you gotta admit it would make for a nice feature-add for a tablet/laptop. Even the ability to log into xbox live and play the live arcade titles with a controller would be a cool feature. We see lots of xbox live integration on the phone.. I would have to assume the model/design for win 8 will be similar to wp7 until I hear differently, just replace mobile games with PC and possibly some xbox ports.
I think most of the speculation includes an "xbox-compatible" graphics processor which won't run an unlicensed xbox game. I agree though, it's a stretch and doesn't seem to make a lot of sense. However, if it's on a game-by-game basis, older titles could have PC-support added later without ever hurting the all-important launch sales.
Stylus input for OneNote and PhotoShop maybe? Outlook for email? Safari for web browsing? Itunes to sync your iphone? The javascript/html5 app platform? I don't know, maybe all you do check the weather. Regardless, it'll add choice and alternatives into the marketplace and drive UI enhancements.
Of course most users won't change from one OS to the other. They'll keep whatever comes with it when they buy it.
Apps can be recompiled for different target architectures without being rewritten. There is as much reason to run windows on ARM as there is to run it on x86. A computer needs an OS. At the moment, ARM chips offer a huge power savings when compared to x86 chips. An ARM-based laptop/tablet is going to last a lot longer than an i3.
If it's a pay service, maybe the main executable is recompiled for x86? You just need the disc for copy-protection? It seems reasonable from a technical perspective. The 360 is around five years old. Modern PCs can smoke it in terms of performance. A recompiled executable is probably enough on any modern gaming rig. The tough part would be building the infrastructure to enable/deploy/integrate it all.