You're missing the point altogether. Any entrepreneur with any reasonable experience knows that retention of anything but the last 4 digits of a card number puts you on the wrong side of PCI compliance. These guys are obviously a bunch of amateurs and should not be trusted.
I'm fairly certain it would be the people stopping short to avoid photo enforcement that caused the accidents. Probably a subsequent threat of a lawsuit by the person who rear-ended one of those people caused the city to rethink and remove the cameras.
I'll second the bfd and apf. It could be the 1M ssh attempts are sourced from a relatively small number of ip addresses, but since they are allowed to run unchecked, they run a whole dictionary or maybe even a brute force attack. I've found with bfd, once the bots start getting timeouts, they give up.
You know, that was very well stated. I was going to say, he should instead forego the firmware update, and take the chance at winning a unique category on the Darwin Awards.
You can, but probably your best bet is to use a fish tape to get through, then pull a string back. Get the good nylon pulling twine, and some cable lube almost never hurts. And don't ever use dish soap as a lube, it works great the first time, then turns hard as a rock. Yes, I was too lazy to go to the store one day.
What else would you use to pull a cable? Fairy dust? I think your mistake is you didn't have someone on the supply end feeding the cable and keeping it from getting kinked.
1 in 20 failures? I've made hundreds, perhaps even a thousand cables with my $75 Paldin crimper, not a single bad one. You get what you pay for, I guess.
That's not true. The theoretical utilization limit on 10Base2 was 60%. I've actually seen 10Base2 installations running at 71%. The theoretical utilization limit is arrived at by the length of the collision window, the back off and retry timing when a collision occurs, which is based on the MAC address of the card, and the packet length. With the right set of cards, and large packets, you can achieve results that exceed the theoretical maximums.
Also, you can get damn near 10Mbits between two nodes, if there aren't any other nodes contending for the wire.
It's not really longer than Cat 5. With Cat 5, the maximum distance between two workstations is 200m. It's about the timing of the collision window and the amount of time it takes the signal to travel down the wire.
Slashdot Mirror
No, it just means he could have been doing it last week, and it would still be before you lost your virginity /rimshot
You're missing the point altogether. Any entrepreneur with any reasonable experience knows that retention of anything but the last 4 digits of a card number puts you on the wrong side of PCI compliance. These guys are obviously a bunch of amateurs and should not be trusted.
/nt
In Soviet Google, privacy discloses you.
Really, this shouldn't matter, unless they are doing something they should not be doing.
C'mon now, you know you should have gone anywhere but Pomona.
Yeah, tell me how it works for you once some asshats from 4chan hack your printer and burn up all your paper and ink printing kiddie porn.
In a battle between two vendors, one with a closed source, insecurt framework and the other with a closed platform, which side do I root for?
Neither. You should ignore this, and use only GPL-licensed software. /laughs
I'm fairly certain it would be the people stopping short to avoid photo enforcement that caused the accidents. Probably a subsequent threat of a lawsuit by the person who rear-ended one of those people caused the city to rethink and remove the cameras.
Here's hoping we can make it 3 by adding you to the list.
Going by the charges filed, I think this is more of a case of "doing it online doesn't give you a free pass".
Especially the part where it says they are relicensing code contributions without the consent of the contributors.
They probably do, but I imagine everyone is still on allocation with the i7, so newegg is forced to go to the open market to meet the demand.
Does anybody know how to read?
I think your judgment is a little premature. It could be some guy on the dock at IPEX swapped a pallet for his criminal cronies.
Ah gee. Here's the appropriate response to the fp: http://instantrimshot.com/
I'll second the bfd and apf. It could be the 1M ssh attempts are sourced from a relatively small number of ip addresses, but since they are allowed to run unchecked, they run a whole dictionary or maybe even a brute force attack. I've found with bfd, once the bots start getting timeouts, they give up.
You know, that was very well stated. I was going to say, he should instead forego the firmware update, and take the chance at winning a unique category on the Darwin Awards.
to dub him "Jimmy Fails"
You can, but probably your best bet is to use a fish tape to get through, then pull a string back. Get the good nylon pulling twine, and some cable lube almost never hurts. And don't ever use dish soap as a lube, it works great the first time, then turns hard as a rock. Yes, I was too lazy to go to the store one day.
What else would you use to pull a cable? Fairy dust? I think your mistake is you didn't have someone on the supply end feeding the cable and keeping it from getting kinked.
1 in 20 failures? I've made hundreds, perhaps even a thousand cables with my $75 Paldin crimper, not a single bad one. You get what you pay for, I guess.
That's not true. The theoretical utilization limit on 10Base2 was 60%. I've actually seen 10Base2 installations running at 71%. The theoretical utilization limit is arrived at by the length of the collision window, the back off and retry timing when a collision occurs, which is based on the MAC address of the card, and the packet length. With the right set of cards, and large packets, you can achieve results that exceed the theoretical maximums.
Also, you can get damn near 10Mbits between two nodes, if there aren't any other nodes contending for the wire.
It's not really longer than Cat 5. With Cat 5, the maximum distance between two workstations is 200m. It's about the timing of the collision window and the amount of time it takes the signal to travel down the wire.
186,000 miles per second. It's not just a good idea, it's the law.