In heavy traffic in a large city, people do obnoxious shit all the time. They do it because nobody they'll ever speak to will see it.
Hmmm, I wonder if there is an online version of this phenomenon? Perhaps a pseudo-anonymous forum where people make nasty, pointless comments without regard for others' feelings. Naaahhh...
The solution to the spam problem is simple yet elegant - gambling.
Every time you send an email you place a small wager on the line that the recipient wants to read your message. Something like 1 cent. If the recipient doesn't mind your message then they don't redeem your offer and it doesn't cost you a thing. However, if you're sending spam then the recipient cashes it in (or perhaps it is used to cover overhead costs of this system).
If you send a legitimate email and somebody decides to be a jerk and cash it in then you're only out 1 penny. However, if you just sent 2 million of those unwanted emails you're screwed.
This is better than the "small price" schemes because it doesn't cost anything. Well, unless you're A) a spammer or B) sending email to dickheads.
This wouldn't replace SMTP, it would just be a layer on top. If you sent an email and you participated in this system then a third party would sign your messages and you'd be get a special verifiable header that the recipient could then treat as "likely ham".
Get yourself a late model 2.4 kernel and follow the directions for 2.6. Everything works the same. If you use Debian 'testing' or 'unstable' the other packages you'll need are ipsec-tools and then racoon (KAME) or isakmpd.
It's actually pretty easy if you just follow the examples.
Good - perhaps this is what we've been needing to finally kill off MP3. Thomson and Fraunhofer are morons if they think this will help market share. The *only* compelling feature of MP3 over WMA or whatever is that you don't have to dick around with licenses for your MP3 playing hardware.
Good news - you don't need 2.6 to do native IPSEC.
I've done a couple FreeS/WAN installs on 2.4 and they were kind of difficult to set up. Not too bad - just painful enough to appreciate them.
However, the other day I decided to try the Linux kernel's new native IPSEC modules (that have been backported to at least 2.4.24). Using 2.4.24 and KAME it was an absolute pleasure to set up. Works beatifully, and no more patching. You couldn't pay me to return to FreeS/WAN.
Seeing as any changes the NSA make are presumably only used internally by the agency, they are under no obligation to release the source.
Actually, anything produced by federal government is public domain. Of course they could have easily said that it would be a security risk to release their work and nobody would have doubted it.
E-mail is free. Deal with it. If you want to have some moronic pay to send system feel free to set it up and watch as no one in their right mind uses it.
You're a doofus. Email would continue to be free. My suggestion is simply an add-on that would allow for "certified non-spam". You could still send and receive regular SMTP, but some emails would come with the sender wagering 5 cents that you won't think it's spam.
Your fucking solution is to bury your head in the sand and say, "I like having 4 email accounts and filtering out 25 messages a day". Whatever.
Okay, I've been thinking about this one for a while, but feel free to shoot me down.
When you send someone an email message you initiate a potential financial transaction for a tiny amount of money (say $.5). If the recipient is so inclined they can complete the transaction and "cash in" your $.5. The idea is that people that want to receive email from you will not redeem your offer.
If you send a non-spam email to someone and they decided to be a jerk and cash in then you're only out 5 cents. Of course if you're a spammer and you just sent that email to 200,000 people then you've got a problem.
Obviously this would not be built into SMTP (to preserve compatibility) but would rather be a layer on top that the common email clients would have to handle. There's also some infrastructure details to be worked out like cryptographic method, payment processing (perhaps 1% of the completed transactions go towards the organization handling the payment processing), etc.
I know it just can't be that simple, so why wouldn't idea this work?
They are asking their UNIX licensees. They are well within there right to do so as such a provision is almost certainly in the contract that the licensees signed.
Now, if they were asking random Linux users it would be another story.
Slashdot Mirror
In heavy traffic in a large city, people do obnoxious shit all the time. They do it because nobody they'll ever speak to will see it.
Hmmm, I wonder if there is an online version of this phenomenon? Perhaps a pseudo-anonymous forum where people make nasty, pointless comments without regard for others' feelings. Naaahhh...
Plus the automated trash talking would be great fun!
So you're the guy who thought that was a good idea in Unreal Tournament.
More fun because you get to drink the sake while you play with your wood.
I prefer to save the food and beverages until after I'm done with that.
Heh - it did fork. It's frickin' called .NET.
Well then you need to find friends that aren't so hard up for a damn penny that they rip you off.
It's not "pay to send spam", it's "pay if the recipient wants you to"
Guess what - if the recipient wants you you to pay that means he didn't want your email. Do you know what unwanted email is?
Uh, if all the recipients want to receive the mailing list what would be the problem? It's not "pay to send", it's "pay to send spam".
The solution to the spam problem is simple yet elegant - gambling.
:)
Every time you send an email you place a small wager on the line that the recipient wants to read your message. Something like 1 cent. If the recipient doesn't mind your message then they don't redeem your offer and it doesn't cost you a thing. However, if you're sending spam then the recipient cashes it in (or perhaps it is used to cover overhead costs of this system).
If you send a legitimate email and somebody decides to be a jerk and cash it in then you're only out 1 penny. However, if you just sent 2 million of those unwanted emails you're screwed.
This is better than the "small price" schemes because it doesn't cost anything. Well, unless you're A) a spammer or B) sending email to dickheads.
This wouldn't replace SMTP, it would just be a layer on top. If you sent an email and you participated in this system then a third party would sign your messages and you'd be get a special verifiable header that the recipient could then treat as "likely ham".
Anybody have a better idea? I didn't think so.
Well, basically I just followed the directions on these sites:
http://lartc.org/howto/lartc.ipsec.html
http://www.ipsec-howto.org/t1.html
Get yourself a late model 2.4 kernel and follow the directions for 2.6. Everything works the same. If you use Debian 'testing' or 'unstable' the other packages you'll need are ipsec-tools and then racoon (KAME) or isakmpd.
It's actually pretty easy if you just follow the examples.
Good - perhaps this is what we've been needing to finally kill off MP3. Thomson and Fraunhofer are morons if they think this will help market share. The *only* compelling feature of MP3 over WMA or whatever is that you don't have to dick around with licenses for your MP3 playing hardware.
Long live Ogg Vorbis.
Good news - you don't need 2.6 to do native IPSEC.
I've done a couple FreeS/WAN installs on 2.4 and they were kind of difficult to set up. Not too bad - just painful enough to appreciate them.
However, the other day I decided to try the Linux kernel's new native IPSEC modules (that have been backported to at least 2.4.24). Using 2.4.24 and KAME it was an absolute pleasure to set up. Works beatifully, and no more patching. You couldn't pay me to return to FreeS/WAN.
Seeing as any changes the NSA make are presumably only used internally by the agency, they are under no obligation to release the source.
Actually, anything produced by federal government is public domain. Of course they could have easily said that it would be a security risk to release their work and nobody would have doubted it.
I don't want a G5 on my lap anyway. It'd make me feel guilty, having that much power in a small package
Don't you mean, "on a small package"?
c) Be persistent
Do they really need that in the handbook? What did they use to do when they had a problem?
Engineer 1: "Shit Fred, I can't ping it."
Engineer 2: "Oh well, cest la vie. You wanna grab a beer?"
System load could be signified by clicks, with the frequency of the clicks increasing as system load increases.
Sounds like you're looking for this. Particularly, feature #3. It makes your computer sound like WOPPER in War Games.
Sorry, but there's very few things worse than being a weasel.
Weaseling out of things is important to learn. It's what separates us from the animals. Except the weasel.
-- Homer Simpson
Boy-Scoutz n the Hood
E-mail is free. Deal with it. If you want to have some moronic pay to send system feel free to set it up and watch as no one in their right mind uses it.
You're a doofus. Email would continue to be free. My suggestion is simply an add-on that would allow for "certified non-spam". You could still send and receive regular SMTP, but some emails would come with the sender wagering 5 cents that you won't think it's spam.
Your fucking solution is to bury your head in the sand and say, "I like having 4 email accounts and filtering out 25 messages a day". Whatever.
Okay, I've been thinking about this one for a while, but feel free to shoot me down.
When you send someone an email message you initiate a potential financial transaction for a tiny amount of money (say $.5). If the recipient is so inclined they can complete the transaction and "cash in" your $.5. The idea is that people that want to receive email from you will not redeem your offer.
If you send a non-spam email to someone and they decided to be a jerk and cash in then you're only out 5 cents. Of course if you're a spammer and you just sent that email to 200,000 people then you've got a problem.
Obviously this would not be built into SMTP (to preserve compatibility) but would rather be a layer on top that the common email clients would have to handle. There's also some infrastructure details to be worked out like cryptographic method, payment processing (perhaps 1% of the completed transactions go towards the organization handling the payment processing), etc.
I know it just can't be that simple, so why wouldn't idea this work?
That being said, I would sign myself up and my wife would sign up for this mission too.
How fucking stupid. I say we send you both too.
I'm pretty sure you'd feel like a complete moron when after the first 3 hours you're thinking "shit, I could've got the same effect in Arizona".
Seriously, what exactly is worth dying for on Mars?
How could you stir it if it has no viscosity?
brb 2 secs, someone's at the door...
It's the dog.
I have a better idea. Wardrive for 15 minutes downtown until you have a 100% anonymous IP address. Good luck tracking that down.
if I had invested my life savings in SCO stock last Christmas I would now be a multi-millionaire
Haha - what a loser. I only missed out on the chance to be a multi-thousandaire.
They are asking their UNIX licensees. They are well within there right to do so as such a provision is almost certainly in the contract that the licensees signed.
Now, if they were asking random Linux users it would be another story.