1: The guy clearly was breathing. It can be seen and heard.
Sheesh. Read some of the other posts here. The cop was kneeling on his neck. They had Pepper-sprayed him, too. He was evidently having trouble breathing. He said "I can't breathe." WHat he meant was "I am having trouble breathing, do to your KNEE on my NECK and the PEPPER-SPRAY you squirted me with." He just chose the more concise way of saying it.
3: Where's the rest of the video? Why was it cut off?
RTFA. It was taken with a camera phone. Those things often have a time limit on how much video they can record at once. 20 seconds sounds about right. (I personally have a digital camera that can record video as well- it can record 20 seconds of 'high' quality, or 80 seconds of 'low' quality at one time.)
I'm not a big fan of the police but this is a bullshit video. It's propaganda designed to manipulate me. Show me the whole video and let me make my own decision.
That's only if his breathing was cut off completely. If he turned his head, and the cops knee was on the SIDE of his neck, rather than stright against his larynx, then he would be able to breath somewhat, but it might still be difficult.
Also, look a few posts down at what the AC says: Do you really expect long, drawn out (but technically correct) explaination? "Excuse me officer(s). The physical position I am in, what with your kneeling on my neck and all, combined with the copius amounts of pepper-spray you sprayed me with, added to by the stress of this situation, is making it quite difficult to breathe." Or would you just gasp out"I can't breathe-"?
4) Serpico. He testified against the corrupt cops, and then was left to die when shot during a drug bust. His Fellow Officers refused to call for assistance.
But other than that, you got all the possible types of cops:
1) Criminal cops 2) Cops who know about criminal cops, but do nothing. (They are just as bad, morally.) 3) Cops so stupid/naive that they don't know about type 1 and 2 cops. (Who wants cops THAT dumb on the force??) 4) Cops who are honest (and get left for dead like Serpico).
So how is the government to know you bought women's lingerie and not silk bikini briefs for yourself without cooperation from the store?
RFID. If things keep going the way they are going, soon everything you buy will have an RFID tag in it.
So, lingerie fetish - check, was at scene of first murder on night in question? Nope, our CCTV cameras did not show you in the area of the park on the evening of June 21st, guess you're not him.
CCTV cameras are useless for IDing someone. What if the murderer wears a baseball cap, and his face is in shadow? Anyone can wear a baseball cap...
Or, what about this other murder on Downy St? You live alone so your alibi you were at home at that time really doesn't hold well, but wait, our CCTV camera from your street recorded you going into your house at 8pm and you didn't emerge until ten the next morning.
1) See above. CCTV can't tell the difference between me and my neighbor. 2) I could have walked out the BACK DOOR. Or jumped out a window, for that matter.
It's only power against us if there is a reason to do something and they take action. This would require laws. A threat of action through constant surveillance only works on people paranoid about the government to begin with and sure they are doing something wrong, whether it's true or not.
There are different laws in different places. Even in the same place, there are different laws at different times. What is legal today may be illegal tomorrow. What 'todays government' may not care about, 'tomorrows government' may try to wipe out.
Does that sound familiar? Yeah, it's exactly what other pedestrians do when you're walking around in public right now. They see you as you pass by, may turn to look if you're doing something interesting, and if they really want to, follow you for a bit if they wish.
But they don't RECORD. No one gives a flying fuck if they are WATCHED in public- as they say, there is no expectation of privacy in public. But cameras are just SOOOOOO easy to record from. What happens to the recordings? How long are they kept? Who has access to them (legit or not)?
Well, my idea is not a scam. It wouldn't be run by one company, it would be a Free, Open Source solution.
Who would control this? Some US goverment agency?
That's the beauty of it- no one needs to 'control' it.
The best way to stop spam is to get people from purchasing crap from spam mailings. Just like JUNK POSTAL MAIL. IMHO
There's a problem with that: I've Never bought anything from a spam email, but I still get spam. I don't know of anyone who has ever bought anything from a spam email, but they still get spam. You see, it only takes literally 1 out of a million people to buy from a spam to make it worthwhile for the spammer to spam. Or, in other words, only 1 in 1,000,000 people respond to spams. That's already a pretty darn low number. I don't really see what can be done to lower that number. And since it's enough to keep the spammers spamming, there will always be spam.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being sen
Exactly- stick the Server (and other networking equipment) in a closet. Preferably one near an outside wall. Run a separate 'window' AC either directly outside thru the wall, or use some ducting to direct the hot air outside. The AC should be enough to keep the closet (and the server in it) nice and cool. If you want to get 'fancy', you can add some ducts and a fan or two that will kick in and circulate the 'normal' air thru the closet during the day, taking advantage of the existing whole-house AC (if it exists). At night, when the 'normal' AC is off, the one you installed for the server closet kicks on as needed.
It's time to put this fucking McDonald's hot coffee case to rest: It's been held up to be a shining beacon of the spurious nature of litigation in America when in FACT it is NOT.
Yes, it is.
The facts are: While sitting in the passenger seat of a parked car, Stella placed the cup between her knees and pulled the lid. This caused the cup to tip, and the coffee to spill into her lap.
- The plaintiff suffered 3rd degree burns over parts of her legs that required SKIN GRAFTS.
Appeal to Emotion is not a valid argument. It does not matter how severe the injuries were, since she caused them to herself through her careless handling of the coffee.
- McDonald's executives testified they KNEW their coffee was hot enough to cause 3rd degree burns (burn occur over 130 degree, McDonalds was brewing their coffee as high as 205).
Non-issue- that is the correct brewing temperature. The National Coffee Association backs this up. Also, I have personally found home coffee makers that use that temperature. CHeck out some of their online user manuals. For example: http://www.bunn.com/pdfs/retail/usecare/38865.0000 _NHBX_U_C_English.pdf Pay attention to page 3: "The water is approximately 50F hotter than what's available from your hot water faucet" (most hot water faucets are 140 deg. + 50 = 190!) and page 7: "BUNN recommends you AVOID:... Re-heating for serving any coffee with a temperature below 175F."
oh- almost forgot page 6: "The patented ready-to-brew reservoir keeps water at the ideal brewing temperature of approximately 200F."
- McDonald's ignored advice to post warnings about the possibility of burns
Incorrect. McDonlds had a warning on their cups already.
as well has ignore the warnings given to fast food industry as a whole that they were brewing their coffee too hot.
As said above, it is NOT "too hot".
- The evidence showed McDonald's coffee was consistently 20 degrees hotter than the industry average.
So?
The JUDGE AND JURY found McDonald's behaviour reckless, callous, and WILLFUL.
Juries suck. They are extremely easy to sway with emotion, and usually quite easy to confuse with tecnical terms, as well. I was on one that awarded a guy $130,000 for walking in back of a reversing mini-van. They would have 'only' given him $100,000, but one of the jurors pointewd out "His lawyer will take 1/3". Like it's out fucking job to pay his lawyer! (Oh, and did you spot the 5th-grade math error they made??)
More recently, I was on a jury that ended up hung. WHy? Because two minority jurors didn't find the 7 audio- and video-tapes of the (monority, of course) defendant dealing drugs convincing enough, and clung to the weak-ass defense claim, even after they were shown there were holes in it you could throw a drug addict through.
So, it doesn't matter that a jury decided against 'the big evil corporation', and for the 'poor defenseless woman'. It just shows how stupid juries are.
Having the receipt proves nothing. Maybe you swapped receipts with a random person. Maybe you picked it out of the trash. Maybe you belong to the If-your-boss-is-pressuring-you-to-vote-a-certain-w ay-come-here-and-get-a-receipt-that-shows-you-vote d-the-'right'-way club.
A receipt is worse than useless here... you don't WANT people to be able to show the party bosses that they voted the "right way".
Simply make sure the receipt has NO personal information on it. It's proof that someone voted for that candidate, but not that ANY PARTICULAR PERSON voted for that candidate. So, it's useless as 'proof you voted the right way'.
(X) Requires immediate total cooperation from everybody at once
-- That is, without the new SMTP software to support it, it's worthless
There is no new software required. The certification can easily be added as a 'plug in' or option to existing software. People could still use email software that does not include 'certification'- they just would not gain any benefits.
(X) Armies of worm riddled broadband-connected Windows boxes --It would be trivial for a worm to get it's current IP and use its ISPs mailserver for "smarthosting" outgoing mail. In fact, I think they're already doing it
In which case, the spam emails could be definitively traced back to the server they came from. A complaint is made, and the ISP investigates and cuts off the 'infected' customer's email service (until they clean their box) or a complaint gets sent to their upstream, who will investigate, and possibly revoke the ISP's email certification.
Either no more spam gets sent, or at least it is sent un-certified, which simplifies filtering.
-- You place too much faith in the SPs who will be "Certifying" users to be non-spammers. There are already providers out there offering "bulletproof hosting" and "pink contracts" to spammers for extra money.
And they have to get their Internet Service from somewhere. If their Upstream doesn't certify them, their un-certified emails will easily be filtered, and never seen. If their Upstream is evil and does certify them, then the Certified email from them (the spammer and/or the upstream, and/or everyone else the upstrean serves, depending on how hardcore you want to be) can be blacklisted.
With Certification, all email will come in Either Un-cerified, or Certified. If it's Uncertified, it can be junked, or whitelisted, or handled anyway the receiver wants. (Most peopel will just junk it, I think.) Certified email can be traced to a specific server, which provides a place to complain to if you get spam. If the owner of the server refuses to deal with it, you can go to the company who certified them, and get their email access cut off. Etc.
UUNET
| Big Regional ISP
| Local ISP
| Spammer
If 'Spammer' sends spam, then complain to Spammer. You KNOW the mail came from their server- the encryption involved in the Certification process proves it. If they solve the problem (maybe they were hacked, whatever), then the spam stops.
If Spammer refuses to do anything, then go to Local ISP. Tell then they Certified someone who is spamming, the Spammer refuses to stop. The ISP will revoke Spammers cerification. The spam, while still being sent, is now UN-certified, and will probably not reach anyone. In addition, Spammer can be added to a 'problem user' list, so if they try to change ISPs, their next ISP can be warned about the problem, and refuse to Certify them.
If Local ISP refuses to do anything, Contact Big Regional ISP. Tell them the story: that Spammer is spamming and refuses to stop, and Local ISP is not doing anything. Big Regional ISP can pressure Local ISP by threatening to revoke Local ISP's Certification. If they need to, they can actually revoke it.
Etc.
See how it works? The key to the whole thing is knowing for sure where the spam came from, so you can complain to them, or their upstream. Unlike the current situation, where email addresses can be spoofed, and bots can blast out untraceable spam from residential accounts, this forces everyone with a (certified) email server to BE RESPONSIBLE, or face the consequences. At the same time, ANYONE can still set up a 'hobby' email server that is UN-certified, and send out newsletters, etc., without restriction. They just need to let the receivers know to whitelist them, or their uncertified emails might end up in the trash.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
"Yes, Jimmy, people really do buy spam advertised products"
Fine. Some idiots out there buy vi@gr@ from spam. But I'd be willing to be that damn close to 0% of people WHO ACTIVELY FILTER SPAM buy stuff from spam.
So, who do they try so hard to defeat spam blockers?? Think about it- they are working so very hard in order to make their message reach the very people who specifically try to block it.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
Them go and pay $68.00 a pound for lettuce and you can't find an asparagus tip or a mushroom for love nor money.
Picking costs are around 5% of the retail price of the produce. Thet means 95% goes to other things. The picker's wages can multiply by TEN (from, say $2 per hour to $20 per hour. That's more than I mkae!!), and it'll only resuly in a $1.00 head of lettuce costing $1.45. (.95 + 10 *.05)
SO, these hugely inflated hypothetical prices are all bull.
"The guards even at best buy never bother to inspect your cart because each expensive or routinely stolen item has a deeply embedded rfid tag with a writable (WRITE ONCE) field that "knows" if it has been bought. Everything in your cart gets interrogated when you push it through the doors."
Problem: When an item is returned, how do you change the "WRITE ONCE" field to reflect the item is no longer sold???
Problem: What if someone makes an emitter that set all the "WRITE ONCE" fields to 'sold' as they walk around inside the store? Even if they don't steal any items themselves, it could cause problems.
Problem: I use my own bags to bag my products. My bags are foil-lined. This method is currently used to defeat EAS tags now.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
As other people have pointed out, this purpose is already widely implemented - sans the scary "ID card" moniker - with nary a complaint. So why do the two magical words "ID card" get such knee-jerk reactions?
Because a "National ID Card" would make it VERY easy to track everything you do.
Does that make me paranoid? No. Just realistic.
Right now, there are many many different forms of ID. 50 different State Drivers licenses, US passport, school ID, Birth Certificate, Social Security cards, etc. If Everyone inthe US is forced to have a National ID, then the NID will be used for all those other purposes. The NID will be your school ID. It will BE your Drivers License. It will have a 'smart chip' on it with your Medical data on it, back to your Birth Certificate.
Just swipe the card when entering your classroom (to prove attendance). Just give it to the cop, and let him swipe it to check for Wants and Warrants on you. Just hand it over to anyone who needs proof you were born, and let them swipe it.
It's everything, all in one. And that's scary. What if you lose it? "Duh, apply for a new one!" Using WHAT, exactly, to prove you are who you say you are? "Um, fingerprints?" like you leave around every time you touch something? "Um, iris scans?" SO, now you have me going to a secure goverment facility (can't let my iris scan data loose, you know) to get a new ID? How do I get there? Can't drive. No license. Can't take the bus- no NID to swipe to pay for it.
It's also scary because, since it will be used for EVERYTHING eventually, it'll be possible to construct a log of what people do, just by where they scan their ID. You swipe it on your Digital Cable box to get it to unlock the 'non-child friendly' channels. Like CNN. You swipe it at the gas station to pay for gas. You swipe it at the corner newsstand to pay for your mornign newspaper. You swipe it to get into work. You swipe it at the time clock to get paid. You swipe it to log onto your computer at work. You swipe it to log off for lunch.
Beginning to get the picture?? Since you use ONE card for all of these things, all your swipes can be compiled into one HUGE database. Along with everyone else's data. Who will have access to that data?? The government. It doesn't matter if you think the CURRENT Administration will use this data for good, or for evil. What about the NEXT Administration? And the one after that? Of the one after THAT?? Digital data can be stored indefinately. A man 40 years from now could be running for President, and his opponent could dredge up data from 20 years earlier that shows he deviated from his normal routine once, just as a crime was being comitted. Stalkers could bribe cops to get data on where their victims go. Cops could use the data to arrest YOU because you once got on a bus with an accused terrorist.
You are probably thinking I'm nuts. This kinda stuff won't happen. IT'S HAPPENING RIGHT NOW!* Just not so much, because people don't have a single, National ID card.
And THAT is why people don';t like the National ID.
.
* Several months ago, a man was killed in England. He was coming out of an apartment building that the cops were watching. They followed him, and shot him 8 times in the head when he got onto a subway train. He was NOT a terrorist, he just lived in the same building as someone who was a suspected terrorist. That's ONE example of how you can be considered guilty by simply being NEAR someone. Imagine if the cops could just let the computer match up people and locations, instead of actually having to watch the suspects. How many time were YOU sharing mass transit with a terrorist or criminal this month?
Slashdot Mirror
1: The guy clearly was breathing. It can be seen and heard.
Sheesh. Read some of the other posts here. The cop was kneeling on his neck. They had Pepper-sprayed him, too. He was evidently having trouble breathing. He said "I can't breathe." WHat he meant was "I am having trouble breathing, do to your KNEE on my NECK and the PEPPER-SPRAY you squirted me with." He just chose the more concise way of saying it.
3: Where's the rest of the video? Why was it cut off?
RTFA. It was taken with a camera phone. Those things often have a time limit on how much video they can record at once. 20 seconds sounds about right. (I personally have a digital camera that can record video as well- it can record 20 seconds of 'high' quality, or 80 seconds of 'low' quality at one time.)
I'm not a big fan of the police but this is a bullshit video. It's propaganda designed to manipulate me. Show me the whole video and let me make my own decision.
That WAS the whole video.
That's only if his breathing was cut off completely. If he turned his head, and the cops knee was on the SIDE of his neck, rather than stright against his larynx, then he would be able to breath somewhat, but it might still be difficult.
Also, look a few posts down at what the AC says:
Do you really expect long, drawn out (but technically correct) explaination? "Excuse me officer(s). The physical position I am in, what with your kneeling on my neck and all, combined with the copius amounts of pepper-spray you sprayed me with, added to by the stress of this situation, is making it quite difficult to breathe." Or would you just gasp out"I can't breathe-"?
You forgot:
4) Serpico. He testified against the corrupt cops, and then was left to die when shot during a drug bust. His Fellow Officers refused to call for assistance.
But other than that, you got all the possible types of cops:
1) Criminal cops
2) Cops who know about criminal cops, but do nothing. (They are just as bad, morally.)
3) Cops so stupid/naive that they don't know about type 1 and 2 cops. (Who wants cops THAT dumb on the force??)
4) Cops who are honest (and get left for dead like Serpico).
1. Offender is a known "Gordon Street" gang banger in Los Angeles.
Correction: The cops SAY he is a gang member.
3. Offender was running from the police officers before they had tackled them.
Um, if THIS is what they do to people, is it any wonder people run from them??
4. In the video, you can see the offender grabbing the officer's inner thigh before the officer started to punch the offender.
You forgot to mention the cop was KNEELING ON THE GUYS NECK.
So how is the government to know you bought women's lingerie and not silk bikini briefs for yourself without cooperation from the store?
RFID. If things keep going the way they are going, soon everything you buy will have an RFID tag in it.
So, lingerie fetish - check, was at scene of first murder on night in question? Nope, our CCTV cameras did not show you in the area of the park on the evening of June 21st, guess you're not him.
CCTV cameras are useless for IDing someone. What if the murderer wears a baseball cap, and his face is in shadow? Anyone can wear a baseball cap...
Or, what about this other murder on Downy St? You live alone so your alibi you were at home at that time really doesn't hold well, but wait, our CCTV camera from your street recorded you going into your house at 8pm and you didn't emerge until ten the next morning.
1) See above. CCTV can't tell the difference between me and my neighbor.
2) I could have walked out the BACK DOOR. Or jumped out a window, for that matter.
It's only power against us if there is a reason to do something and they take action. This would require laws. A threat of action through constant surveillance only works on people paranoid about the government to begin with and sure they are doing something wrong, whether it's true or not.
There are different laws in different places. Even in the same place, there are different laws at different times. What is legal today may be illegal tomorrow. What 'todays government' may not care about, 'tomorrows government' may try to wipe out.
Does that sound familiar? Yeah, it's exactly what other pedestrians do when you're walking around in public right now. They see you as you pass by, may turn to look if you're doing something interesting, and if they really want to, follow you for a bit if they wish.
But they don't RECORD. No one gives a flying fuck if they are WATCHED in public- as they say, there is no expectation of privacy in public. But cameras are just SOOOOOO easy to record from. What happens to the recordings? How long are they kept? Who has access to them (legit or not)?
They have something like that already. http://bondedsender.org/ And its a scam ....
Well, my idea is not a scam. It wouldn't be run by one company, it would be a Free, Open Source solution.
Who would control this? Some US goverment agency?
That's the beauty of it- no one needs to 'control' it.
The best way to stop spam is to get people from purchasing crap from spam mailings. Just like JUNK POSTAL MAIL. IMHO
There's a problem with that: I've Never bought anything from a spam email, but I still get spam. I don't know of anyone who has ever bought anything from a spam email, but they still get spam. You see, it only takes literally 1 out of a million people to buy from a spam to make it worthwhile for the spammer to spam. Or, in other words, only 1 in 1,000,000 people respond to spams. That's already a pretty darn low number. I don't really see what can be done to lower that number. And since it's enough to keep the spammers spamming, there will always be spam.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being sen
Exactly- stick the Server (and other networking equipment) in a closet. Preferably one near an outside wall. Run a separate 'window' AC either directly outside thru the wall, or use some ducting to direct the hot air outside. The AC should be enough to keep the closet (and the server in it) nice and cool. If you want to get 'fancy', you can add some ducts and a fan or two that will kick in and circulate the 'normal' air thru the closet during the day, taking advantage of the existing whole-house AC (if it exists). At night, when the 'normal' AC is off, the one you installed for the server closet kicks on as needed.
It's time to put this fucking McDonald's hot coffee case to rest: It's been held up to be a shining beacon of the spurious nature of litigation in America when in FACT it is NOT.
0 _NHBX_U_C_English.pdf ...
Yes, it is.
The facts are: While sitting in the passenger seat of a parked car, Stella placed the cup between her knees and pulled the lid. This caused the cup to tip, and the coffee to spill into her lap.
- The plaintiff suffered 3rd degree burns over parts of her legs that required SKIN GRAFTS.
Appeal to Emotion is not a valid argument. It does not matter how severe the injuries were, since she caused them to herself through her careless handling of the coffee.
- McDonald's executives testified they KNEW their coffee was hot enough to cause 3rd degree burns (burn occur over 130 degree, McDonalds was brewing their coffee as high as 205).
Non-issue- that is the correct brewing temperature. The National Coffee Association backs this up. Also, I have personally found home coffee makers that use that temperature. CHeck out some of their online user manuals. For example:
http://www.bunn.com/pdfs/retail/usecare/38865.000
Pay attention to page 3: "The water is approximately 50F hotter than what's available from your hot water faucet" (most hot water faucets are 140 deg. + 50 = 190!)
and page 7: "BUNN recommends you AVOID:
Re-heating for serving any coffee with a temperature below 175F."
oh- almost forgot page 6: "The patented ready-to-brew reservoir keeps water at the ideal brewing
temperature of approximately 200F."
- McDonald's ignored advice to post warnings about the possibility of burns
Incorrect. McDonlds had a warning on their cups already.
as well has ignore the warnings given to fast food industry as a whole that they were brewing their coffee too hot.
As said above, it is NOT "too hot".
- The evidence showed McDonald's coffee was consistently 20 degrees hotter than the industry average.
So?
The JUDGE AND JURY found McDonald's behaviour reckless, callous, and WILLFUL.
Juries suck. They are extremely easy to sway with emotion, and usually quite easy to confuse with tecnical terms, as well. I was on one that awarded a guy $130,000 for walking in back of a reversing mini-van. They would have 'only' given him $100,000, but one of the jurors pointewd out "His lawyer will take 1/3". Like it's out fucking job to pay his lawyer! (Oh, and did you spot the 5th-grade math error they made??)
More recently, I was on a jury that ended up hung. WHy? Because two minority jurors didn't find the 7 audio- and video-tapes of the (monority, of course) defendant dealing drugs convincing enough, and clung to the weak-ass defense claim, even after they were shown there were holes in it you could throw a drug addict through.
So, it doesn't matter that a jury decided against 'the big evil corporation', and for the 'poor defenseless woman'. It just shows how stupid juries are.
Having the receipt proves nothing.w ay-come-here-and-get-a-receipt-that-shows-you-vote d-the-'right'-way club.
Maybe you swapped receipts with a random person.
Maybe you picked it out of the trash.
Maybe you belong to the If-your-boss-is-pressuring-you-to-vote-a-certain-
A receipt is worse than useless here... you don't WANT people to be able to show the party bosses that they voted the "right way".
Simply make sure the receipt has NO personal information on it. It's proof that someone voted for that candidate, but not that ANY PARTICULAR PERSON voted for that candidate. So, it's useless as 'proof you voted the right way'.
(X) Requires immediate total cooperation from everybody at once
-- That is, without the new SMTP software to support it, it's worthless
There is no new software required. The certification can easily be added as a 'plug in' or option to existing software. People could still use email software that does not include 'certification'- they just would not gain any benefits.
(X) Armies of worm riddled broadband-connected Windows boxes
--It would be trivial for a worm to get it's current IP and use its ISPs mailserver for "smarthosting" outgoing mail. In fact, I think they're already doing it
In which case, the spam emails could be definitively traced back to the server they came from. A complaint is made, and the ISP investigates and cuts off the 'infected' customer's email service (until they clean their box) or a complaint gets sent to their upstream, who will investigate, and possibly revoke the ISP's email certification.
Either no more spam gets sent, or at least it is sent un-certified, which simplifies filtering.
-- You place too much faith in the SPs who will be "Certifying" users to be non-spammers. There are already providers out there offering "bulletproof hosting" and "pink contracts" to spammers for extra money.
And they have to get their Internet Service from somewhere. If their Upstream doesn't certify them, their un-certified emails will easily be filtered, and never seen. If their Upstream is evil and does certify them, then the Certified email from them (the spammer and/or the upstream, and/or everyone else the upstrean serves, depending on how hardcore you want to be) can be blacklisted.
With Certification, all email will come in Either Un-cerified, or Certified. If it's Uncertified, it can be junked, or whitelisted, or handled anyway the receiver wants. (Most peopel will just junk it, I think.) Certified email can be traced to a specific server, which provides a place to complain to if you get spam. If the owner of the server refuses to deal with it, you can go to the company who certified them, and get their email access cut off. Etc.
UUNET
|
Big Regional ISP
|
Local ISP
|
Spammer
If 'Spammer' sends spam, then complain to Spammer. You KNOW the mail came from their server- the encryption involved in the Certification process proves it. If they solve the problem (maybe they were hacked, whatever), then the spam stops.
If Spammer refuses to do anything, then go to Local ISP. Tell then they Certified someone who is spamming, the Spammer refuses to stop. The ISP will revoke Spammers cerification. The spam, while still being sent, is now UN-certified, and will probably not reach anyone. In addition, Spammer can be added to a 'problem user' list, so if they try to change ISPs, their next ISP can be warned about the problem, and refuse to Certify them.
If Local ISP refuses to do anything, Contact Big Regional ISP. Tell them the story: that Spammer is spamming and refuses to stop, and Local ISP is not doing anything. Big Regional ISP can pressure Local ISP by threatening to revoke Local ISP's Certification. If they need to, they can actually revoke it.
Etc.
See how it works? The key to the whole thing is knowing for sure where the spam came from, so you can complain to them, or their upstream. Unlike the current situation, where email addresses can be spoofed, and bots can blast out untraceable spam from residential accounts, this forces everyone with a (certified) email server to BE RESPONSIBLE, or face the consequences. At the same time, ANYONE can still set up a 'hobby' email server that is UN-certified, and send out newsletters, etc., without restriction. They just need to let the receivers know to whitelist them, or their uncertified emails might end up in the trash.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
vacuum cleaner spider
You mean Gas Pump Nozzle Spider.
And I'd buy a [$1.00] coke every single time. Everybody would buy a coke every single time.
And if they charge $3, maybe only half the people would buy one... but they stil make more money.
100 people x $1 = $100
(.5 x 100) x $3 = $150
"Yes, Jimmy, people really do buy spam advertised products"
Fine. Some idiots out there buy vi@gr@ from spam. But I'd be willing to be that damn close to 0% of people WHO ACTIVELY FILTER SPAM buy stuff from spam.
So, who do they try so hard to defeat spam blockers?? Think about it- they are working so very hard in order to make their message reach the very people who specifically try to block it.
Why?
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
And the cops will confiscate it if they find you carrying 'too much' of it. (You have a big wad of cash? MUST be from selling drugs!)
You forgot the part where it was only available "at select LA and San Francisco Toyota dealers".
Now, multiply that by the number of Cities in the USA....
Add in advertising...
and that's a respectable amount of sales.
Them go and pay $68.00 a pound for lettuce and you can't find an asparagus tip or a mushroom for love nor money.
.05)
Picking costs are around 5% of the retail price of the produce. Thet means 95% goes to other things. The picker's wages can multiply by TEN (from, say $2 per hour to $20 per hour. That's more than I mkae!!), and it'll only resuly in a $1.00 head of lettuce costing $1.45. (.95 + 10 *
SO, these hugely inflated hypothetical prices are all bull.
"The guards even at best buy never bother to inspect your cart because each expensive or routinely stolen item has a deeply embedded rfid tag with a writable (WRITE ONCE) field that "knows" if it has been bought. Everything in your cart gets interrogated when you push it through the doors."
Problem: When an item is returned, how do you change the "WRITE ONCE" field to reflect the item is no longer sold???
Problem: What if someone makes an emitter that set all the "WRITE ONCE" fields to 'sold' as they walk around inside the store? Even if they don't steal any items themselves, it could cause problems.
Problem: I use my own bags to bag my products. My bags are foil-lined. This method is currently used to defeat EAS tags now.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
I have a simple, foolproof idea to help eliminate spam.
Email certification.
If you want to be able to send Certified Email (CE), you apply for Certification from the company that gives you internet connectivity. They check you out, and 'Certify' you as being a legitimate emailer (ie: not a spammer). Then, you generate a private/public key pair and give them the public one. In the headers of all your email, is their certification, and an encrypted header line that's createdusing your private key.
When email arrives at the recipients server (or this could be done at the client level, as well), the server sees the certification, and connects to the certifying server to get your public key. It attempts to decrypt the header line. If it does it marks the email as 'certified', if it cannot, it marks the email as 'uncertified', and the email client can be programmed to filter messages based on that.
Due to the public/private key cryptography, there can be no certified email spoofing. (Assuming the private keys are secure, the keys are of decent length, etc.) All emails are traceable back to the originating server. CORRECTION- all CERTIFIED emails are traceable. Anonymous email is still possible. People can still set up email servers for mailing lists without "having" to get them certified. And people can still receive non-certified mail.
If an email server sends out spam, the complaints go to it's certifier. They can drop the certification, deleting the public key from their server. When this happens, ALL the email from the spamming server is now 'uncertified', and gets handled accordingly by email clients. If nothing is done, complaints go to THEIR upstream, etc. Individuals and groups can keep their own blacklists, if they wish, and anyone can choose to filter emails according to those lists.
Now, I've looked over that 'form email' that people like to post to shoot down anti-spam ideas. And nothing applies to this idea. (If something seems to apply, it's because I either left out details, or explained something wrong.) This idea does NOT need to be universally adopted, nor does it need to be adopted by everyone all at once. It's primarily a way of reliably tracing (certified) emails back to their originating server. The anti-spam part comes later: if you receive certified spam, complain and get the server un-certified. If you receive un-certified spam... well, just have your email client dump all uncertified emails in the trash. (Not nessisarilly, you could just use it's un-certifedness as a factor in filtering your email.)
This idea does not require anything be changed with SMTP. It simply requires a second connection be made to the certifying server. Now, before you bitch about the extra bandwidth, I'd like to remind you that, once this idea catches on, spam will be greatly reduced. This reduction will MORE than make up for the slight increase in bandwidth created in querying the certifying servers. Also, the certifying servers can set time limits on when the certifications expire, and need to be re-downloaded (kind of like DHCP leases). A 'new' company that just applied for certification might have it's certificate set to expire almost instantly. This way, every email they send requires a download of the certificate. This allows the certificate to be pulled rapidly if they start spamming. After a month or two, it could be set to expire weekly or monthly.
To sum up: Email Certification is reliable way of tracing the certified emails back to their originating server. This allows spammers to be identified unequivocally, and have their certification pulled. Email servers are NOT required to be certified, and anonymous email is still possible. Email recipients can, if they choose, set up their client to send uncertified emails to the trash, or to handle them however they wish. White lists and black lists are still possible. 'Hobby mailing lists' are still possible, certified or not. The extra bandwidth is minimal, and easily overshadowed by the reduction in spam being send once spammers realize no one is even seeing, much less reading or replying to their spam.
As other people have pointed out, this purpose is already widely implemented - sans the scary "ID card" moniker - with nary a complaint. So why do the two magical words "ID card" get such knee-jerk reactions?
Because a "National ID Card" would make it VERY easy to track everything you do.
Does that make me paranoid? No. Just realistic.
Right now, there are many many different forms of ID. 50 different State Drivers licenses, US passport, school ID, Birth Certificate, Social Security cards, etc. If Everyone inthe US is forced to have a National ID, then the NID will be used for all those other purposes. The NID will be your school ID. It will BE your Drivers License. It will have a 'smart chip' on it with your Medical data on it, back to your Birth Certificate.
Just swipe the card when entering your classroom (to prove attendance). Just give it to the cop, and let him swipe it to check for Wants and Warrants on you. Just hand it over to anyone who needs proof you were born, and let them swipe it.
It's everything, all in one. And that's scary. What if you lose it? "Duh, apply for a new one!" Using WHAT, exactly, to prove you are who you say you are? "Um, fingerprints?" like you leave around every time you touch something? "Um, iris scans?" SO, now you have me going to a secure goverment facility (can't let my iris scan data loose, you know) to get a new ID? How do I get there? Can't drive. No license. Can't take the bus- no NID to swipe to pay for it.
It's also scary because, since it will be used for EVERYTHING eventually, it'll be possible to construct a log of what people do, just by where they scan their ID. You swipe it on your Digital Cable box to get it to unlock the 'non-child friendly' channels. Like CNN. You swipe it at the gas station to pay for gas. You swipe it at the corner newsstand to pay for your mornign newspaper. You swipe it to get into work. You swipe it at the time clock to get paid. You swipe it to log onto your computer at work. You swipe it to log off for lunch.
Beginning to get the picture?? Since you use ONE card for all of these things, all your swipes can be compiled into one HUGE database. Along with everyone else's data. Who will have access to that data?? The government. It doesn't matter if you think the CURRENT Administration will use this data for good, or for evil. What about the NEXT Administration? And the one after that? Of the one after THAT?? Digital data can be stored indefinately. A man 40 years from now could be running for President, and his opponent could dredge up data from 20 years earlier that shows he deviated from his normal routine once, just as a crime was being comitted. Stalkers could bribe cops to get data on where their victims go. Cops could use the data to arrest YOU because you once got on a bus with an accused terrorist.
You are probably thinking I'm nuts. This kinda stuff won't happen. IT'S HAPPENING RIGHT NOW!* Just not so much, because people don't have a single, National ID card.
And THAT is why people don';t like the National ID.
.
* Several months ago, a man was killed in England. He was coming out of an apartment building that the cops were watching. They followed him, and shot him 8 times in the head when he got onto a subway train. He was NOT a terrorist, he just lived in the same building as someone who was a suspected terrorist. That's ONE example of how you can be considered guilty by simply being NEAR someone. Imagine if the cops could just let the computer match up people and locations, instead of actually having to watch the suspects. How many time were YOU sharing mass transit with a terrorist or criminal this month?