Yes, I was also occasionally the victim of a dictionary attack, as well as plain old address harvesting, but much more common was someone else named Jay (or someone whose initials were J) entering "jay@aol.com" as his e-mail address when signing up for a web site. It was very clear when the latter occurred - it was usually a legitimate mailing list that simply didn't use verified opt-in, or an e-commerce site that automatically added customers to their "hot products" newsletter.
Oddly, another common source of mail was an AOL member named Jay typing "Jay" into the CC field. This was less of a problem after the field label was changed from "CC to "Copy To" a few versions ago. It seems that, in the post-carbon-paper era, people don't always know what "CC" stands for. The first box is "To", so the second one must mean "From"!
I usually tell all those sites to send to joe@aol.com. I wonder who that poor sucker is
It's self-centered assholes like you that forced me to stop using jay@aol.com after nine years. My misdirected mailing list subscriptions were far more problematic than my spam load. You don't want to get e-mail, so you send it to someone else instead? Do you also dump your trash on your neighbor's lawn?
If you don't want to get spammed by e-commerce sites and the like, use "me@privacy.net". That sends an auto-response for every e-mail, telling the merchant that they should ask permission before assuming you want to be added to a mailing list. If the site tells you that is already used, try adding a single digit, e.g. me3@privacy.net.
Like the Way I Do" has an intro filled with highhats, cymballs and tambourines
Now if you could encode the "Brave and Crazy" intro at 128kbps, and the echo from the wood block was indistinguishable in PCABX, I'd be REAL impressed.
A UPS is an emergency backup solution for mission-critical applications. Building a UPS out of spare parts based on instructions from a web site seems like sewing a parachute using recycled grocery bags with a pattern from McCall's.
What they SHOULD have done was cut them off, and when the judge asks them why they proceded with teh cut off, despote the court order, simply retort, "We did NOT cut them off. We cut off a spammer. Since they have already admited to NOT being a spammer, logic dictates that we did not cut them off."
That is SOOO cool! That should work with ANY judge built on ANY silicon-based microprocessor.
Still, maybe just fuck up the routing tables to send their packets through every router in the building
Willfully disobeying a *court order* to provide service? Nice. You are not Kiefer Sutherland or a rogue cop out for justice. This is not 24. Your sense of cleverness and independent retaliation just cost your hypothetical employer hundreds of thousands of dollars, and probably the court case itself. Remind me never, ever to hire you.
the typical spammer is a guy running a home buisness or a store
No, the typical spammer these days is running a highly successful scam or porn site and often has ties to organized crime. The innocent days of Sanford Wallace are gone.
You don't see telemarketters calling people one by one thru the receptionnist in a 1000 employee company right?
Actually, you do. Not through the receptionist, but by sequential-dialing through DID lines. There's no law against it for business lines, unfortunately.
The irony is that contract lawyers generally consider the ALL CAPS section to be a means of complying with the requirement that warranty disclaimers are "conspicuous."
I should hope any contract lawyer worth his salt doesn't still think so, since that's been explicitly refuted in at least one appeals court ruling.
Which in a way proves to me that high-bandwidth IDE controllers are rare if not vaporware
OK, we're both right! I was thinking of the 3Ware RAID box, www.3ware.com. That's 64-bit, but it doesn't mention 66MHz. If it is 33MHz, the card can still handle 8 drives no problem, but you'd have 50% bus saturation by my early-morning math.
seems some people have to read a little closer:-/ Unless everyone in the company is a CEO that is a lot of space
Say what? You're not making any sense, man. 13 million square feet of *office space*, not of executive offices. Seems some people have to think a little closer.
You were not following the "thread" of the conversation, you were deflecting it to another issue.
You are right. I remembered some discussion about algorithms, but I thought the post I replied to (yours) was discussing the speed of the STL in general - in fact, it was of course discussing the algorithms as well. My bad.
Did you know, for example, that AOL Time Warner, at latest tally, has nearly 13 million square feet of office space on its books?
So what? At 90,000 employees, that works out to an average of 162.5 square feet per employee, including conference rooms, hallways, cafeterias, bathrooms, etc. That doesn't sound like a whole lot to me.
Unfortunately, that is what I meant. I used a sed script to replace string,and>>> with string, etc. That helped for the common problems, but debugging was a big problem - especially being unable to directly view the contents of data structures in a useful fashion. Suddenly, I had to create.debug_print functions for every single class...
Unfortunately, that is what I meant. I used a sed script to replace string>>> with string, etc. That helped for the common problems, but debugging was a big problem - especially being unable to directly view the contents of data structures in a useful fashion. Suddenly, I had to create.debug_print functions for every single class...
I'd like to see _any_ data to back up this implicit assertion that the STL algorithms are anything but very fast
Two or three years ago, in a high-volume e-mail-processing application running on Solaris and HP-UX, compiled with GCC 2.9x and the STL that came with it, found that c-strings performed significantly better than the much more elegant STL string class.
I do realize that libstdc++ is probably farther along now, and that GCC 3.0 is out now, and I make no claim about any other compiler or STL implementation. But one of the most popular implementations of the STL *did* have performance problems with one of the most popular classes.
I once spent a month trying to get STLPort to compile on a Solaris 7 box with gcc 2.97. Never did get it working, and got no help from stlport.org either.
The point is that you shouldn't wait until you've implemented five levels of code before you start debugging let alone compiling.
The question is not when you start debugging.
The question is when you expect to finish.
If the answer is "never", then your code must be debuggable. STL isn't, at least not with today's compilers, although you can approximate it for the *common* errors with a sed script.
Unfortunately this opens up the possibility of simply taping a photocopy of somebody else's thumbprint onto my own thumb.
No, it doesn't, because you're BUYING GROCERIES.
It doesn't have to be impenetrable. There are easier, and less detectable, ways to fraudulently buy groceries. You think nobody on line behind you is going to notice you walking around with a photocopy of a fingerprint TAPED to your THUMB?
None of those would apply, because none of those are in Gecko. The CompuServe client is still a client unto its own right; it sounds like it will just open browser windows with Gecko instead of IE.
When AOL first bought CompuServe, it was supposed to be the business brand, with AOL the home brand. Made sense, given where CompuServe Classic was. However, that didn't last long, as few businesses (in the CompuServe sense) use dialups anymore.
These days, CompuServe is the "discount" brand. It's still $9.95 for 20 hours, $19.95/mo for unlimited use, $199 for a year of unlimited service (about $17/mo). If you're just looking for the forums and other content, it's still $9.95/mo for bring-your-own-access.
Back in the days of Q-Link, when screen names were only 10 characters and there was no automatic recycling after six months, Q-Link would auction off a handful of used screen names to the highest bidder. We're only talking in the tens of dollars, but it was always interesting to see what screen names people were willing to PAY to get.
Slashdot Mirror
Yes, I was also occasionally the victim of a dictionary attack, as well as plain old address harvesting, but much more common was someone else named Jay (or someone whose initials were J) entering "jay@aol.com" as his e-mail address when signing up for a web site. It was very clear when the latter occurred - it was usually a legitimate mailing list that simply didn't use verified opt-in, or an e-commerce site that automatically added customers to their "hot products" newsletter.
Oddly, another common source of mail was an AOL member named Jay typing "Jay" into the CC field. This was less of a problem after the field label was changed from "CC to "Copy To" a few versions ago. It seems that, in the post-carbon-paper era, people don't always know what "CC" stands for. The first box is "To", so the second one must mean "From"!
I usually tell all those sites to send to joe@aol.com. I wonder who that poor sucker is
It's self-centered assholes like you that forced me to stop using jay@aol.com after nine years. My misdirected mailing list subscriptions were far more problematic than my spam load. You don't want to get e-mail, so you send it to someone else instead? Do you also dump your trash on your neighbor's lawn?
If you don't want to get spammed by e-commerce sites and the like, use "me@privacy.net". That sends an auto-response for every e-mail, telling the merchant that they should ask permission before assuming you want to be added to a mailing list. If the site tells you that is already used, try adding a single digit, e.g. me3@privacy.net.
Like the Way I Do" has an intro filled with highhats, cymballs and tambourines
Now if you could encode the "Brave and Crazy" intro at 128kbps, and the echo from the wood block was indistinguishable in PCABX, I'd be REAL impressed.
A UPS is an emergency backup solution for mission-critical applications. Building a UPS out of spare parts based on instructions from a web site seems like sewing a parachute using recycled grocery bags with a pattern from McCall's.
What they SHOULD have done was cut them off, and when the judge asks them why they proceded with teh cut off, despote the court order, simply retort, "We did NOT cut them off. We cut off a spammer. Since they have already admited to NOT being a spammer, logic dictates that we did not cut them off."
That is SOOO cool! That should work with ANY judge built on ANY silicon-based microprocessor.
Oh, but wait.
Still, maybe just fuck up the routing tables to send their packets through every router in the building
Willfully disobeying a *court order* to provide service? Nice. You are not Kiefer Sutherland or a rogue cop out for justice. This is not 24. Your sense of cleverness and independent retaliation just cost your hypothetical employer hundreds of thousands of dollars, and probably the court case itself. Remind me never, ever to hire you.
the typical spammer is a guy running a home buisness or a store
No, the typical spammer these days is running a highly successful scam or porn site and often has ties to organized crime. The innocent days of Sanford Wallace are gone.
You don't see telemarketters calling people one by one thru the receptionnist in a 1000 employee company right?
Actually, you do. Not through the receptionist, but by sequential-dialing through DID lines. There's no law against it for business lines, unfortunately.
The irony is that contract lawyers generally consider the ALL CAPS section to be a means of complying with the requirement that warranty disclaimers are "conspicuous."
I should hope any contract lawyer worth his salt doesn't still think so, since that's been explicitly refuted in at least one appeals court ruling.
More likely, it's been cut and paste forever.
Which in a way proves to me that high-bandwidth IDE controllers are rare if not vaporware
OK, we're both right! I was thinking of the 3Ware RAID box, www.3ware.com. That's 64-bit, but it doesn't mention 66MHz. If it is 33MHz, the card can still handle 8 drives no problem, but you'd have 50% bus saturation by my early-morning math.
I haven't seen any IDE controllers that sport a 64-bit/66 MHz PCI bus interface
Then you haven't checked Google. They're out there.
I am actually curious what kinds of things were being done with the strings that made it slow.
If I knew, I forgot...
seems some people have to read a little closer :-/ Unless everyone in the company is a CEO that is a lot of space
Say what? You're not making any sense, man. 13 million square feet of *office space*, not of executive offices. Seems some people have to think a little closer.
You were not following the "thread" of the conversation, you were deflecting it to another issue.
You are right. I remembered some discussion about algorithms, but I thought the post I replied to (yours) was discussing the speed of the STL in general - in fact, it was of course discussing the algorithms as well. My bad.
Did you know, for example, that AOL Time Warner, at latest tally, has nearly 13 million square feet of office space on its books?
So what? At 90,000 employees, that works out to an average of 162.5 square feet per employee, including conference rooms, hallways, cafeterias, bathrooms, etc. That doesn't sound like a whole lot to me.
You said "use the STL algorithms only if you don't care about performance". Now, you are backing that up by saying that the "string" class is slow.
And if it were I that had said the former, you would have successfully poked a hole in my argument.
Unfortunately, that is what I meant. I used a sed script to replace string,and>>> with string, etc. That helped for the common problems, but debugging was a big problem - especially being unable to directly view the contents of data structures in a useful fashion. Suddenly, I had to create .debug_print functions for every single class...
unless you mean the compiler error messages
.debug_print functions for every single class...
Unfortunately, that is what I meant. I used a sed script to replace string>>> with string, etc. That helped for the common problems, but debugging was a big problem - especially being unable to directly view the contents of data structures in a useful fashion. Suddenly, I had to create
I'd like to see _any_ data to back up this implicit assertion that the STL algorithms are anything but very fast
Two or three years ago, in a high-volume e-mail-processing application running on Solaris and HP-UX, compiled with GCC 2.9x and the STL that came with it, found that c-strings performed significantly better than the much more elegant STL string class.
I do realize that libstdc++ is probably farther along now, and that GCC 3.0 is out now, and I make no claim about any other compiler or STL implementation. But one of the most popular implementations of the STL *did* have performance problems with one of the most popular classes.
I once spent a month trying to get STLPort to compile on a Solaris 7 box with gcc 2.97. Never did get it working, and got no help from stlport.org either.
The point is that you shouldn't wait until you've implemented five levels of code before you start debugging let alone compiling.
The question is not when you start debugging.
The question is when you expect to finish.
If the answer is "never", then your code must be debuggable. STL isn't, at least not with today's compilers, although you can approximate it for the *common* errors with a sed script.
If the answer isn't "never", rethink your answer.
If the answer is not "never", you're wrong.
Unfortunately this opens up the possibility of simply taping a photocopy of somebody else's thumbprint onto my own thumb.
No, it doesn't, because you're BUYING GROCERIES.
It doesn't have to be impenetrable. There are easier, and less detectable, ways to fraudulently buy groceries. You think nobody on line behind you is going to notice you walking around with a photocopy of a fingerprint TAPED to your THUMB?
The supermarket is not your lab, Dr. Biscuit.
Compuserve Classic has been left out there to whither and die.
You don't think that's because it's running on hardware that isn't even made anymore, do you?
None of those would apply, because none of those are in Gecko. The CompuServe client is still a client unto its own right; it sounds like it will just open browser windows with Gecko instead of IE.
When AOL first bought CompuServe, it was supposed to be the business brand, with AOL the home brand. Made sense, given where CompuServe Classic was. However, that didn't last long, as few businesses (in the CompuServe sense) use dialups anymore.
These days, CompuServe is the "discount" brand. It's still $9.95 for 20 hours, $19.95/mo for unlimited use, $199 for a year of unlimited service (about $17/mo). If you're just looking for the forums and other content, it's still $9.95/mo for bring-your-own-access.
Back in the days of Q-Link, when screen names were only 10 characters and there was no automatic recycling after six months, Q-Link would auction off a handful of used screen names to the highest bidder. We're only talking in the tens of dollars, but it was always interesting to see what screen names people were willing to PAY to get.