And there's a fair amount of consideration given to the keypad tactile feel, given the popularity of text messaging. For example, this model has a contoured key surface for easier touch-typing:
Sorry to say, but Canadians like you really ought to put pressure on the government for allowing nasty oligopolies like Rogers/Telus/Bell to stifle mobile innovation in Canada.
There are three kinds of complaints related to the new Macs. Unfortunately, most of them are red herrings and just end up obscuring the real problems.
1. Aesthetic issues. Staining, mooing, etc. The "whine" could mean poor EMF design, but for now it's just another aesthetic complaint. As others have said, these "problems" are simply amplified by the "pickiness" of Mac users.
2. "Switcher" issues. The Intel Macs have attracted a lot of former Windows users and people who simply haven't upgraded in a while, who clutter the boards with "problems" that are not new, and in many cases workarounds are available when you start doing things the "Mac way". "Heat" complaints go here. Yes, it's hot compared to your old computer. Duh.
3. Serious issues. Exploding/bulging batteries, sudden shutdowns. As I said before, sudden shutdowns don't occur until MONTHS after purchase, so you can pretty much disregard all those people who say "I just bought a MacBook and it works fine!" -- they will not really know until much later.
Just like in SW engineering, there are AESTHETIC "bugs", NON-BUGS, and FATAL bugs. If we want to have a clear discussion about supposed Apple quality control problems, we need to ID the bugs accordingly.
Otherwise we're just weakening our case and making it easier for Apple to ignore the problems. The Ars Technica article doesn't mention the FATALs until the very end. Most readers would probably read about heat and mooing and shrug them off as a bunch of whiny Mac users.
As I said before, you're going to be hearing more about sudden shutdowns...
Apple has a looming disaster on its hands with MacBooks suddenly powering off after a month or two of working just fine. 16000 page views and 500 posts on the support discussion board tell the story: http://discussions.apple.com/thread.jspa?threadID= 544012&tstart=0
This is NOT some whiny cosmetic complaint about stains or "moo"ing or heat. When computers suddenly can't stay on for minutes at a time and require the main logic board to be replaced, it is going to be costly, both for owners and for Apple.
If it's true that they sold a load of MacBooks shortly after intro, they're going to be taking a big hit as these problems surface over the next few weeks.
> In my opinion, errors that can be fixed by a well-known script or program (e.g. indent)
Then why didn't you just run the script on your badly formatted code before you handed it in? Sounds to me like you lost a couple of points are trying to blame the grading scheme after the fact.
Formatting requirements are *not* nitpicky. Wait till you graduate and have to read and extend your coworker's code. Then you will understand why formatting standards are used.
Students always complain about this stuff, but the bottom line is, if you're not comfortable paying attention to details, you should consider sociology or something.
From that point of view, graduate school is getting a PhD. Masters and professional students serve two purposes: fund raising and an outlet for failed/burned out Ph.D. students.
This may be true in some schools in the USA, but it is not true everywhere. There are tonnes of masters degrees, some more research-oriented and others more vocational. It is a big mistake to assume that someone with a masters is either a PhD dropout or someone who paid for a few more letters after their name.
Most of the research universities in Canada, for instance, expect entering PhD candidates to have already earned a master's. As a result, supervisors tend to push their masters students harder than in the States, exposing them to knottier research problems and encouraging them to publish.
Apparently your doctorate didn't teach you not to make generalizations where it's not warranted...
How can an article like this not even mention Wikipedia's various moderation systems?
Of course, if the article itself was editable, someone could go in and fix the omission. But instead we are stuck with Mr. Frank Ahrens' singular agenda of spreading FUD about the whole concept of a community-written reference. Ironic, isn't it?
Cheap hydro power, good net connectivity, and plenty of admin techs... the fact that there aren't huge data centre projects like this in Canada is evidence that the government isn't doing something right.
Instead of powering clusters, all that nice hydroelectricity in BC is being used to grow pot. (which arguably powers a different kind of tech innovation, but anyway...)
Here's the transcript of the video. Note that the audio is out of sync on the BitTorrent version too.
--------- (Dvorak):... there's a formula for pissing off Macintosh users and getting a lot of links or attention. And this has been deconstructed, but never accurately. I'm going to give you the deconstruction.
First, I write something that would be semi-innocuous, with just enough insulting stuff to get a lot of attention from the Macintosh community. So then they would write in -- and by the way, it would always be done in such a way that I had outs -- in other words, I would write in kind of a leisurely way. That would get me one column with a lot of numbers.
Then I'd get a lot of hate mail, and all kinds of weird Macintosh reaction. And then, I would react to it as though I was flabbergasted that everybody misterpreted me, and that they hated it, and I don't get it, and what's wrong with these people... which would piss them off even more.
So I'd get like huge hits...
(Interviewer): So what was the point of all this?
(Dvorak): Now wait a minute. For numbers!
(Interviewer): Which numbers -- exactly, what numbers are you looking for?
(Dvorak): I get them. Believe me. Lots of numbers.
Now, then I let it simmer down for a while, and then whatever position I took originally, I would change the position exactly the opposite, and tell the Macintosh people I was completely wrong, and they were write all along, and the numbers would go through the ceiling!! Haha!
People love USB drives for good reasons. They make the data personal, tangible, an object that follows physical laws that users know intuitively. To an IT person, data is just ones and zeroes in some arbitrary physical medium. But to most users, there is a big difference between that letter you wrote last week disappearing into some network ether, versus residing on a physical USB drive you can hold in your hand.
Most of the comments in this thread are of the "USB drives are a big security hole! Disable them!" variety. What a classic example of IT snobbery. A good administrator, one who understands his users, would stop to think WHY people use USB drives, and try to create a solution that balances the benefits vs. risk to the users.
Along this line of reasoning, an ideal system would be a thin client that accepts USB drives for file storage, automagically backs them up when they are used, and doesn't run any executables other than what's configured. Kind of like the old Sun smart card idea where the user has a physical, tangible ID card where his files conceptually reside.
If you want your users to respect your network security concerns, you first have to try to respect your users.
Headphones, speakers, and amplifiers operate best at certain volume settings, that's why people crank it up -- because the output sounds like crap at low volumes. Unfortunately, these things are specced in terms of things like "watts" and "signal to noise dB" -- all measures that favour high volumes. Even specs like frequency range don't talk about changes in frequency response as you adjust the volume.
Just try searching for audio equipment that produces high-quality sound at relatively low volumes. Good luck! Not even us Slashdotters could find any measure, or review based on such criteria, let alone your average Joe walking into a consumer electronics store where he's encouraged to buy the 300 watt sound system because it's better than the 150 watt one.
Change needs to happen at the manufacturer spec level, and also the audio review level, to take into account the fact that some of us still want clear music without blowing out our ears.
Those of us who weren't hiding under rocks ten years ago remember the days when Sprint distinguished itself as being the "no contract" carrier. Simple, flat rate plans, no crazy cancellation fees, etc. Fido was the same in Canada.
What happened? They wised up and joined the rest of the crowd with their draconian contracts.
+1 to the poster above who pointed out the anti-competitive nature of the wireless market and -1 to the one who said unlocked phones are a solution. Yes, you can buy them, but then you're forefeitting the subsidy that would otherwise be available to you. There are no shortcuts for the consumer. Viva revolucion! The only way out is some kind of intervention.
In other news, Softbank's purchase of Vodafone in Japan should have some nice effects there if they continue to shake things up as they have with Yahoo residential broadband service. Some people say the benefits will expand internationally, but I doubt it unless something is done about the short-term profit minded, lets-find-another-way-to-screw-the-consumer carriers in North America.
I've worked with Shape Memory Alloys (SMAs) before, and they are not like real muscles because, as the article says, they rely on heat to cause contraction. That means you have to wait for them to cool down before they expand again. For lots of applications, including stuff on the time-scale of human movement, cooling doesn't happen fast enough unless you have some kind of active cooling system. Maybe it's possible in the body as long as you don't boil the surrounding fluid (!).
The novelty in this article is not the artificial muscle or the strength of the muscle itself, but the idea of powering (heating) an SMA with a chemical reaction instead of electricity. So the Slashdot headline is a bit misleading...
I was your TA at UBC. The reason is simply that UBC stands for "University of a Billion Chinese" -- as anyone who's been there knows. The proportion of Asian women in computer science is roughly the same as in any other science major at UBC.
That being said, I'm glad UBC's copious efforts to promote gender inclusiveness seem to be paying off.
How many of the people chiming in on this thread have actually USED Dvorak, as opposed to just trying it out and forming some opinion? And what about the original poster's query -- ie, switching back and forth?
So over the past 9 years of Dvorak use I've found myself switching less and less. Here's an estimate of how my Qwerty speed was affected by Dvorak use:
Week 1 - Dvorak 10% of present speed (130 wpm), Qwerty 100% of original (pre-switch) speed (110 wpm)
Week 2 - Dvorak 30%, Qwerty 90%
Month 2 - Dvorak 80%, Qwerty 90%
Year 1 - Dvorak 95%, Qwerty 70%
Year 2 - Dvorak 100%, Qwerty 60%
Year 5 - Dvorak 100%, Qwerty 50%
Year 9 - Dvorak 100%, Qwerty 50%
Something like that. It now takes me longer to get over the "shock" of switching to Qwerty, too, maybe a day instead of 10 minutes...
One option for frequent "switchers" is to use Dvorak for typing, and Qwerty for commands. Mac OS X comes with a "DV - Qwerty command" keymap that lets you keep your muscle memory for all those command (CTRL)-C, V, etc. combinations. And it should be theoretically possible to set this up under Unix with an appropriate xmodmap, too.
As of March 1 there have already been 3 million downloads on 'iPod phones' in Japan. KDDI's "chaku uta full" service is exactly what's being ballyhooed here in the States, and it's been in full operation since November 19, 2004.
Let's get our heads out of the sand, now shall we?
Doing the small tasks first?
on
Getting Things Done
·
· Score: 2, Insightful
"If it takes less than 2-3 minutes, do it right away."
So I've been following such a policy myself, but this ends up having the net effect of putting the small stuff before the big stuff -- one of the big no-nos of time management. At the end of the day, I've gotten a ton of tiny tasks done and a clean to-do list except for the big one that can't be delegated, has to be done, and there isn't enough time left to do.
Does this book address that problem at all? Anybody have any strategies to share?
To answer your question about the Master's in the U.S. versus Canada... I'm an American in a Canadian grad school.
The big difference is that in Canada, people typically finish their Master's before getting a PhD, whereas in the States, they often apply directly to a PhD. Grad school to the PhD level usually takes a few years longer in Canada as a result.
This implies that Canadian schools take their master's students more seriously than U.S. ones, because it's not known whether you'll go further to a PhD (and helping your professor's reputation) or be a so-called "terminal master's" (sounds like a disease doesn't it). In the U.S., since a high percentage of master's students are terminal master's, the professors are less likely to invest as much time and effort into them. In the worst case, the U.S. master's can get seen as a tuition farm or a kind of dumping ground for PhD dropouts, whereas in Canada the master's is seen as a somewhat necessary step along the way to a PhD.
This is talking about research (M.S. or M.Sc.) master's of course. Professional master's degrees are a whole nuther ballgame, and usually involve big tuition in exchange for more job security.
I also use the method of giving out lots of different E-mail addresses to track down who sells my info. Those who say, "you can always turn off the catch-all" are missing the point, because those of us using this method don't usually remember all the addresses we've given out, and therefore, using a "whitelist" isn't practical.
Now, this system works great as others have said. You get a few occasional spams to things like webmaster@, sales@, info@, etc. but those can be easily filtered.
The big problem is with annoying worms that generate random E-mail addresses. Of course, all of them get sent to your catch-all account -- in one day I got 150 Zafi.B worm E-mails from somewhere in Mexico. When you get one of these, what do you do? If you don't bounce the message, it's likely that the randomly generated E-mail address will be treated as valid and added to some spammer's database. Sure, you can blacklist each address, but then you're playing catch-up to a random generator algorithm. Not likely to win at that kind of game.
Anybody know a good way to generate bounce messages in this kind of situation? Most mail bouncers assume you have only one address, and they create dangerous bounce messages that carry your *real* (i.e., desired) return address. I need a bounce script that grabs the "Received from... for ____" header and uses that to generate a bounce as if it originated from the randomly generated E-mail address.
I also use the method of giving out lots of different E-mail addresses to track down who sells my info. Those who say, "you can always turn off the catch-all" are missing the point, because those of us using this method don't usually remember all the addresses we've given out, and therefore, using a "whitelist" isn't practical.
Now, this system works great as others have said. You get a few occasional spams to things like webmaster@, sales@, info@, etc. but those can be easily filtered.
The big problem is with annoying worms that generate random E-mail addresses. Of course, all of them get sent to your catch-all account -- in one day I got 150 Zafi.B worm E-mails from somewhere in Mexico. When you get one of these, what do you do? If you don't bounce the message, it's likely that the randomly generated E-mail address will be treated as valid and added to some spammer's database. Sure, you can blacklist each address, but then you're playing catch-up to a random generator algorithm. Not likely to win at that kind of game.
Anybody know a good way to generate bounce messages in this kind of situation? Most mail bouncers assume you have only one address, and they create dangerous bounce messages that carry your *real* (i.e., desired) return address. I need a bounce script that grabs the "Received from... for ____" header and uses that to generate a bounce as if it originated from the randomly generated E-mail address.
Can anybody help?
PLEASE?
Thanks!
People are talking about this as if it's some kind of simplified data input solution. But phones with cameras are already effective barcode readers and some come with OCR these days... DoCoMo 505i series phones
All without additional hardware. The main advantage of RFID in this case is simply resistance to cloning of the tags. That's why this isn't being marketed as a mass-market feature.
Also, although this is the first READER application, DoCoMo did a pretty widespread trial last year with tags embedded in cell phones for use as train fare debits: Article.
This is more of a consumer application since the infrastructure and user need is already there.
Slashdot Mirror
We've had waterproof phones in Japan for quite some time now. Here's a recent model that's advertised as "if it gets dirty, just wash it."
i /index.html
x .html
http://www.nttdocomo.co.jp/product/foma/703i/f703
And there's a fair amount of consideration given to the keypad tactile feel, given the popularity of text messaging. For example, this model has a contoured key surface for easier touch-typing:
http://mb.softbank.jp/mb/en/product/3g/812sh/inde
Sorry to say, but Canadians like you really ought to put pressure on the government for allowing nasty oligopolies like Rogers/Telus/Bell to stifle mobile innovation in Canada.
Look,
There are three kinds of complaints related to the new Macs. Unfortunately, most of them are red herrings and just end up obscuring the real problems.
1. Aesthetic issues. Staining, mooing, etc. The "whine" could mean poor EMF design, but for now it's just another aesthetic complaint. As others have said, these "problems" are simply amplified by the "pickiness" of Mac users.
2. "Switcher" issues. The Intel Macs have attracted a lot of former Windows users and people who simply haven't upgraded in a while, who clutter the boards with "problems" that are not new, and in many cases workarounds are available when you start doing things the "Mac way". "Heat" complaints go here. Yes, it's hot compared to your old computer. Duh.
3. Serious issues. Exploding/bulging batteries, sudden shutdowns. As I said before, sudden shutdowns don't occur until MONTHS after purchase, so you can pretty much disregard all those people who say "I just bought a MacBook and it works fine!" -- they will not really know until much later.
Just like in SW engineering, there are AESTHETIC "bugs", NON-BUGS, and FATAL bugs. If we want to have a clear discussion about supposed Apple quality control problems, we need to ID the bugs accordingly.
Otherwise we're just weakening our case and making it easier for Apple to ignore the problems. The Ars Technica article doesn't mention the FATALs until the very end. Most readers would probably read about heat and mooing and shrug them off as a bunch of whiny Mac users.
As I said before, you're going to be hearing more about sudden shutdowns...
Apple has a looming disaster on its hands with MacBooks suddenly powering off after a month or two of working just fine. 16000 page views and 500 posts on the support discussion board tell the story:= 544012&tstart=0
http://discussions.apple.com/thread.jspa?threadID
This is NOT some whiny cosmetic complaint about stains or "moo"ing or heat. When computers suddenly can't stay on for minutes at a time and require the main logic board to be replaced, it is going to be costly, both for owners and for Apple.
If it's true that they sold a load of MacBooks shortly after intro, they're going to be taking a big hit as these problems surface over the next few weeks.
> In my opinion, errors that can be fixed by a well-known script or program (e.g. indent)
Then why didn't you just run the script on your badly formatted code before you handed it in? Sounds to me like you lost a couple of points are trying to blame the grading scheme after the fact.
Formatting requirements are *not* nitpicky. Wait till you graduate and have to read and extend your coworker's code. Then you will understand why formatting standards are used.
Students always complain about this stuff, but the bottom line is, if you're not comfortable paying attention to details, you should consider sociology or something.
From that point of view, graduate school is getting a PhD. Masters and professional students serve two purposes: fund raising and an outlet for failed/burned out Ph.D. students.
This may be true in some schools in the USA, but it is not true everywhere. There are tonnes of masters degrees, some more research-oriented and others more vocational. It is a big mistake to assume that someone with a masters is either a PhD dropout or someone who paid for a few more letters after their name.
Most of the research universities in Canada, for instance, expect entering PhD candidates to have already earned a master's. As a result, supervisors tend to push their masters students harder than in the States, exposing them to knottier research problems and encouraging them to publish.
Apparently your doctorate didn't teach you not to make generalizations where it's not warranted...
Mod parent up. That was an awesome post.
And kind of ironic that the author slipped in some unsolicited politically motivated PR on the Falun Gong as part of his/her message.
Of course, if the article itself was editable, someone could go in and fix the omission. But instead we are stuck with Mr. Frank Ahrens' singular agenda of spreading FUD about the whole concept of a community-written reference. Ironic, isn't it?
Cheap hydro power, good net connectivity, and plenty of admin techs ... the fact that there aren't huge data centre projects like this in Canada is evidence that the government isn't doing something right.
Instead of powering clusters, all that nice hydroelectricity in BC is being used to grow pot. (which arguably powers a different kind of tech innovation, but anyway...)
And this is a good thing, because it means more independance from certain CPU architectures.
And in other news, a mysterious link is discovered between bad spelling ("loosing", "independance") and advocating interpreted languages.
Acutally could there be something here? After all, writing native code does demand a greater attention to detail than the quick-and-dirty way...
oops... write --> right in the last paragraph...
Here's the transcript of the video. Note that the audio is out of sync on the BitTorrent version too.
... there's a formula for pissing off Macintosh users and getting a lot of links or attention. And this has been deconstructed, but never accurately. I'm going to give you the deconstruction.
... which would piss them off even more.
...
---------
(Dvorak):
First, I write something that would be semi-innocuous, with just enough insulting stuff to get a lot of attention from the Macintosh community. So then they would write in -- and by the way, it would always be done in such a way that I had outs -- in other words, I would write in kind of a leisurely way. That would get me one column with a lot of numbers.
Then I'd get a lot of hate mail, and all kinds of weird Macintosh reaction. And then, I would react to it as though I was flabbergasted that everybody misterpreted me, and that they hated it, and I don't get it, and what's wrong with these people
So I'd get like huge hits
(Interviewer): So what was the point of all this?
(Dvorak): Now wait a minute. For numbers!
(Interviewer): Which numbers -- exactly, what numbers are you looking for?
(Dvorak): I get them. Believe me. Lots of numbers.
Now, then I let it simmer down for a while, and then whatever position I took originally, I would change the position exactly the opposite, and tell the Macintosh people I was completely wrong, and they were write all along, and the numbers would go through the ceiling!! Haha!
People love USB drives for good reasons. They make the data personal, tangible, an object that follows physical laws that users know intuitively. To an IT person, data is just ones and zeroes in some arbitrary physical medium. But to most users, there is a big difference between that letter you wrote last week disappearing into some network ether, versus residing on a physical USB drive you can hold in your hand.
Most of the comments in this thread are of the "USB drives are a big security hole! Disable them!" variety. What a classic example of IT snobbery. A good administrator, one who understands his users, would stop to think WHY people use USB drives, and try to create a solution that balances the benefits vs. risk to the users.
Along this line of reasoning, an ideal system would be a thin client that accepts USB drives for file storage, automagically backs them up when they are used, and doesn't run any executables other than what's configured. Kind of like the old Sun smart card idea where the user has a physical, tangible ID card where his files conceptually reside.
If you want your users to respect your network security concerns, you first have to try to respect your users.
Just try searching for audio equipment that produces high-quality sound at relatively low volumes. Good luck! Not even us Slashdotters could find any measure, or review based on such criteria, let alone your average Joe walking into a consumer electronics store where he's encouraged to buy the 300 watt sound system because it's better than the 150 watt one.
Change needs to happen at the manufacturer spec level, and also the audio review level, to take into account the fact that some of us still want clear music without blowing out our ears.
What happened? They wised up and joined the rest of the crowd with their draconian contracts.
+1 to the poster above who pointed out the anti-competitive nature of the wireless market and -1 to the one who said unlocked phones are a solution. Yes, you can buy them, but then you're forefeitting the subsidy that would otherwise be available to you. There are no shortcuts for the consumer. Viva revolucion! The only way out is some kind of intervention.
In other news, Softbank's purchase of Vodafone in Japan should have some nice effects there if they continue to shake things up as they have with Yahoo residential broadband service. Some people say the benefits will expand internationally, but I doubt it unless something is done about the short-term profit minded, lets-find-another-way-to-screw-the-consumer carriers in North America.
The novelty in this article is not the artificial muscle or the strength of the muscle itself, but the idea of powering (heating) an SMA with a chemical reaction instead of electricity. So the Slashdot headline is a bit misleading...
By the way, yay, UBC got a plug in the article!
That being said, I'm glad UBC's copious efforts to promote gender inclusiveness seem to be paying off.
So over the past 9 years of Dvorak use I've found myself switching less and less. Here's an estimate of how my Qwerty speed was affected by Dvorak use:
Week 1 - Dvorak 10% of present speed (130 wpm), Qwerty 100% of original (pre-switch) speed (110 wpm)
Week 2 - Dvorak 30%, Qwerty 90%
Month 2 - Dvorak 80%, Qwerty 90%
Year 1 - Dvorak 95%, Qwerty 70%
Year 2 - Dvorak 100%, Qwerty 60%
Year 5 - Dvorak 100%, Qwerty 50%
Year 9 - Dvorak 100%, Qwerty 50%
Something like that. It now takes me longer to get over the "shock" of switching to Qwerty, too, maybe a day instead of 10 minutes...
One option for frequent "switchers" is to use Dvorak for typing, and Qwerty for commands. Mac OS X comes with a "DV - Qwerty command" keymap that lets you keep your muscle memory for all those command (CTRL)-C, V, etc. combinations. And it should be theoretically possible to set this up under Unix with an appropriate xmodmap, too.
Good luck!
See data comparing mobile downloads and iTMS here.
Let's get our heads out of the sand, now shall we?
So I've been following such a policy myself, but this ends up having the net effect of putting the small stuff before the big stuff -- one of the big no-nos of time management. At the end of the day, I've gotten a ton of tiny tasks done and a clean to-do list except for the big one that can't be delegated, has to be done, and there isn't enough time left to do.
Does this book address that problem at all? Anybody have any strategies to share?
You mean, "... to demonstrate that you have a master's NOT because you failed your PhD"?
The big difference is that in Canada, people typically finish their Master's before getting a PhD, whereas in the States, they often apply directly to a PhD. Grad school to the PhD level usually takes a few years longer in Canada as a result.
This implies that Canadian schools take their master's students more seriously than U.S. ones, because it's not known whether you'll go further to a PhD (and helping your professor's reputation) or be a so-called "terminal master's" (sounds like a disease doesn't it). In the U.S., since a high percentage of master's students are terminal master's, the professors are less likely to invest as much time and effort into them. In the worst case, the U.S. master's can get seen as a tuition farm or a kind of dumping ground for PhD dropouts, whereas in Canada the master's is seen as a somewhat necessary step along the way to a PhD.
This is talking about research (M.S. or M.Sc.) master's of course. Professional master's degrees are a whole nuther ballgame, and usually involve big tuition in exchange for more job security.
Now, this system works great as others have said. You get a few occasional spams to things like webmaster@, sales@, info@, etc. but those can be easily filtered.
The big problem is with annoying worms that generate random E-mail addresses. Of course, all of them get sent to your catch-all account -- in one day I got 150 Zafi.B worm E-mails from somewhere in Mexico. When you get one of these, what do you do? If you don't bounce the message, it's likely that the randomly generated E-mail address will be treated as valid and added to some spammer's database. Sure, you can blacklist each address, but then you're playing catch-up to a random generator algorithm. Not likely to win at that kind of game.
Anybody know a good way to generate bounce messages in this kind of situation? Most mail bouncers assume you have only one address, and they create dangerous bounce messages that carry your *real* (i.e., desired) return address. I need a bounce script that grabs the "Received from... for ____" header and uses that to generate a bounce as if it originated from the randomly generated E-mail address.
Can anybody help?
PLEASE?
Thanks!
I also use the method of giving out lots of different E-mail addresses to track down who sells my info. Those who say, "you can always turn off the catch-all" are missing the point, because those of us using this method don't usually remember all the addresses we've given out, and therefore, using a "whitelist" isn't practical. Now, this system works great as others have said. You get a few occasional spams to things like webmaster@, sales@, info@, etc. but those can be easily filtered. The big problem is with annoying worms that generate random E-mail addresses. Of course, all of them get sent to your catch-all account -- in one day I got 150 Zafi.B worm E-mails from somewhere in Mexico. When you get one of these, what do you do? If you don't bounce the message, it's likely that the randomly generated E-mail address will be treated as valid and added to some spammer's database. Sure, you can blacklist each address, but then you're playing catch-up to a random generator algorithm. Not likely to win at that kind of game. Anybody know a good way to generate bounce messages in this kind of situation? Most mail bouncers assume you have only one address, and they create dangerous bounce messages that carry your *real* (i.e., desired) return address. I need a bounce script that grabs the "Received from... for ____" header and uses that to generate a bounce as if it originated from the randomly generated E-mail address. Can anybody help? PLEASE? Thanks!
All without additional hardware. The main advantage of RFID in this case is simply resistance to cloning of the tags. That's why this isn't being marketed as a mass-market feature.
Also, although this is the first READER application, DoCoMo did a pretty widespread trial last year with tags embedded in cell phones for use as train fare debits: Article.
This is more of a consumer application since the infrastructure and user need is already there.