Emails don't typically traverse lots of different servers... They usually go direct from servers controlled by A, to servers controlled by B... The only exception is when there are third party filtering services in between which have been explicitly employed by either party.
Also as you said the logs will just show that an email was sent from A to B, it won't show the content so it would be trivially easy to create a fake copy of the content using the legitimate headers.
And the other side could dig up the original email (if it's within their retention policy) and say "HEY LOOK". Obviously one side is tampering evidence, and that's typically not worth the risk. Or if there was no email, the other side could dig up the logs and say "HEY LOOK, NEVER HAPPENED".
Long retention policies are good if you have nothing to hide. Short retention policies are good if you want to hide evidence.
Short retention policies are also good if you want to avoid lengthy and costly bullshit in discovery processes (especially if you're not even a direct party to a suit), but having a decent backup/archive scheme and making shit easily retrievable solves this problem.
Right, but the shipping estimate page will still list the maximum. I often get things in 1 day despite getting 2-day shipping. Newegg will get shit to me in 1 or 2 days despite it being 3-5 fays, or 7-10 days shipping.
You're wrong about inflammable and flammable. While inflammable is older, dating back to the late 16th century, flammable is almost 2 centuries old, well in advance of either Yoda, Slashdotters, or Fleshlights ( I hope I got the order of origination right for those last 3 ).
But, soft, for the common speech doth truly amend as the seasons turn. Else why wouldst it be that in uncounted years hence our distant progeny not speakest as ye and me?
Yoda is from time long ago, in a galaxy far, far, away. Besides, it doesn't matter because the use of the word "like" is there for comparison - humans today can roar like dinosaurs even though they no longer exist. (We know how they sound because Jesus rode them around 200 years ago.)
Yes, language changes, but some changes are good, some are neutral, and some are bad.
Modems were x baud/second, so the K or M meant 1000 or 1000000. If you talked about a modem in x bits/second, then you were supposed to use the binary 1024 or 1048576.
You're committing the classic mistake of not knowing when or why to use 1024. You're just wrong.
Nothing is a red herring. Engineers built early storage devices on tracks, cylinders, sectors, etc., and specced them out to have X tracks, Y sectors, etc., and said you could hold Z bits per sector.
Marketing, and fools like you, intentionally/ignorantly said "Well I have a total of 8000 sectors, and each sector holds Z bits (and W data bits), so that's Z * 8000 bits, or Z*8 Kbits!". The error is failing to use the proper, binary-based scalar (1024 instead of 1000) when the term involves bits or bytes, binary data.
It's the same mistake every time from people like you, and you will never get it. Either because you're stupid, or because you don't want to admit that you were wrong at one point in your life. There is no debating the "correctness" of it, or "when" you should use 1024 or 1000. If a terms units contain bits ("b") or bytes (B), or any other binary measure, shorthand notation of scalar multiples (K/k, M, G, etc.) MUST represent 1024, 1048576, etc. Even if you don't like the reasoning behind the rule, or you feel butthurt because you made a mistake one time, it's still correct. No amount of pointing to others who do it incorrectly (marketing people who sell hard drives) will make you correct.
For example, communication protocols (like this one) are specified in powers-of-10 units because they're based on measuring wireless frequencies, which are measured in powers-of-10 hertz -- in this case, I'm sure that 1.5 Gbps means 1.5E9 bits per second. A 14.4 kbps modem transmitted 14,400 bits per second. A T-1 line transmits 1.54 Mbps, meaning 1,540,000 bits per second -- and note that framing and other overhead bits mean that you can't just divide by 8 to get bytes per second.
You, like many modem vendors who labelled their products at X kbps, instead of X k, are just wrong. You're confusing BAUD with BITS. A 56k modem is 56,000 BAUD.
And yes, floppies were a cluster fuck. All of storage was, because they all wanted to advertise more space. 1 KB was 1024 bytes, and everyone knew it. But a MB was something new to a lot of people, so they thought they could get away with calling 1000 KB 1 MB. Many of the early storage devices weren't actually specced in a number of bytes, anyway, they were specced to tracks, sectors, etc. which marketing goons confused/abused, take your pick.
While GoogleDocs version lacks a lot of features Excel provides, it's FILTER function, and it's ability to process whole columns, as opposed to just ranges, makes certain operations so much more elegant, extensible and maintainable. While nowhere near close in a head-on, feature-for-feature comparison, there are certainly use-cases where Google's version is more useful than Excel.
So basically you don't know how to use Excel? Excel functions absolutely can work on an entire column.
Just because we can't know a position and vector of a particle now doesn't mean we won't ever be able to. Furthermore, that doesn't change the fact that the numbers aren't random, even if they're unknown and unpredictable.
If we live in a deterministic Universe, and I believe we do, there is nothing that is random.
The CA system is set up so that you can be reasonably sure that the host you're connected to is who they say they are. You "trust" that a certificate they present is legitimate because it is cryptographically signed by a CA. You trust the CA because you have a root list of CAs to trust, typically fed to you by MS.
The problem with the CA system is the fact that the CAs themselves are untrustworthy. They don't do their due diligence in verifying hosts they issue certificates to, safeguarding their private keys, or revoking certificates when keys get stolen. The entire idea is insecure because users want shit to work transparently, and CAs want to do shit as cheaply as possible.
You can have all the logs and auditing that you want, but when some soccer mom can't buy something on Amazon, your system has failed. And when some CA fucks up and nobody knows because no one is actually monitoring those logs, your system has failed. And if you DO have dedicated groups that monitor logs and do audits, it becomes the same fucking game of knowing which monitoring group to trust, how far to trust them, etc. 99.9999% of users will just be confused, and will think their next computer crash has something to do with the internet hacks Wolf Blitzer told them about.
The only way to trust a host is to verify their identity yourself. And if you're going to go and fucking verify the trustworthiness of CAs via analyzing their logs yourself, you may as well just verify the trustworthiness of individual sites yourself. Call up Amazon and ask them about their certificate. Maybe they should print it on the back of all their packing slips.
The telecommuter isn't taking up a cubicle. He doesn't clog up the toilet. He won't have a heart attack in the office. He doesn't need a parking space. He doesn't suck back gallons of coffee. He doesn't add to the fire code limit of how many sardines you can pack into the can.
Physical presence comes with a cost and presents a liability. Given 2 equal employees I'd axe the one at the office and keep the one at home.
If the lack of a physical presence is detrimental to your business in any way (people don't know how shit works, people don't know who to go to, etc.), then the two weren't really equal, and you're doing it wrong.
There's no way to guarantee you won't be in the.15% whose vasectomies fail, so saying it's 100% effective is misleading. Also, there are a handful of cases of spontaneous healing of the gap in that.15%, so it's not even 100% for correctly implemented vasectomies.
It's extremely effective. There's even a dedicated group of people in the US and other western countries today that use such methods (organized through the internet, of course) and measure their own sperm counts and report results. Some of the more dedicated actually manually push their testicles back into their abdominal cavity, either over night or just keeping them there 24/7.
Both of which can be trivially faked, but then lots of legal matters hinge on something as ridiculously arbitrary as a signature - a random mark on a piece of paper which is even easier to fake.
Trivially faked and trivially verified. Send subpoenas to whoever owns the various servers the email passed through. You won't get the body of the email, but you will get logs out the ass.
1: Pop open case. 2: Remove Drive. 3: ??? 4: Profit (through continued employment).
?
You only want 1 copy of the data, so the original is the backup. Just convince the nearest PHB that it's a waste of your time and their money to wipe drives. If the machines are going to be repurposed or sold, it's cheaper and easier to buy new drives, or sell them without the drive. As for the backup, same deal - cheaper and easier to store a bunch of HDDs in anti static bags in a box somewhere. Safer than storing their data on a live backup device anyway. And if you need immediate, constant access to that data - why are you killing the machines in the first place?
But if you have to do it their way, get Acronis. It lets you backup an entire drive to a network location from a bootable cd / usb thingamajig. It works with like, every fucking SATA / RAID controller there is, and if it doesn't, you get official support for building a BartPE disc that includes those drivers so you can get your shit on. You can even do a full drive backup from within windows. It's pretty fast, too. You can encrypt backups with AES-256, and you can browse through the backups with any machine that has Acronis installed. You could also of course dump the full contents of the backup into a 7zip archive or some other format if you wanted to not depend on Acronis's file format and software in the future.
Just make as many copies of the disc as you have network ports in whatever dark corner you'll be working in, line em all up, tell them to go, then play Minecraft until it's time to switch out machines. I think the bootable cd also has basic 0 wiping tools, as well, but I don't know for sure.
When you build something essential to the operation of a must-have, you'd better believe the government is going to come knocking.
I don't know about you, but the last time I looked at CISCO's products and services, they were:
Vaguely defined Overpriced Intentionally confusing
The trifecta of an aging tech company that focuses more on its past reputation that its forward progress. CISCO used to be the guys who made routers, and they gave us a backwards ACL notation system that everyone uses (because they got a certificate in it). Today? They run ads about how they are able to violate causality - a school in the US and a school in China are video conferencing with no lag. In the middle of the day. At both locations. I guess they still sell routers, too, but why pay their ridiculous prices when you can get the same hardware elsewhere, or hell, build it your fucking self, for cheaper?
Your entire posts shows that you have no idea what you're talking about. SI doesn't get to claim letters and symbols for its own exclusive use. It doesn't matter that K was in use. SI has no authority over anything. Furthermore, the use of 1024 instead of 1000 has an intrinsic practical advantage in computer science - shit is binary and we care about permutations, so we like powers of 2. They're infinitely more useful.
And SI scalars are scalars. They are not prefixes even though they call them that - they can be, and are, inserted ANYWHERE in a computation or algebraic statement. They are scalar multiples. If you want to bitch about K being lower case, fine - just go ahead and first concede that KB isn't confusing at all because K isn't an SI prefix. And then ignore M and m for meter, milli, and mega.
As for the 1, "according to whom?"? According to SI! Read their fucking shit and learn what a mass fraction is. It's absurd.
Again, SEVERELY LIMITING. If an employee is writing down every SSN that comes in, it will be extremely easy to figure out which employee is the one stealing ID's. Not to mention it'll be pretty obvious to supervisors walking around the office when they see someone writing down the SSN's. Furthermore, the number of ID's they can steal in a given month is minuscule in comparison.
Not limiting at all, because the way it is right now every account lookup is logged already.
None of those employees need to be able to read existing entries though. All they need is a field where the rep asks you for your SSN, they type it in and hit a button, and it matches it against the database. If for some reason it wasn't matching, and they needed to actually view the entry, they would request a manager to unlock the one record for them temporarily.
This would severely limit the amount of information they had access to.
1) Please note what time it is. 2) Read your post again. 3) When you realize your folly, note the time again. 4) Please reply with the amount of time it took you to realize that if the employee KEYS IN the SSN YOU PROVIDE to match against, THEY KNOW the one you gave during account setup and the one you gave during the support call when they match. If they don't match, they know the one you gave during the support call and your solution is to UNLOCK THAT SINGLE ENTRY for them to view, so they know both anyway.
The proper thing to do is to NOT FUCKING STORE SSNs. But that would make selling the information and doing credit checks much more troublesome. So they don't give a shit. At lot of places at least let you set up a PIN number that you can use when talking to a customer support peon (as opposed to the last 4 of your social), at least.
What can I do with 30 GiB/s? I'm trying to figure that out, give me some ideas.
Nothing, because a "GiB" is not a thing. 1 GB is 1073741824 Bytes. It always has been, and it always will be. Note that the "G" is not an SI scalar. No one ever said it was, and there's no reason it needs to be. Note that there is never any confusion because you always see the G right next to the B. Indeed, there is no "K", "M", "G", etc.; there is a "KB", "Kb", and so on. Note that calling 1 GB 1000000000 Bytes and 1 "GiB" 1073741824 Bytes - the proposed solution to the ambiguity - is what actually causes the ambiguity. Note that the SI units, prefixes, etc. themselves have all sorts of ambiguity built in. T is Tesla. Or is it tera? K is Kelvin, or is it kilo? Gy is Giga...something? Oh no, it's just grays! And that's being generous - if you look at practical usage, where people and fields use units and variables of their own, or don't always use the proper case (or its use is indistinguishable), it's far worse. And then there's the mass fraction. Yup, kg/kg. The symbol for this unit? 1. That's right. The digit 1. Anytime you divide a mass by a mass you better add a superfluous 1 in there otherwise you're not compliant with the SI quackery!
It's "flammable" and "non-flammable" all over again. These are not words. These have been thrust upon the language like a/.er on a Yoda Fleshlight. The correct words are "inflammable" and "non-inflammable". The addition of "flammable" and "non-flammable" adds ambiguity and confusion where there was none. It has also killed people.
Neither of these are instances of language "evolving", so please kindly fuck off before you post that horse shit. The sole purpose of language is communication. When you introduce ambiguity and confusion, you are damaging the language.
Terahertz radiation is non-ionizing, unlike say X-Rays. This type of radiation is used in things like bomb detectors and to inspect explosives and other unstable compounds because it can penetrate a few millimeters but does not break down molecular bonds.
Non ionizing != safe. There's a reason there's a little grill on your microwave door window.
That "study" only dealt with the correctness of the statistics applied to the data, it did not validate the data itself. The data itself has been manually manipulated, and consists of disparate sets using different measurement methods, different amounts of accuracy, reliability, etc.
Yeah, this is off topic, but when dealing with such a meaningless story, I figure I cannot do any more harm
I am interested in learning about coding in a LAMP environment. My thought is I'd like to find a hosting partner (low cost) that has the infrastructure already. I want to do some of the configuration, and get started coding a PHP hello world, then work up to some more advanced topics involving mysql database access.
1) Who would be a good hosting partner for this? Not looking for free, but not looking to spend $100/month either. 2) Any good tutorials for basic configuration, sercurity considerations? PHP tutorials?
Set it up yourself in a VM, then when you're ready to make it actually do shit, export it to Amazon C3 or whatever they call it now.
Before the inevitable ridicule, the reason the wine is swirled is to get the aroma into the air inside the glass, enhancing flavor perception. As an analogy imagine taking a shit. You plop one, it stinks real bad for a while but then it gets better. Then you drop another, this stirs up the water and brings the stink back again for a bit.
Doesn't change the facts:
Wine snobs suck. The movie Sideways sucks. Wine snobs are just closet alcoholics. Wine snobbery comes with oaky notes and hints of bullshit.
Slashdot Mirror
Emails don't typically traverse lots of different servers...
They usually go direct from servers controlled by A, to servers controlled by B... The only exception is when there are third party filtering services in between which have been explicitly employed by either party.
Also as you said the logs will just show that an email was sent from A to B, it won't show the content so it would be trivially easy to create a fake copy of the content using the legitimate headers.
And the other side could dig up the original email (if it's within their retention policy) and say "HEY LOOK". Obviously one side is tampering evidence, and that's typically not worth the risk.
Or if there was no email, the other side could dig up the logs and say "HEY LOOK, NEVER HAPPENED".
Long retention policies are good if you have nothing to hide.
Short retention policies are good if you want to hide evidence.
Short retention policies are also good if you want to avoid lengthy and costly bullshit in discovery processes (especially if you're not even a direct party to a suit), but having a decent backup/archive scheme and making shit easily retrievable solves this problem.
Right, but the shipping estimate page will still list the maximum.
I often get things in 1 day despite getting 2-day shipping.
Newegg will get shit to me in 1 or 2 days despite it being 3-5 fays, or 7-10 days shipping.
You're wrong about inflammable and flammable. While inflammable is older, dating back to the late 16th century, flammable is almost 2 centuries old, well in advance of either Yoda, Slashdotters, or Fleshlights ( I hope I got the order of origination right for those last 3 ).
But, soft, for the common speech doth truly amend as the seasons turn. Else why wouldst it be that in uncounted years hence our distant progeny not speakest as ye and me?
Yoda is from time long ago, in a galaxy far, far, away.
Besides, it doesn't matter because the use of the word "like" is there for comparison - humans today can roar like dinosaurs even though they no longer exist. (We know how they sound because Jesus rode them around 200 years ago.)
Yes, language changes, but some changes are good, some are neutral, and some are bad.
Modems were x baud/second, so the K or M meant 1000 or 1000000.
If you talked about a modem in x bits/second, then you were supposed to use the binary 1024 or 1048576.
You're committing the classic mistake of not knowing when or why to use 1024. You're just wrong.
Nothing is a red herring. Engineers built early storage devices on tracks, cylinders, sectors, etc., and specced them out to have X tracks, Y sectors, etc., and said you could hold Z bits per sector.
Marketing, and fools like you, intentionally/ignorantly said "Well I have a total of 8000 sectors, and each sector holds Z bits (and W data bits), so that's Z * 8000 bits, or Z*8 Kbits!". The error is failing to use the proper, binary-based scalar (1024 instead of 1000) when the term involves bits or bytes, binary data.
It's the same mistake every time from people like you, and you will never get it. Either because you're stupid, or because you don't want to admit that you were wrong at one point in your life. There is no debating the "correctness" of it, or "when" you should use 1024 or 1000.
If a terms units contain bits ("b") or bytes (B), or any other binary measure, shorthand notation of scalar multiples (K/k, M, G, etc.) MUST represent 1024, 1048576, etc. Even if you don't like the reasoning behind the rule, or you feel butthurt because you made a mistake one time, it's still correct. No amount of pointing to others who do it incorrectly (marketing people who sell hard drives) will make you correct.
Free No Rush Shipping with $1 Amazon MP3 Credit
Free 2-Day Shipping
$3.99 per item Next Day Shipping
$7.99 per item 8 Hour Service (maximum 20 pounds)
MAKE IT HAPPEN
For example, communication protocols (like this one) are specified in powers-of-10 units because they're based on measuring wireless frequencies, which are measured in powers-of-10 hertz -- in this case, I'm sure that 1.5 Gbps means 1.5E9 bits per second. A 14.4 kbps modem transmitted 14,400 bits per second. A T-1 line transmits 1.54 Mbps, meaning 1,540,000 bits per second -- and note that framing and other overhead bits mean that you can't just divide by 8 to get bytes per second.
You, like many modem vendors who labelled their products at X kbps, instead of X k, are just wrong.
You're confusing BAUD with BITS.
A 56k modem is 56,000 BAUD.
And yes, floppies were a cluster fuck. All of storage was, because they all wanted to advertise more space. 1 KB was 1024 bytes, and everyone knew it. But a MB was something new to a lot of people, so they thought they could get away with calling 1000 KB 1 MB. Many of the early storage devices weren't actually specced in a number of bytes, anyway, they were specced to tracks, sectors, etc. which marketing goons confused/abused, take your pick.
While GoogleDocs version lacks a lot of features Excel provides, it's FILTER function, and it's ability to process whole columns, as opposed to just ranges, makes certain operations so much more elegant, extensible and maintainable. While nowhere near close in a head-on, feature-for-feature comparison, there are certainly use-cases where Google's version is more useful than Excel.
So basically you don't know how to use Excel?
Excel functions absolutely can work on an entire column.
A Heiselber's Uncertainty Principle attacks!
It says "hello"!
It is very effective!
Just because we can't know a position and vector of a particle now doesn't mean we won't ever be able to.
Furthermore, that doesn't change the fact that the numbers aren't random, even if they're unknown and unpredictable.
If we live in a deterministic Universe, and I believe we do, there is nothing that is random.
The CA system is set up so that you can be reasonably sure that the host you're connected to is who they say they are.
You "trust" that a certificate they present is legitimate because it is cryptographically signed by a CA.
You trust the CA because you have a root list of CAs to trust, typically fed to you by MS.
The problem with the CA system is the fact that the CAs themselves are untrustworthy.
They don't do their due diligence in verifying hosts they issue certificates to, safeguarding their private keys, or revoking certificates when keys get stolen.
The entire idea is insecure because users want shit to work transparently, and CAs want to do shit as cheaply as possible.
You can have all the logs and auditing that you want, but when some soccer mom can't buy something on Amazon, your system has failed.
And when some CA fucks up and nobody knows because no one is actually monitoring those logs, your system has failed.
And if you DO have dedicated groups that monitor logs and do audits, it becomes the same fucking game of knowing which monitoring group to trust, how far to trust them, etc. 99.9999% of users will just be confused, and will think their next computer crash has something to do with the internet hacks Wolf Blitzer told them about.
The only way to trust a host is to verify their identity yourself. And if you're going to go and fucking verify the trustworthiness of CAs via analyzing their logs yourself, you may as well just verify the trustworthiness of individual sites yourself. Call up Amazon and ask them about their certificate. Maybe they should print it on the back of all their packing slips.
I had no idea one could put a firmware update in a print job.
Is this possible?
I don't know.
Therefore, aliens.
The telecommuter isn't taking up a cubicle.
He doesn't clog up the toilet.
He won't have a heart attack in the office.
He doesn't need a parking space.
He doesn't suck back gallons of coffee.
He doesn't add to the fire code limit of how many sardines you can pack into the can.
Physical presence comes with a cost and presents a liability.
Given 2 equal employees I'd axe the one at the office and keep the one at home.
If the lack of a physical presence is detrimental to your business in any way (people don't know how shit works, people don't know who to go to, etc.), then the two weren't really equal, and you're doing it wrong.
There's no way to guarantee you won't be in the .15% whose vasectomies fail, so saying it's 100% effective is misleading. Also, there are a handful of cases of spontaneous healing of the gap in that .15%, so it's not even 100% for correctly implemented vasectomies.
99.85% of the time, it works every time.
It's extremely effective.
There's even a dedicated group of people in the US and other western countries today that use such methods (organized through the internet, of course) and measure their own sperm counts and report results. Some of the more dedicated actually manually push their testicles back into their abdominal cavity, either over night or just keeping them there 24/7.
Both of which can be trivially faked, but then lots of legal matters hinge on something as ridiculously arbitrary as a signature - a random mark on a piece of paper which is even easier to fake.
Trivially faked and trivially verified.
Send subpoenas to whoever owns the various servers the email passed through.
You won't get the body of the email, but you will get logs out the ass.
How much money will US corporations throw at the EU cheeseheads to decide in their favor?
My guess: a lot.
How about:
1: Pop open case.
2: Remove Drive.
3: ???
4: Profit (through continued employment).
?
You only want 1 copy of the data, so the original is the backup.
Just convince the nearest PHB that it's a waste of your time and their money to wipe drives. If the machines are going to be repurposed or sold, it's cheaper and easier to buy new drives, or sell them without the drive. As for the backup, same deal - cheaper and easier to store a bunch of HDDs in anti static bags in a box somewhere. Safer than storing their data on a live backup device anyway. And if you need immediate, constant access to that data - why are you killing the machines in the first place?
But if you have to do it their way, get Acronis. It lets you backup an entire drive to a network location from a bootable cd / usb thingamajig.
It works with like, every fucking SATA / RAID controller there is, and if it doesn't, you get official support for building a BartPE disc that includes those drivers so you can get your shit on. You can even do a full drive backup from within windows. It's pretty fast, too. You can encrypt backups with AES-256, and you can browse through the backups with any machine that has Acronis installed. You could also of course dump the full contents of the backup into a 7zip archive or some other format if you wanted to not depend on Acronis's file format and software in the future.
Just make as many copies of the disc as you have network ports in whatever dark corner you'll be working in, line em all up, tell them to go, then play Minecraft until it's time to switch out machines. I think the bootable cd also has basic 0 wiping tools, as well, but I don't know for sure.
When you build something essential to the operation of a must-have, you'd better believe the government is going to come knocking.
I don't know about you, but the last time I looked at CISCO's products and services, they were:
Vaguely defined
Overpriced
Intentionally confusing
The trifecta of an aging tech company that focuses more on its past reputation that its forward progress.
CISCO used to be the guys who made routers, and they gave us a backwards ACL notation system that everyone uses (because they got a certificate in it).
Today? They run ads about how they are able to violate causality - a school in the US and a school in China are video conferencing with no lag. In the middle of the day. At both locations. I guess they still sell routers, too, but why pay their ridiculous prices when you can get the same hardware elsewhere, or hell, build it your fucking self, for cheaper?
Your entire posts shows that you have no idea what you're talking about.
SI doesn't get to claim letters and symbols for its own exclusive use. It doesn't matter that K was in use. SI has no authority over anything. Furthermore, the use of 1024 instead of 1000 has an intrinsic practical advantage in computer science - shit is binary and we care about permutations, so we like powers of 2. They're infinitely more useful.
And SI scalars are scalars. They are not prefixes even though they call them that - they can be, and are, inserted ANYWHERE in a computation or algebraic statement. They are scalar multiples. If you want to bitch about K being lower case, fine - just go ahead and first concede that KB isn't confusing at all because K isn't an SI prefix. And then ignore M and m for meter, milli, and mega.
As for the 1, "according to whom?"? According to SI! Read their fucking shit and learn what a mass fraction is. It's absurd.
Again, SEVERELY LIMITING. If an employee is writing down every SSN that comes in, it will be extremely easy to figure out which employee is the one stealing ID's. Not to mention it'll be pretty obvious to supervisors walking around the office when they see someone writing down the SSN's. Furthermore, the number of ID's they can steal in a given month is minuscule in comparison.
Not limiting at all, because the way it is right now every account lookup is logged already.
None of those employees need to be able to read existing entries though. All they need is a field where the rep asks you for your SSN, they type it in and hit a button, and it matches it against the database. If for some reason it wasn't matching, and they needed to actually view the entry, they would request a manager to unlock the one record for them temporarily.
This would severely limit the amount of information they had access to.
1) Please note what time it is.
2) Read your post again.
3) When you realize your folly, note the time again.
4) Please reply with the amount of time it took you to realize that if the employee KEYS IN the SSN YOU PROVIDE to match against, THEY KNOW the one you gave during account setup and the one you gave during the support call when they match. If they don't match, they know the one you gave during the support call and your solution is to UNLOCK THAT SINGLE ENTRY for them to view, so they know both anyway.
The proper thing to do is to NOT FUCKING STORE SSNs. But that would make selling the information and doing credit checks much more troublesome. So they don't give a shit. At lot of places at least let you set up a PIN number that you can use when talking to a customer support peon (as opposed to the last 4 of your social), at least.
What can I do with 30 GiB/s? I'm trying to figure that out, give me some ideas.
Nothing, because a "GiB" is not a thing.
1 GB is 1073741824 Bytes. It always has been, and it always will be.
Note that the "G" is not an SI scalar. No one ever said it was, and there's no reason it needs to be.
Note that there is never any confusion because you always see the G right next to the B. Indeed, there is no "K", "M", "G", etc.; there is a "KB", "Kb", and so on.
Note that calling 1 GB 1000000000 Bytes and 1 "GiB" 1073741824 Bytes - the proposed solution to the ambiguity - is what actually causes the ambiguity.
Note that the SI units, prefixes, etc. themselves have all sorts of ambiguity built in. T is Tesla. Or is it tera? K is Kelvin, or is it kilo? Gy is Giga...something? Oh no, it's just grays! And that's being generous - if you look at practical usage, where people and fields use units and variables of their own, or don't always use the proper case (or its use is indistinguishable), it's far worse. And then there's the mass fraction. Yup, kg/kg. The symbol for this unit? 1. That's right. The digit 1. Anytime you divide a mass by a mass you better add a superfluous 1 in there otherwise you're not compliant with the SI quackery!
It's "flammable" and "non-flammable" all over again. These are not words. These have been thrust upon the language like a /.er on a Yoda Fleshlight. The correct words are "inflammable" and "non-inflammable". The addition of "flammable" and "non-flammable" adds ambiguity and confusion where there was none. It has also killed people.
Neither of these are instances of language "evolving", so please kindly fuck off before you post that horse shit. The sole purpose of language is communication. When you introduce ambiguity and confusion, you are damaging the language.
Terahertz radiation is non-ionizing, unlike say X-Rays. This type of radiation is used in things like bomb detectors and to inspect explosives and other unstable compounds because it can penetrate a few millimeters but does not break down molecular bonds.
Non ionizing != safe.
There's a reason there's a little grill on your microwave door window.
That "study" only dealt with the correctness of the statistics applied to the data, it did not validate the data itself.
The data itself has been manually manipulated, and consists of disparate sets using different measurement methods, different amounts of accuracy, reliability, etc.
Yeah, this is off topic, but when dealing with such a meaningless story, I figure I cannot do any more harm
I am interested in learning about coding in a LAMP environment. My thought is I'd like to find a hosting partner (low cost) that has the infrastructure already. I want to do some of the configuration, and get started coding a PHP hello world, then work up to some more advanced topics involving mysql database access.
1) Who would be a good hosting partner for this? Not looking for free, but not looking to spend $100/month either.
2) Any good tutorials for basic configuration, sercurity considerations? PHP tutorials?
Set it up yourself in a VM, then when you're ready to make it actually do shit, export it to Amazon C3 or whatever they call it now.
Before the inevitable ridicule, the reason the wine is swirled is to get the aroma into the air inside the glass, enhancing flavor perception. As an analogy imagine taking a shit. You plop one, it stinks real bad for a while but then it gets better. Then you drop another, this stirs up the water and brings the stink back again for a bit.
Doesn't change the facts:
Wine snobs suck.
The movie Sideways sucks.
Wine snobs are just closet alcoholics.
Wine snobbery comes with oaky notes and hints of bullshit.