Manage to patent an irrational number and then sue everyone because math shows that everyone have everything there if you dig enough. Then take down the patent system as even them are covered by your patent. And then we can live happily ever after.
If is specifically about android and dalvik apps you won't have available all hardware power for your app. I would go to native apps either in Android or some other linux based OS for that kind of things, and of course, native apps for those OSs (development could be done in QT/QML for most of them, porting between them should not be so hard)
Well, if you call monitor something wireless, that is not rectangular and dedicated but fitting in existing surfaces, that gathers information (not just touchscreen, maybe other kind of sensors too), and probably should have some level of transparency, then yes. But probably will get a new shiny name like happened with smartphone or ultrabook.
As someone else already pointed out, the problem started that way, the 1.0.0.0/8 was in used by one of those organizations/reserved, and in 2009 or 2010 was given to APNIC to mitigate the ipv4 exhaustion problem, so it started to be "someone's else public IP". So something that wasn't inherently wrong became wrong, because happened things that were outside your control.
Ok, that make sense. Is not right, but at least didn't looked as a very bad idea some time ago, as some of those low ranges looked like internal networks for big companies (an actual list). But using the standard, meant for internet networks ranges, is more future proof.
There are a lot of things that could go very wrong using public IPs (that are being used actually) for internal networks. You eventually could want to access or send mail to one of those public IPs. Or if you have an internal site, the public IP could be used to deploy a fake site so if you try to connect from outside (i.e. dropped vpn connection) or inside (i.e. proxy to access outside). Or you have a firewall that enables certain internal IPs to access a resource that could be accessed from outside too. This are just a few easy examples, but things usually go wrong in more imaginative ways.
Yes, it could be managed securely, but why take the risk if the right way to do things is just less complex than messing in that way with everything?
The bank used public IP addresses (existing, used elsewhere) for their internal network? The one that designed that should be considered a bigger security threat that any current cyberattack.
The fix is in the wrong place. Is basically broken hardware, something that run as root/admin (intended or not) could brick them at any time. Is a problem just waiting to happen, avoiding them is the right solution.
Targetting a bunch of mobile platforms at once is one of the biggest advantages of QT/QML. Having a key app as Calligra in all of them not just gives base to the new mobile platforms, but also extend the ecosystem to Android, as a lot of people will have the libraries installed, making more attractive to develop for it.
Shit and black swans happens. And probably would had been mapped every grain of sand in the solar system with the money "invested" in wars which real justification is just profit of a few..
Is difficult to hit a specific small nation. And more important, is very difficult to hit a city, even or specially a big one,, with rich enough people live in it, to make governments worry about it. Odds are high that will strike ocean (and probably several did in the last decades, if weren't bigger than recent Russia ones) or deserted land.
But the problem are big ones. With them don't matter the exact point where it hits. And if you didn't invested to detect early or advance enough tech to be able to do something, will be nothing that you can do to avoid it.
If a meteor strikes a big city, then USA could start the War on Space. Will still be madness, but at least this time won't be thousands of civil casualties because of it.
Seems that anyone can reset your password knowing your email and birthdate for the ones not using the two-factor authentication. And that option is available in just a few countries.
Hopely it gets fixed in very short time or could get a massive impact in all the world.
Do local hackers have the right to kill enemy citizens? Would be right and without retaliation if the attacked country send a missile to that local hacker house? You lose the right when you make it one sided.
What about nations with shady definitions of hacking, digital rights and digital property? You could be targetted to kill/kidnap/jail just because a web page you visited had a funny javascript. In their own soil could send people to jail for decades for that kind of things, but who cares about people in other countries?
Killing Reader didn't kill RSS. But killed all the ecosystem around it, both from apps and for the way you used it. Why i should do an alternative app that makes use of Keep if they could end it tomorrow? Why i use it to store notes if they could not be there tomorrow, and all that that was put there because that particular way of access is not there anymore?
In any case, either with Drive or Takeout, you don't lose your data, but it lose a part of its value without the "right" way to access it, all of it. A bit more "bening" shutdown was Wave, that if well was discontinued but open sourced the server so you can continue using it in the same way elsewhere.
Thats why should be a non-profit organization, not a for-profit company. No money nor power must be involved if you want fairness, else even if the organization goals are good people wanting power/money will try to get there to take decisions to benefit them or 3rd parties that will benefit them. Look at what happens at governments, the "voice of the people", or other organizations where money or some kind of power is involved.
A lot of organizations (ISOC, W3C, ICANN, *NIC, ITU, etc) could have commercial/political interest groups affecting decisions.
EFF could be a good example of such organization, or at least as member with weight of a bigger organization with that goal (that should include too i.e. Mozilla and Wikimedia Foundations).
Don't point just to the visible head. Probably were more people involved in that decision/actions and that are still active (or even still profitting from other, more recent, conflicts).
Preemptively not training for doing it would be better. If someone gives you a weapon and tells to you go outside and kill some, the option you have is to stop him before it does some damage, reeducate telling that the first person was wrong, and put in jail the first person. Or just live with the fact that a lot of people will be killed and the first person will get a medal for that, and surely will move more people to kill, that is the usual way to do things, and that it will keep happening if the other alternatives are not taken.
You are giving the reason why American police, and who trained/put them into that way, should be put right now in jail as preemptive punishment. They will kill innocent people, sooner or later, phone jokes or not, things like this or this will continue to happen,
And with guns practically mandated to normal citizens, social engineering could be a lethal weapon too, but again, the one shooting would still be the real killer.
What is that thing "truth" that you are talking about? Something that goes with unicorns and elves in fairy tales? If you publish something straight taken from wikileaks, but denied from the government, who will get the libel fines?
Manage to patent an irrational number and then sue everyone because math shows that everyone have everything there if you dig enough. Then take down the patent system as even them are covered by your patent. And then we can live happily ever after.
Just wait for government regulations requiring to be secure enough for their promoted cyberwar. There costs of everything will go up.
If is specifically about android and dalvik apps you won't have available all hardware power for your app. I would go to native apps either in Android or some other linux based OS for that kind of things, and of course, native apps for those OSs (development could be done in QT/QML for most of them, porting between them should not be so hard)
Well, if you call monitor something wireless, that is not rectangular and dedicated but fitting in existing surfaces, that gathers information (not just touchscreen, maybe other kind of sensors too), and probably should have some level of transparency, then yes. But probably will get a new shiny name like happened with smartphone or ultrabook.
As someone else already pointed out, the problem started that way, the 1.0.0.0/8 was in used by one of those organizations/reserved, and in 2009 or 2010 was given to APNIC to mitigate the ipv4 exhaustion problem, so it started to be "someone's else public IP". So something that wasn't inherently wrong became wrong, because happened things that were outside your control.
The next generation of patent trolls could make this an exception to that rule.
Ok, that make sense. Is not right, but at least didn't looked as a very bad idea some time ago, as some of those low ranges looked like internal networks for big companies (an actual list). But using the standard, meant for internet networks ranges, is more future proof.
There are a lot of things that could go very wrong using public IPs (that are being used actually) for internal networks. You eventually could want to access or send mail to one of those public IPs. Or if you have an internal site, the public IP could be used to deploy a fake site so if you try to connect from outside (i.e. dropped vpn connection) or inside (i.e. proxy to access outside). Or you have a firewall that enables certain internal IPs to access a resource that could be accessed from outside too. This are just a few easy examples, but things usually go wrong in more imaginative ways.
Yes, it could be managed securely, but why take the risk if the right way to do things is just less complex than messing in that way with everything?
The bank used public IP addresses (existing, used elsewhere) for their internal network? The one that designed that should be considered a bigger security threat that any current cyberattack.
BTW, the CNN editorial "Why cyber attacks threaten our freedom" is another piece of art of more or less the same magnitude. I'd say that is on a par with this one
The fix is in the wrong place. Is basically broken hardware, something that run as root/admin (intended or not) could brick them at any time. Is a problem just waiting to happen, avoiding them is the right solution.
Targetting a bunch of mobile platforms at once is one of the biggest advantages of QT/QML. Having a key app as Calligra in all of them not just gives base to the new mobile platforms, but also extend the ecosystem to Android, as a lot of people will have the libraries installed, making more attractive to develop for it.
Shit and black swans happens. And probably would had been mapped every grain of sand in the solar system with the money "invested" in wars which real justification is just profit of a few..
Is difficult to hit a specific small nation. And more important, is very difficult to hit a city, even or specially a big one,, with rich enough people live in it, to make governments worry about it. Odds are high that will strike ocean (and probably several did in the last decades, if weren't bigger than recent Russia ones) or deserted land.
But the problem are big ones. With them don't matter the exact point where it hits. And if you didn't invested to detect early or advance enough tech to be able to do something, will be nothing that you can do to avoid it.
If a meteor strikes a big city, then USA could start the War on Space. Will still be madness, but at least this time won't be thousands of civil casualties because of it.
Seems that anyone can reset your password knowing your email and birthdate for the ones not using the two-factor authentication. And that option is available in just a few countries.
Hopely it gets fixed in very short time or could get a massive impact in all the world.
I put all this money in the bank and don't have it anymore, at least for a long time. In the short term, is unprofitable.
Do local hackers have the right to kill enemy citizens? Would be right and without retaliation if the attacked country send a missile to that local hacker house? You lose the right when you make it one sided.
So if any country of the world have a computer hacked from an US IP is right to launch a bomb there and the US won't retaliate?
What about nations with shady definitions of hacking, digital rights and digital property? You could be targetted to kill/kidnap/jail just because a web page you visited had a funny javascript. In their own soil could send people to jail for decades for that kind of things, but who cares about people in other countries?
Killing Reader didn't kill RSS. But killed all the ecosystem around it, both from apps and for the way you used it. Why i should do an alternative app that makes use of Keep if they could end it tomorrow? Why i use it to store notes if they could not be there tomorrow, and all that that was put there because that particular way of access is not there anymore?
In any case, either with Drive or Takeout, you don't lose your data, but it lose a part of its value without the "right" way to access it, all of it. A bit more "bening" shutdown was Wave, that if well was discontinued but open sourced the server so you can continue using it in the same way elsewhere.
Thats why should be a non-profit organization, not a for-profit company. No money nor power must be involved if you want fairness, else even if the organization goals are good people wanting power/money will try to get there to take decisions to benefit them or 3rd parties that will benefit them. Look at what happens at governments, the "voice of the people", or other organizations where money or some kind of power is involved.
A lot of organizations (ISOC, W3C, ICANN, *NIC, ITU, etc) could have commercial/political interest groups affecting decisions.
EFF could be a good example of such organization, or at least as member with weight of a bigger organization with that goal (that should include too i.e. Mozilla and Wikimedia Foundations).
Don't point just to the visible head. Probably were more people involved in that decision/actions and that are still active (or even still profitting from other, more recent, conflicts).
Preemptively not training for doing it would be better. If someone gives you a weapon and tells to you go outside and kill some, the option you have is to stop him before it does some damage, reeducate telling that the first person was wrong, and put in jail the first person. Or just live with the fact that a lot of people will be killed and the first person will get a medal for that, and surely will move more people to kill, that is the usual way to do things, and that it will keep happening if the other alternatives are not taken.
You are giving the reason why American police, and who trained/put them into that way, should be put right now in jail as preemptive punishment. They will kill innocent people, sooner or later, phone jokes or not, things like this or this will continue to happen,
And with guns practically mandated to normal citizens, social engineering could be a lethal weapon too, but again, the one shooting would still be the real killer.
What is that thing "truth" that you are talking about? Something that goes with unicorns and elves in fairy tales? If you publish something straight taken from wikileaks, but denied from the government, who will get the libel fines?