And there is no requirement in the Constitution that a business provides you a service. To imply otherwise would be way outside what even most 'literalists' believe about its intent. A business can't compel the government to limit your speech, but a business can deny you the use of their forum to practice your speech. Certain laws have created protected classes that a businesses can't discriminate against, but a person wanting to donate to an organization is not a protected class.
Now I believe Wikileaks should be protected as a part of the press. I disagree with what Visa and Mastercard have done. And I wish in a better country, until Wikileaks is found guilty of breaking the law by a court, representatives in our government would have a discussion on whether Visa and MC actions were appropriate, and whether given they are the dominant payment network in an oligopoly, perhaps they should be quasi-nationalized or just compelled to process payments unless they have evidence of fraud or are directed not to by duly authorized government agents (and not bloviating politicians).
Tried to watch the first episode last night on Netflix streaming. I love Wooster & Jeeves. There were a few funny gags in this, but it rapidly got so much of a bore that I was forced by my fellow TV watchers to turn it off.
I believe NandroidBackup will allow them to back up their apps and other local data and restore after a system wipe, if they know when the system wipe is coming.
That's what most people use when they are upgrading rooted versions of Android like Cyanogenmod. I haven't had to try it yet, because I'm on CM6.something. CM6.1 will be out soon, and I'll get to try NandroidBackup then.
Unless your company specifically forbids it, I'd use TouchDown for Android. I've set it up for my mom and it seemed to work ok. I couldn't get her tasks to sync, but I'm sure I could have figured it out with some more effort. The email came down fine. It isn't quite as chic as having everything integrated into the native apps on your phone, but the interface seemed serviceable enough, and it keeps more of a firewall between your work and personal life.
Many companies don't specifically check the client string. If they do, and you really want to, you can masquerade as an iPhone. It supports Exchange remote wipe (but only for the TouchDown data store), all your personal data on the phone will be unaffected. I have Prey on my phone to wipe my personal data in case it gets stolen.
I was riding shotgun in my girlfriend's dad's 2010 Camry, trying to get his cellphone to auto-connect with the radio. Bluetooth was being sketchy as common, and Toyota has the most hideously user unfriendly menu and button layout I have ever seen in an OEM radio product. I'd be embarrassed if I was involved in designing that tripe.
I tried deleting the pairing information, and when I went to repair the phone, the radio said "This feature is disabled with the vehicle in motion." I nearly hit the roof, it just added insult to injury.
After that, I vowed I would not buy a Toyota product, or encourage anyone else to, unless their user interface and legal team did an about face. I was going to write them a love note saying my mother was in the market for a new car, and after what happened I encouraged her not to. But the next month, Toyota's little PR meltdown occurred, and I figured my letter, already unlikely to be read by anyone who mattered, would now just hit the circular file.
T-Mobile didn't discontinue the feature, only the $10/mo upgrade that provided unmetered minutes. Most people believe it wasn't discontinued because of low penetration, but to encourage people to upgrade to their "low cost" unlimited or higher rate plans. Now all minutes, regardless of how they originate, are billed to your rate plan.
The feature is called UMA, and they sell phones (mostly Blackberries) that feature it. They supposedly will have an app that will allow UMA on Android soon. One cool advantage is you can connect by UMA/WiFi in a foreign country and place or receive calls to/from your home country with no roaming charge. It is billed as if you are still in your home country. Of course calls to/from numbers in the foreign country you are in will be charged long distance as if they were originated inside your home country too.
It remains to be seen if Gingerbread will even reasonably run on a G1, so it may be a non-issue that the focus of CM has moved on. It was rather heroic they got FroYo running on it so well.
I noticed you outlined several issues with the older CM6. I'm running CM6.1 on my G1 rignt now, with several relatively easy performance tweaks. It is as fast or faster than the sanctioned T-Mo firmware, supports apps and data on SD ext2/3/4, and official apps on SD seem to work fine. Only problem I've encountered is 3 of 10 apps I have must be moved to the phone before they can update themselves, and then they can be moved back to SD to run.
I was planning on getting a new phone as soon as I could afford it before CM6.1. Now I no longer have any immediate plans, though the G2 is pretty cool looking, I don't think I can stomach paying more than $300 unsubsidized for a phone that can so easily be damaged.
I'd say you are being generous. I complain about the fact car companies don't give access to certain features in code or data on the CAN bus of cars. I'm on email lists of DIY enthusiasts who complain about similar.
Car mfgrs are also terrible about not following specs, or creating proprietary specs and charging a lot for access, where they should be encouraging open industry standards to develop for new features. The argument about safety is used to justify this, but it is not terribly germane, as there are ways they could secure the engine/transmission/brake code while still giving third party access to other features. Another reason is proprietary secrets, though I don't think software should be patentable, so that one is out.
And really I feel like all car code should be available to 3rd parties, regardless of the safety implications, and if you'd like to run 3rd party code on your car, you sign a contract with the mfgr acknowledging you waiving warranty and liability claims, and you get a physical dongle for a low cost that basically gives you root access to your car. The dongle is less about the method of delivery for access, than about the act of inserting it is willful acknowledgement of what you are doing.
The performance of SSDs holds up better than HDDs when run close to capacity, but everything I've read says it is better not to do this because it limits the amount of wear leveling on the memory cells the SSD can do. Even though SSDs are rated in millions of hours of MTBF, that really doesn't mean anything. The memory cells have ~10k write cycles and if you have swap file on, that has to write to the same area because the SSD is almost full, and you use your computer a lot, your MTBF might be a couple years.
If you need that much capacity, don't have 2 drive bays where you can run an OS SSD and data HDD at the same time, aren't inclined to spend $500 on a 200gb SSD, you might want to look at the Seagage Momentus XT hybrids, which can get you 250gigs for $100. If you do run one SSD near capacity, be sure to max out your memory, turn off swap space, and do all the other OS tweaks for SSDs to limit the number of writes.
If I posted an article from HuffPo, and didn't bother to (if I were using that article for my frame of reference) instead link down to its primary sources from reputable academic researchers, that were not specifically known for bias, then I doubt many commenters would take me seriously.
I've looked for information on this topic in the past from non-biased sources that don't pick and choose resarcher's findings based on the news source's or researcher's ideology. I'm not going to spend my limited time breaking the Heritage piece down point for you, offering rebuttals, and finding alternative sources again.
Given the level of discourse in politics and the news (that I'd strongly argue is primarily the responsibility of Republicans and other quasi-conservatives that seem to be in the majority of that party), I have no problem totally discounting the message when the messenger is a certain group known for severe bias and cognitive dissidence. That doesn't mean I won't believe the message given alternative sources, only that I will not consider information from that messenger worthy of consideration. I actually do this on certain liberal news and political sites as well.
Various studies have indicated that Medicare has either an extremely advantageous administrative expense ratio compared to private insurance, or possibly a slight but negligible advantage, depending on what you agree should be included or not.
It seems a gaggle of Washington Bureaucrats can't do much worse damage to the admin expense ratio compared to the Free Market Insurance Industry moochers.
You mean the flaw that was fixed in Oct 2009? A year ago. It'd help if you were specific.
Over the past year, I've read about at least 5 what I would consider very concerning iPhone/iOS bugs. Some were recently fixed, others were waiting for a response from the notoriously uncommunicative Apple PR system. I'm not in the mood to spend hours trying to track down all these articles for a quick conversation on Slashdot. I didn't keep track of the articles because they weren't relevant to my life more than reminding me to be wary of Apple products.
Coverity themselves say 359 bugs, with 88 of them being high-risk security flaws. And that's just in the kernel. Yes, that's a huge number. With iPhone, a single security flaw (such as the one you mentioned) is big news on slashdot.
And people in that thread who have used Coverity said their bug count and rating system is notoriously duplicative and generous. One person said the actual serious bugs will probably turn out to be less than 22. It isn't a huge number for a complex OS. And again we have no idea how many serious bugs Coverity or any other tool would identify in iOS because it is closed source.
There's absolutely no evidence for OSS being an advantage in fixing bugs.
That is absolutely untrue. As I said before, Coverity was a research project originally unleashed on the Linux kernel. It identified thousands of bugs initially. The actual bugs WERE quickly fixed by the community.
They rely on manufacturers issuing updates to privide fixes and patch security defects. And they are poor at that...Again, advantage iPhone - Apple issues a security fix, and it's quickly available to all, and generally installed automatically. The power of tight integration.
All manufacturers are poor at this, including Apple. iOS4 is not backward compatible to the original iPhone/iPod touch, and there are some remaining bugs on the original iPhone that likely won't be fixed. This situation reflects poorly on HTC, it does not yet reflect poorly on Android, but it may in the future after more indepth research.
Again, an assertion in the RMS catechism, believed without question by freetards...I'll take professional software engineers doing their job against a bunch of amateurs doing what they fancy any day.
Absolutely untrue again. For one blatantly obvious example, when code is freely available, it can be sent through automated review and exploit tools such as Coverity that find potential flaws. You seem terribly misinformed or ideological. Much of the important bits of Linux are written by software engineers on the job, or in their free time, or by extremely experienced "amateurs" that by every measure match or rival "professional" counterparts.
That would be the closed source Blackberry.
But it isn't because Blackberry is closed source. I have no doubt the Blackberry OS would be incrementally better with public review of their code. However, BB source code has been reviewed by several government agencies, including likely the NSA when it was being considered for use by the President. There is extensive non-code documentation they have had to submit to large companies spelling out how the OS operates and why it is secure, before it was considered for implementation. Again this isn't ideal, but it is good evidence. Finally, I am sure there have been some BB exploits found, but I can't remember reading about any recently. So if publicized exploits are the ultimate judge for you, BB takes it.
With Android, you can just pull the SD card out of the device, and read it on your PC directly. That'll never be fixed. Access to data on the internal drive? Whoops
Again that is by design and I wouldn't have it any other way. If an app on Android needs to keep its data secure, the developer knows it must come over the air encrypted, and stay in volatile memory, or only be written to flash while encrypted. It doesn't matter that you can take the SD card out, there is nothing to read in that case.
iPhone Apps only have access to their own private data directory.
Doesn't matter. I'm talking about the ability to read the contents of supposedly encrypted iPhone data that is allowed to be unencrypted inflight by iOS using another computer.
when the app in question can only work on the Android... due to fundamental security mistakes on Android
The "app in question" works by design on Android. There is currently no confirmed data there were "security mistakes" in Android that allowed this behavior. The only question is to what extent the app was able to cloak itself and if that should be prevented.
huge numbers of security vulnerabilities on Android.
There weren't a "huge" number. There were 88. People who have used the tool that claimed these vulnerablities, and its categorization system, have said the actual number of real vulnerabilities are probably half that number, and less than half of those remaining are probably legitimately "serious."
When that tool was released for Linux originally, there were thousands of identified potential bugs. The actual ones were quickly quashed by the community. The fact that Android source is open, means many of these "bugs" will be quickly quashed also. In fact, the targeted build of Android wasn't the stock Google one, it was a customized HTC one. It remains to be seen how many of the actual serious bugs are present in the standard Android build.
Finally, since iOS source code isn't available for community review and testing like Linux and Android are, there are likely as many or more bugs in iOS. There have been plenty already inadvertently identified serious iOS bugs by enthusiasts and security researchers. The only mobile OS that has a solid claim to superior security is Blackberry. Apple has demonstrated their inadequacies, Android looks to have some inadequacies that will be quickly addressed.
Face it, Android is far more susceptible to malware than the iPhone.
That absolutely remains to be proven, and until today there was little evidence to support that assertion. The evidence released today is highly preliminary.
I never claimed there was a specific exploit for capturing and resending SMS on iPhone. But there are plenty of other exploits that are as big, or a bigger security concern, including unencrypted access to the file system containing user data.
As I said, access to SMS on permission was by design with Android. The only concerning thing about this episode, was that apparently the app could hide by not showing an icon, not showing up in the downloaded applications list, and possibly hiding in the process menu.
My ancient $50 WRT-54GL with DD-WRT does segregated VLANS with multiple SSIDs and independent passkeys. Running one now keyless for my neighbors, and WPA2 for me.
Doubtful, there are plenty of iPhone security holes that can be exploited. Having world readable SMS access (on permission) was by design for Android. And that is a design consideration I am still comfortable with.
Seriously, I've never been disappointed with T-Mobile in the South Central US. From the carrier rankings it seems they are good in the West also, and not so good on the East Coast.
Given that iPhones are limited to Edge on T-Mo's network, and that in general they are very friendly to unsupported phones (they helped me get an AT&T Blackberry working on their network), I'm surprised and disappointed they are acting like crybabies over this.
Everything else equal, a fixed wing drone will be more mechanically reliable than a manned helicopter, nothing to do with the drone, but with the realities of helicopter design.
Why does the FAA not allow drones in commercial airspace yet? Short answer is no one has took the time and money to develop one and get it certified. The longer answer is it depends on whether you are talking about piloted drones or autonomous drones.
There is a problem with coordination of pilot or autopilot to ATC requests, a pilot not physically being in the vehicle to make emergency avoidance maneuvers and trusting the autopilot to do it instead, and ensuring continuity of positive control of the autopilot or the wireless pilot interface. If a drone is going to be in airspace with passenger aircraft or over populated areas with heavy aircraft, the FAA wants to be damn confident it won't wreak havoc with highly automated commercial aircraft or Joe Bob in his Cessna.
Piloted military drones have a demonstrably higher accident rate. But I have no doubt after some teething pains and a lot of money, automated drones will have lower accident rates than piloted aircraft.
Used that as a generic term. I'm aware of the vague layout of US airspace. I was a student pilot in the early 1990's but I never got my ticket. Another commenter pointed out drones are not allowed in US airspace above 400 AGL or out of visual range of the operator (they can operate under RC rules).
My brother used to work as a commercial real estate appraiser. He talked to one of the first guys in Texas (perhaps the US) who retrofitted his Cessna with a viewport, a fancy DSLR, and a laptop. He flew around Houston and other cities in TX once a year or on demand, and took high res images that his software stitched together later. It may not be economical compared to a drone, but it was affordable, especially compared to satellite imagery at the time.
Were Google's drones just RC craft piloted by a certified pilot on the ground? I thought automated aircraft (no pilot) and RC craft flown by non-pilots were not allowed in controlled airspace in the USA.
Wow, thanks for the heads up. So many books and adoption sites say retired Greyhounds can make excellent pets for lazy people because they like to lay around and only need occasional sprints to work off their energy. It makes sense that without lots of socialization and training early in life, they could be difficult pets. I wonder how common it is to get an ill tempered one?
Rotide's quote was cute, but didn't get to the root of the matter. The real issue is when you have a DHCP server you are running on an unsecured wireless connection, and you don't even bother to set your SSID to something like (stayoffmywireless), then you are inviting people to use it. I specifically and intentionally have my wireless unsecured to allow neighbors to occasionally borrow it, though I have the speed significantly throttled so I don't turn into the neighborhood free ISP.
Slashdot Mirror
And there is no requirement in the Constitution that a business provides you a service. To imply otherwise would be way outside what even most 'literalists' believe about its intent. A business can't compel the government to limit your speech, but a business can deny you the use of their forum to practice your speech. Certain laws have created protected classes that a businesses can't discriminate against, but a person wanting to donate to an organization is not a protected class.
Now I believe Wikileaks should be protected as a part of the press. I disagree with what Visa and Mastercard have done. And I wish in a better country, until Wikileaks is found guilty of breaking the law by a court, representatives in our government would have a discussion on whether Visa and MC actions were appropriate, and whether given they are the dominant payment network in an oligopoly, perhaps they should be quasi-nationalized or just compelled to process payments unless they have evidence of fraud or are directed not to by duly authorized government agents (and not bloviating politicians).
But unfortunately we don't live in that country.
Tried to watch the first episode last night on Netflix streaming. I love Wooster & Jeeves. There were a few funny gags in this, but it rapidly got so much of a bore that I was forced by my fellow TV watchers to turn it off.
I believe NandroidBackup will allow them to back up their apps and other local data and restore after a system wipe, if they know when the system wipe is coming.
That's what most people use when they are upgrading rooted versions of Android like Cyanogenmod. I haven't had to try it yet, because I'm on CM6.something. CM6.1 will be out soon, and I'll get to try NandroidBackup then.
Beta testing system level Android software? Cool.
Unless your company specifically forbids it, I'd use TouchDown for Android. I've set it up for my mom and it seemed to work ok. I couldn't get her tasks to sync, but I'm sure I could have figured it out with some more effort. The email came down fine. It isn't quite as chic as having everything integrated into the native apps on your phone, but the interface seemed serviceable enough, and it keeps more of a firewall between your work and personal life.
Many companies don't specifically check the client string. If they do, and you really want to, you can masquerade as an iPhone. It supports Exchange remote wipe (but only for the TouchDown data store), all your personal data on the phone will be unaffected. I have Prey on my phone to wipe my personal data in case it gets stolen.
I was riding shotgun in my girlfriend's dad's 2010 Camry, trying to get his cellphone to auto-connect with the radio. Bluetooth was being sketchy as common, and Toyota has the most hideously user unfriendly menu and button layout I have ever seen in an OEM radio product. I'd be embarrassed if I was involved in designing that tripe.
I tried deleting the pairing information, and when I went to repair the phone, the radio said "This feature is disabled with the vehicle in motion." I nearly hit the roof, it just added insult to injury.
After that, I vowed I would not buy a Toyota product, or encourage anyone else to, unless their user interface and legal team did an about face. I was going to write them a love note saying my mother was in the market for a new car, and after what happened I encouraged her not to. But the next month, Toyota's little PR meltdown occurred, and I figured my letter, already unlikely to be read by anyone who mattered, would now just hit the circular file.
T-Mobile didn't discontinue the feature, only the $10/mo upgrade that provided unmetered minutes. Most people believe it wasn't discontinued because of low penetration, but to encourage people to upgrade to their "low cost" unlimited or higher rate plans. Now all minutes, regardless of how they originate, are billed to your rate plan.
The feature is called UMA, and they sell phones (mostly Blackberries) that feature it. They supposedly will have an app that will allow UMA on Android soon. One cool advantage is you can connect by UMA/WiFi in a foreign country and place or receive calls to/from your home country with no roaming charge. It is billed as if you are still in your home country. Of course calls to/from numbers in the foreign country you are in will be charged long distance as if they were originated inside your home country too.
It remains to be seen if Gingerbread will even reasonably run on a G1, so it may be a non-issue that the focus of CM has moved on. It was rather heroic they got FroYo running on it so well.
I noticed you outlined several issues with the older CM6. I'm running CM6.1 on my G1 rignt now, with several relatively easy performance tweaks. It is as fast or faster than the sanctioned T-Mo firmware, supports apps and data on SD ext2/3/4, and official apps on SD seem to work fine. Only problem I've encountered is 3 of 10 apps I have must be moved to the phone before they can update themselves, and then they can be moved back to SD to run.
I was planning on getting a new phone as soon as I could afford it before CM6.1. Now I no longer have any immediate plans, though the G2 is pretty cool looking, I don't think I can stomach paying more than $300 unsubsidized for a phone that can so easily be damaged.
I'd say you are being generous. I complain about the fact car companies don't give access to certain features in code or data on the CAN bus of cars. I'm on email lists of DIY enthusiasts who complain about similar.
Car mfgrs are also terrible about not following specs, or creating proprietary specs and charging a lot for access, where they should be encouraging open industry standards to develop for new features. The argument about safety is used to justify this, but it is not terribly germane, as there are ways they could secure the engine/transmission/brake code while still giving third party access to other features. Another reason is proprietary secrets, though I don't think software should be patentable, so that one is out.
And really I feel like all car code should be available to 3rd parties, regardless of the safety implications, and if you'd like to run 3rd party code on your car, you sign a contract with the mfgr acknowledging you waiving warranty and liability claims, and you get a physical dongle for a low cost that basically gives you root access to your car. The dongle is less about the method of delivery for access, than about the act of inserting it is willful acknowledgement of what you are doing.
Allows you to run on the G2, non-T-Mobile versions of the Android operating system.
The performance of SSDs holds up better than HDDs when run close to capacity, but everything I've read says it is better not to do this because it limits the amount of wear leveling on the memory cells the SSD can do. Even though SSDs are rated in millions of hours of MTBF, that really doesn't mean anything. The memory cells have ~10k write cycles and if you have swap file on, that has to write to the same area because the SSD is almost full, and you use your computer a lot, your MTBF might be a couple years.
If you need that much capacity, don't have 2 drive bays where you can run an OS SSD and data HDD at the same time, aren't inclined to spend $500 on a 200gb SSD, you might want to look at the Seagage Momentus XT hybrids, which can get you 250gigs for $100. If you do run one SSD near capacity, be sure to max out your memory, turn off swap space, and do all the other OS tweaks for SSDs to limit the number of writes.
If I posted an article from HuffPo, and didn't bother to (if I were using that article for my frame of reference) instead link down to its primary sources from reputable academic researchers, that were not specifically known for bias, then I doubt many commenters would take me seriously.
I've looked for information on this topic in the past from non-biased sources that don't pick and choose resarcher's findings based on the news source's or researcher's ideology. I'm not going to spend my limited time breaking the Heritage piece down point for you, offering rebuttals, and finding alternative sources again.
Given the level of discourse in politics and the news (that I'd strongly argue is primarily the responsibility of Republicans and other quasi-conservatives that seem to be in the majority of that party), I have no problem totally discounting the message when the messenger is a certain group known for severe bias and cognitive dissidence. That doesn't mean I won't believe the message given alternative sources, only that I will not consider information from that messenger worthy of consideration. I actually do this on certain liberal news and political sites as well.
"Conservative Policy Research and Analysis | The Heritage Foundation"
Straight from the Conservative's mouth to the ears of babes.
Various studies have indicated that Medicare has either an extremely advantageous administrative expense ratio compared to private insurance, or possibly a slight but negligible advantage, depending on what you agree should be included or not.
It seems a gaggle of Washington Bureaucrats can't do much worse damage to the admin expense ratio compared to the Free Market Insurance Industry moochers.
You mean the flaw that was fixed in Oct 2009? A year ago. It'd help if you were specific.
Over the past year, I've read about at least 5 what I would consider very concerning iPhone/iOS bugs. Some were recently fixed, others were waiting for a response from the notoriously uncommunicative Apple PR system. I'm not in the mood to spend hours trying to track down all these articles for a quick conversation on Slashdot. I didn't keep track of the articles because they weren't relevant to my life more than reminding me to be wary of Apple products.
Coverity themselves say 359 bugs, with 88 of them being high-risk security flaws. And that's just in the kernel. Yes, that's a huge number. With iPhone, a single security flaw (such as the one you mentioned) is big news on slashdot.
And people in that thread who have used Coverity said their bug count and rating system is notoriously duplicative and generous. One person said the actual serious bugs will probably turn out to be less than 22. It isn't a huge number for a complex OS. And again we have no idea how many serious bugs Coverity or any other tool would identify in iOS because it is closed source.
There's absolutely no evidence for OSS being an advantage in fixing bugs.
That is absolutely untrue. As I said before, Coverity was a research project originally unleashed on the Linux kernel. It identified thousands of bugs initially. The actual bugs WERE quickly fixed by the community.
They rely on manufacturers issuing updates to privide fixes and patch security defects. And they are poor at that...Again, advantage iPhone - Apple issues a security fix, and it's quickly available to all, and generally installed automatically. The power of tight integration.
All manufacturers are poor at this, including Apple. iOS4 is not backward compatible to the original iPhone/iPod touch, and there are some remaining bugs on the original iPhone that likely won't be fixed. This situation reflects poorly on HTC, it does not yet reflect poorly on Android, but it may in the future after more indepth research.
Again, an assertion in the RMS catechism, believed without question by freetards...I'll take professional software engineers doing their job against a bunch of amateurs doing what they fancy any day.
Absolutely untrue again. For one blatantly obvious example, when code is freely available, it can be sent through automated review and exploit tools such as Coverity that find potential flaws. You seem terribly misinformed or ideological. Much of the important bits of Linux are written by software engineers on the job, or in their free time, or by extremely experienced "amateurs" that by every measure match or rival "professional" counterparts.
That would be the closed source Blackberry.
But it isn't because Blackberry is closed source. I have no doubt the Blackberry OS would be incrementally better with public review of their code. However, BB source code has been reviewed by several government agencies, including likely the NSA when it was being considered for use by the President. There is extensive non-code documentation they have had to submit to large companies spelling out how the OS operates and why it is secure, before it was considered for implementation. Again this isn't ideal, but it is good evidence. Finally, I am sure there have been some BB exploits found, but I can't remember reading about any recently. So if publicized exploits are the ultimate judge for you, BB takes it.
With Android, you can just pull the SD card out of the device, and read it on your PC directly. That'll never be fixed. Access to data on the internal drive? Whoops
Again that is by design and I wouldn't have it any other way. If an app on Android needs to keep its data secure, the developer knows it must come over the air encrypted, and stay in volatile memory, or only be written to flash while encrypted. It doesn't matter that you can take the SD card out, there is nothing to read in that case.
iPhone Apps only have access to their own private data directory.
Doesn't matter. I'm talking about the ability to read the contents of supposedly encrypted iPhone data that is allowed to be unencrypted inflight by iOS using another computer.
when the app in question can only work on the Android... due to fundamental security mistakes on Android
The "app in question" works by design on Android. There is currently no confirmed data there were "security mistakes" in Android that allowed this behavior. The only question is to what extent the app was able to cloak itself and if that should be prevented.
huge numbers of security vulnerabilities on Android.
There weren't a "huge" number. There were 88. People who have used the tool that claimed these vulnerablities, and its categorization system, have said the actual number of real vulnerabilities are probably half that number, and less than half of those remaining are probably legitimately "serious."
When that tool was released for Linux originally, there were thousands of identified potential bugs. The actual ones were quickly quashed by the community. The fact that Android source is open, means many of these "bugs" will be quickly quashed also. In fact, the targeted build of Android wasn't the stock Google one, it was a customized HTC one. It remains to be seen how many of the actual serious bugs are present in the standard Android build.
Finally, since iOS source code isn't available for community review and testing like Linux and Android are, there are likely as many or more bugs in iOS. There have been plenty already inadvertently identified serious iOS bugs by enthusiasts and security researchers. The only mobile OS that has a solid claim to superior security is Blackberry. Apple has demonstrated their inadequacies, Android looks to have some inadequacies that will be quickly addressed.
Face it, Android is far more susceptible to malware than the iPhone.
That absolutely remains to be proven, and until today there was little evidence to support that assertion. The evidence released today is highly preliminary.
I never claimed there was a specific exploit for capturing and resending SMS on iPhone. But there are plenty of other exploits that are as big, or a bigger security concern, including unencrypted access to the file system containing user data.
As I said, access to SMS on permission was by design with Android. The only concerning thing about this episode, was that apparently the app could hide by not showing an icon, not showing up in the downloaded applications list, and possibly hiding in the process menu.
My ancient $50 WRT-54GL with DD-WRT does segregated VLANS with multiple SSIDs and independent passkeys. Running one now keyless for my neighbors, and WPA2 for me.
Doubtful, there are plenty of iPhone security holes that can be exploited. Having world readable SMS access (on permission) was by design for Android. And that is a design consideration I am still comfortable with.
Allwho?
Seriously, I've never been disappointed with T-Mobile in the South Central US. From the carrier rankings it seems they are good in the West also, and not so good on the East Coast.
Given that iPhones are limited to Edge on T-Mo's network, and that in general they are very friendly to unsupported phones (they helped me get an AT&T Blackberry working on their network), I'm surprised and disappointed they are acting like crybabies over this.
Everything else equal, a fixed wing drone will be more mechanically reliable than a manned helicopter, nothing to do with the drone, but with the realities of helicopter design.
Why does the FAA not allow drones in commercial airspace yet? Short answer is no one has took the time and money to develop one and get it certified. The longer answer is it depends on whether you are talking about piloted drones or autonomous drones.
There is a problem with coordination of pilot or autopilot to ATC requests, a pilot not physically being in the vehicle to make emergency avoidance maneuvers and trusting the autopilot to do it instead, and ensuring continuity of positive control of the autopilot or the wireless pilot interface. If a drone is going to be in airspace with passenger aircraft or over populated areas with heavy aircraft, the FAA wants to be damn confident it won't wreak havoc with highly automated commercial aircraft or Joe Bob in his Cessna.
Piloted military drones have a demonstrably higher accident rate. But I have no doubt after some teething pains and a lot of money, automated drones will have lower accident rates than piloted aircraft.
Used that as a generic term. I'm aware of the vague layout of US airspace. I was a student pilot in the early 1990's but I never got my ticket. Another commenter pointed out drones are not allowed in US airspace above 400 AGL or out of visual range of the operator (they can operate under RC rules).
My brother used to work as a commercial real estate appraiser. He talked to one of the first guys in Texas (perhaps the US) who retrofitted his Cessna with a viewport, a fancy DSLR, and a laptop. He flew around Houston and other cities in TX once a year or on demand, and took high res images that his software stitched together later. It may not be economical compared to a drone, but it was affordable, especially compared to satellite imagery at the time.
Were Google's drones just RC craft piloted by a certified pilot on the ground? I thought automated aircraft (no pilot) and RC craft flown by non-pilots were not allowed in controlled airspace in the USA.
Wow, thanks for the heads up. So many books and adoption sites say retired Greyhounds can make excellent pets for lazy people because they like to lay around and only need occasional sprints to work off their energy. It makes sense that without lots of socialization and training early in life, they could be difficult pets. I wonder how common it is to get an ill tempered one?
Rotide's quote was cute, but didn't get to the root of the matter. The real issue is when you have a DHCP server you are running on an unsecured wireless connection, and you don't even bother to set your SSID to something like (stayoffmywireless), then you are inviting people to use it. I specifically and intentionally have my wireless unsecured to allow neighbors to occasionally borrow it, though I have the speed significantly throttled so I don't turn into the neighborhood free ISP.
Crap...
I stupidly put angle brackets around the SSID I wanted to say - (donotconnecttome)