You can check the phone rates to call many phone numbers that are not a 900 type number. Most likely the account was used to call friends and associates.
Not all country codes are listed. 8816, for example. And if you don't do your research, you may arrive at an equivalent to 900 number, or destination with ludicrous termination charges.
The international rate sheets only show you the standard rates for dialing certain countries, but there are destinations that can be $10 to $25 per minute, and it's not necessarily obvious, or shown to you by those.
Morality does not require you to exhaust legal means first.
Morality would insist that the destructiveness and pain not just to yourself, but to society, created to achieve the just outcome be minimized.
The good of the whole outweights, even the desire for vengeance.
This would insist that you don't flaunt the law for light or transient purposes, as it harms society -- so yes, in general, morality means that legal and nondestructive means be exhausted first; otherwise there's no real respect for morality.
Most reasonably sharp thieves will quickly wipe your HD and install a "fresh" OS on your laptop after they take it from you.
Most reasonably sharp laptop anti-theft products tattoo themselves in the BIOS, or load in the master-boot record, so when you install a "fresh" OS;
that fresh OS install will be modified to include a bootstrap for the anti-theft software; upon first boot, the anti-theft software is quietly and undetectably
reinstalled, and the owner's configuration is reinstated.
It's pretty clear that the intent behind posting what he's posted was malicious and as such he could very well be liable for that.
Could be... but do you think the civil damage to the thief exceeds the thief's civil damage in physically injuring the original owner and making off with his property?
Before he can be liable for his actions, the thief's liability for his actions has to be exhausted too.
As for morality. I'm sorry, but this isn't moral. Moral would be referring it to the police and the CC issuer and insurance company and accepting that there isn't anything that can be done.
Which he did, and they failed to establish justice.
After you have exhausted options that are legal. Morality does not require that all your actions are legal.
Morality would permit you to take further actions to equalize injustice and discourage the mugger's activity.
Vigilantism is just not something which is acceptable in a civilized society.
So-called vigilantism is not what has happened here.
He has not committed any violent act, or attempted to physically restrain, arrest, injure, or kill the mugger in any way.
He has taken advantage of the fact, that his property has been put to a use without his authorization, and used that fact,
to make his property do something he has authorized, but the current illegal possessor does not approve of.
They're most likely either (1) disconnected numbers, (2) toll numbers that will rack up massive charges, OR
(3) Numbers that the thief sold innocent 3rd parties "cheap long distance minutes" to, through fraudulent schemes.
Don't engage yourself in placing international harassing phone calls to "create havoc" in random people's lives;
that would be you committing a crime.,
Both are very expensive and easily noticed by the public.
The defense method against those is the police and local guard units;
regardless of whether the computer is running Windows '95 or a modern network connected OS.
If I were in charge of Siri, I'd do the same thing.
And I suppose, if you were writing a web browser, it would upload screenshots of sites visited, to help your team ensure proper rendering?
I think the point is not that the recordings are useful (or not), but that it is invasive to record voices talking to Siri.
And especially since it is not well advertised -- the argument can easily be made that not everyone has necessarily given their consent (especially, if, for example, a friend uses your phone, and puts some searches to Siri, without acknowledging or agreeing to any Apple terms).
Apple should safeguard privacy by (1) limiting the number of samples taken to a small percentage, e.g. 1% of searches to Siri.
(2) Anonymizing the data immediately, not retaining a random number -- that way the recording could not be used against the user - no link at all to the device or user.
(3) Review all samples, and have a technician immediately delete/expunge any sample containing any hint of private or personal information, before reviewing the entire sample.
(4) Provide an assurance of security and safeguarding of the data.
Not only that but, it is a dangerous industrial solvent used in the production of heroin!
Ah! That explains where the addictiveness and serious negative consequences of Heroin come from -- it contains active byproducts of the ingredient DHMO
It only makes sense that DHMO should be treated as an illegal drug as well, and authorities should seize and destroy any DHMO that can be found in public, for sure.
There must be stiff and serious penalties for both dealing in or using DHMO-containing products,
with mandatory detox clinics for persons convicted of consuming or possessing DHMO or DHmo-containing products
According to the story the prosecutors were the ones who informed the defense counsel that they had found the emails, and said they stopped reading once they realized what they were.
It seems the system administrators' procedures were broken, as they allowed the lawyers to perform discovery and access to information in a scope outside their legal authority to do so.
It is the system administrator's duty to ensure that the scope of any search request is limited such that the data that can be retrieved will only be data that is legally allowed to be retrieved.
Sure, you start paying us like doctors, lawyers, and so on, and we'll talk about liability. But the reality is, the software industry would implode with the requirement for liability insurance, as the stuff we work on is far too complicated for even the brightest of programmers, and the pay is often times way too low
Programming errors and provably intended malice are different things.
Errors are understandable... the company developing the software has a duty to ffix errors, but the individual programmer has limited ability to 'own' the operaitonal characteristics of the result.
Now, if it can be proven the developer inserted malicious code specifically designed to commit a crime or abuse, then that developer has potential criminal and civil liability.
I will however say that I end up being hired to fix shitty PHP code more often than not. Kind of worrying... It's why I'm on my way out of this sorry excuse for a career. I don't recommend it.
It sounds challenging... then again rewrite may be better than fixing, as long as the pay is good....
Sooner or later, you're going to have to trust someone else's code. I guarantee you, whatever projects you work on, you're using someone else's code for something, and probably sight-unseen.
It's not everyone's code you can't trust.
It's only (1) the code you will actually distribute with your software, and (2) uncommon dependencies that are not part of widely used software packages.
And even then, you have to be able to trust the code of people working for you; e.g. the coders you hire.
If you can't do that, then you can't get anything done.
So you should check into their background, and make sure the people you hire to make your code are either under a good contract or surety bond that protects your interest, and effects some risk transfer by providing you the right to sue for damages, especially, in case of obvious or provable malice.
That way you align your worker's interest with yours, by ensuring that if they conduct an intentional abuse they are at risk.
I didn't mean to imply the move to Javascript/HTML will eliminate waste. But the recent problem there is programmer attitude, not the technology.
On the other hand with Java; the problem is the Sun JRE is a massive memory hog, that likes to allocate a big pool of memory, and because there's no real memory management in Java applications, it just keeps growing and growing, until eventually all allowed RAM is included in the java heap....
On the other hand... C and C++ applications with proper memory management were lean, and did not waste many gigabytes of memory in a useless memory allocation pool.
If they were using lots of memory, it was probably a bug in the program, or being used for something useful,
such as caching for improved performance.
Not only is the java heap junk space, as cold areas eventually accumulate over time, which is not used to improve performance.
But it expands to fill every niche of available memory over time, and Java performance is essentially guaranteed to degrade, once it's fully utilizing all system memory.
Normally the console is just fine, and the human has the problems.
It's necessary in the event of a disaster, to be able to do something like dump power from the phaser banks into the consoles to bring them back online.
How do you handle the must change password ever x days/months stuff? I have a spreadsheet with 100+ logins, no way that work in a safe deposit box easily.
By including the master password in the box, with the instructions for using it to unlock the digital keychain.
Besides, you need backups anyways
Can you sell them to the crew of the Enterprise? The number of exploding consoles they have...
The consoles are exploding, when they're at red alert, so they have engaged the battle short, or bypass of circuit protection,
to maintain the availability of critical control systems in spite of battle damage, during the lifethreatening situation.:)
I'd sure go with the party that voted FOR women's rights (Republicans 81-34 for women's right to vote , 1915), the party who pushed the Civil Rights Act through against the democrat filibuster, etc.
The fallacy of: once right, always right.
Just because a certain party has the better idea than the other once, doesn't mean they always have the most rational/moral/correct position.
IMO, at the current time, both parties' actions are horrible, and both of their agendas are not in the best interests of the country.
IMO, it's time to abolish Democrat and Republican parties, and give the spotlight to some new ideas.
Build a SAS array with the same number of SSDs and it'll murder the 15K HDDs any day.
You're making a different argument. The available SAS SSDs are much more expensive than their consumer-oriented SATA cousins.
The point is the 15K SAS drives win against a consumer level SSD,
both in terms of performance, and in terms of dollars per unit of performance as well.
Of course enterprise flash solutions (which include very expensive things like large amounts of DRAM cache, and lower-density SLC sells), are going to be more optimized --- there would be no point in spending the extra money if they didn't have an advantage - in general, the Enterprise flash offerings seek to provide a better Dollars to Unit of storage performance value, and Dollars to storage endurance (lowest likely to fail).
Whereas, the Consumer flash offerings seek to provide a better Dollars to Unit of storage raw bytes storage capacity value, and Dollars per unit of power consumption / consumer-perceived product coolness value.
He's not right. You are never going to get significantly lower throughput over time.
I have already performed my own experiments, and proven, that: yes, in fact, you do eventually get lower throughput over time, if your write throughput requirements are high enough, and you wait a long enough time, and this is attributed to the greater write endurance of Enterprise magnetic disks over consumer level high-density MLC flash.
Some more expensive kinds of flash, I firmly believe would fair much better; although I have not been able to afford or justify the cost to personally test the comparison in detail (as the flash storage media would be significantly worn after a long term high-write test).
You are encouraged to perform your own experiments, and show that you never get significantly lower throughput over time, and that the write endurance of the MLC flash is better than a few 15K RPM SCSI drives, for video editing.
But I don't think you will be able to do so, without misconfiguring it, picking particularly bad or cheap components, or applying a test methodology with errors.
No, not in a laptop. Video editing is mostly why I like having the speed.
15KRPM U320 SCSI disks perform extremely well with high-bandwidth non-random workloads.
SSDs have much faster seek times; however, there is the possibility of greater write latencies, and eventually lower throughput -- due to read - erase - program cycle.
This is especially the case with non-write-optimized MLC type flash.
Slashdot Mirror
You can check the phone rates to call many phone numbers that are not a 900 type number. Most likely the account was used to call friends and associates.
Not all country codes are listed. 8816, for example. And if you don't do your research, you may arrive at an equivalent to 900 number, or destination with ludicrous termination charges.
The international rate sheets only show you the standard rates for dialing certain countries, but there are destinations that can be $10 to $25 per minute, and it's not necessarily obvious, or shown to you by those.
Morality does not require you to exhaust legal means first.
Morality would insist that the destructiveness and pain not just to yourself, but to society, created to achieve the just outcome be minimized.
The good of the whole outweights, even the desire for vengeance.
This would insist that you don't flaunt the law for light or transient purposes, as it harms society -- so yes, in general, morality means that legal and nondestructive means be exhausted first; otherwise there's no real respect for morality.
Considering this particular summary is in regards to medical software, I certainly hope that's not the case.
It's very common that medical software would need network access.
To upload results to records server.
To upload test data to lab and other offsite servers.
To download and print lab test results.
To download updates to consumables, such as per-software-invokation license; verification against activation servers, download new billing code lists.
Transmit medical data to insurance companies and government.
Perform billing operations.
Download new versions of forms.
Backup data to central server at location, and off site locations.
Most reasonably sharp thieves will quickly wipe your HD and install a "fresh" OS on your laptop after they take it from you.
Most reasonably sharp laptop anti-theft products tattoo themselves in the BIOS, or load in the master-boot record, so when you install a "fresh" OS; that fresh OS install will be modified to include a bootstrap for the anti-theft software; upon first boot, the anti-theft software is quietly and undetectably reinstalled, and the owner's configuration is reinstated.
It's pretty clear that the intent behind posting what he's posted was malicious and as such he could very well be liable for that.
Could be... but do you think the civil damage to the thief exceeds the thief's civil damage in physically injuring the original owner and making off with his property?
Before he can be liable for his actions, the thief's liability for his actions has to be exhausted too.
As for morality. I'm sorry, but this isn't moral. Moral would be referring it to the police and the CC issuer and insurance company and accepting that there isn't anything that can be done.
Which he did, and they failed to establish justice.
After you have exhausted options that are legal. Morality does not require that all your actions are legal.
Morality would permit you to take further actions to equalize injustice and discourage the mugger's activity.
Vigilantism is just not something which is acceptable in a civilized society.
So-called vigilantism is not what has happened here.
He has not committed any violent act, or attempted to physically restrain, arrest, injure, or kill the mugger in any way.
He has taken advantage of the fact, that his property has been put to a use without his authorization, and used that fact, to make his property do something he has authorized, but the current illegal possessor does not approve of.
They're most likely either (1) disconnected numbers, (2) toll numbers that will rack up massive charges, OR (3) Numbers that the thief sold innocent 3rd parties "cheap long distance minutes" to, through fraudulent schemes.
Don't engage yourself in placing international harassing phone calls to "create havoc" in random people's lives; that would be you committing a crime. ,
Or against a guy with a tank and an RPG...
Both are very expensive and easily noticed by the public.
The defense method against those is the police and local guard units; regardless of whether the computer is running Windows '95 or a modern network connected OS.
If I were in charge of Siri, I'd do the same thing.
And I suppose, if you were writing a web browser, it would upload screenshots of sites visited, to help your team ensure proper rendering?
I think the point is not that the recordings are useful (or not), but that it is invasive to record voices talking to Siri.
And especially since it is not well advertised -- the argument can easily be made that not everyone has necessarily given their consent (especially, if, for example, a friend uses your phone, and puts some searches to Siri, without acknowledging or agreeing to any Apple terms).
Apple should safeguard privacy by (1) limiting the number of samples taken to a small percentage, e.g. 1% of searches to Siri.
(2) Anonymizing the data immediately, not retaining a random number -- that way the recording could not be used against the user - no link at all to the device or user.
(3) Review all samples, and have a technician immediately delete/expunge any sample containing any hint of private or personal information, before reviewing the entire sample.
(4) Provide an assurance of security and safeguarding of the data.
Escargot, por favor.
And be sure to cook thoroughly
Not only that but, it is a dangerous industrial solvent used in the production of heroin!
Ah! That explains where the addictiveness and serious negative consequences of Heroin come from -- it contains active byproducts of the ingredient DHMO
It only makes sense that DHMO should be treated as an illegal drug as well, and authorities should seize and destroy any DHMO that can be found in public, for sure.
There must be stiff and serious penalties for both dealing in or using DHMO-containing products,
with mandatory detox clinics for persons convicted of consuming or possessing DHMO or DHmo-containing products
According to the story the prosecutors were the ones who informed the defense counsel that they had found the emails, and said they stopped reading once they realized what they were.
It seems the system administrators' procedures were broken, as they allowed the lawyers to perform discovery and access to information in a scope outside their legal authority to do so.
It is the system administrator's duty to ensure that the scope of any search request is limited such that the data that can be retrieved will only be data that is legally allowed to be retrieved.
And well it should. I fully support the labeling of products that contain dangerous and addictive additives like DHMO.
Indeed... DHMO consumption is highly correlated to almost every disease and sickness known to man.
Just about everyone who eventually gets sick or dies has consumed DHMO.
I'm afraid the warning alone might never be effective. A mandatory recall of DHMO containing products seems the only wise idea.
Sure, you start paying us like doctors, lawyers, and so on, and we'll talk about liability. But the reality is, the software industry would implode with the requirement for liability insurance, as the stuff we work on is far too complicated for even the brightest of programmers, and the pay is often times way too low
Programming errors and provably intended malice are different things.
Errors are understandable... the company developing the software has a duty to ffix errors, but the individual programmer has limited ability to 'own' the operaitonal characteristics of the result.
Now, if it can be proven the developer inserted malicious code specifically designed to commit a crime or abuse, then that developer has potential criminal and civil liability.
I will however say that I end up being hired to fix shitty PHP code more often than not. Kind of worrying... It's why I'm on my way out of this sorry excuse for a career. I don't recommend it.
It sounds challenging... then again rewrite may be better than fixing, as long as the pay is good....
Sooner or later, you're going to have to trust someone else's code. I guarantee you, whatever projects you work on, you're using someone else's code for something, and probably sight-unseen.
It's not everyone's code you can't trust.
It's only (1) the code you will actually distribute with your software, and (2) uncommon dependencies that are not part of widely used software packages.
And even then, you have to be able to trust the code of people working for you; e.g. the coders you hire. If you can't do that, then you can't get anything done.
So you should check into their background, and make sure the people you hire to make your code are either under a good contract or surety bond that protects your interest, and effects some risk transfer by providing you the right to sue for damages, especially, in case of obvious or provable malice.
That way you align your worker's interest with yours, by ensuring that if they conduct an intentional abuse they are at risk.
I didn't mean to imply the move to Javascript/HTML will eliminate waste. But the recent problem there is programmer attitude, not the technology.
On the other hand with Java; the problem is the Sun JRE is a massive memory hog, that likes to allocate a big pool of memory, and because there's no real memory management in Java applications, it just keeps growing and growing, until eventually all allowed RAM is included in the java heap....
On the other hand... C and C++ applications with proper memory management were lean, and did not waste many gigabytes of memory in a useless memory allocation pool.
If they were using lots of memory, it was probably a bug in the program, or being used for something useful, such as caching for improved performance.
Not only is the java heap junk space, as cold areas eventually accumulate over time, which is not used to improve performance. But it expands to fill every niche of available memory over time, and Java performance is essentially guaranteed to degrade, once it's fully utilizing all system memory.
Normally the console is just fine, and the human has the problems.
It's necessary in the event of a disaster, to be able to do something like dump power from the phaser banks into the consoles to bring them back online.
How do you handle the must change password ever x days/months stuff? I have a spreadsheet with 100+ logins, no way that work in a safe deposit box easily.
By including the master password in the box, with the instructions for using it to unlock the digital keychain. Besides, you need backups anyways
except for code that isn't mine to relicense as GPL
I'd just open it all up, with appropriate disclaimers, just because of the fact that the information ought to be free, and you cannot sue a corpse
Can you sell them to the crew of the Enterprise? The number of exploding consoles they have...
The consoles are exploding, when they're at red alert, so they have engaged the battle short, or bypass of circuit protection, to maintain the availability of critical control systems in spite of battle damage, during the lifethreatening situation. :)
I'd sure go with the party that voted FOR women's rights (Republicans 81-34 for women's right to vote , 1915), the party who pushed the Civil Rights Act through against the democrat filibuster, etc.
The fallacy of: once right, always right.
Just because a certain party has the better idea than the other once, doesn't mean they always have the most rational/moral/correct position.
IMO, at the current time, both parties' actions are horrible, and both of their agendas are not in the best interests of the country.
IMO, it's time to abolish Democrat and Republican parties, and give the spotlight to some new ideas.
Build a SAS array with the same number of SSDs and it'll murder the 15K HDDs any day.
You're making a different argument. The available SAS SSDs are much more expensive than their consumer-oriented SATA cousins.
The point is the 15K SAS drives win against a consumer level SSD, both in terms of performance, and in terms of dollars per unit of performance as well.
Of course enterprise flash solutions (which include very expensive things like large amounts of DRAM cache, and lower-density SLC sells), are going to be more optimized --- there would be no point in spending the extra money if they didn't have an advantage - in general, the Enterprise flash offerings seek to provide a better Dollars to Unit of storage performance value, and Dollars to storage endurance (lowest likely to fail).
Whereas, the Consumer flash offerings seek to provide a better Dollars to Unit of storage raw bytes storage capacity value, and Dollars per unit of power consumption / consumer-perceived product coolness value.
He's not right. You are never going to get significantly lower throughput over time.
I have already performed my own experiments, and proven, that: yes, in fact, you do eventually get lower throughput over time, if your write throughput requirements are high enough, and you wait a long enough time, and this is attributed to the greater write endurance of Enterprise magnetic disks over consumer level high-density MLC flash.
Some more expensive kinds of flash, I firmly believe would fair much better; although I have not been able to afford or justify the cost to personally test the comparison in detail (as the flash storage media would be significantly worn after a long term high-write test).
You are encouraged to perform your own experiments, and show that you never get significantly lower throughput over time, and that the write endurance of the MLC flash is better than a few 15K RPM SCSI drives, for video editing.
But I don't think you will be able to do so, without misconfiguring it, picking particularly bad or cheap components, or applying a test methodology with errors.
Java
That one word explains the quad core 8gb of RAM requirement.
End user computing experience moved away from java, and onto HTML5/Javascript
No, not in a laptop. Video editing is mostly why I like having the speed.
15KRPM U320 SCSI disks perform extremely well with high-bandwidth non-random workloads.
SSDs have much faster seek times; however, there is the possibility of greater write latencies, and eventually lower throughput -- due to read - erase - program cycle.
This is especially the case with non-write-optimized MLC type flash.