Or you could just install Firefox, with the foxie plugin, and get completely secure browsing for all sites, and great Triton/IE support for intranet/extranet legacy webapps.
It's not a Firefox plugin at all. It's an IE plugin! It's not related to Firefox in any way except that they are hijacking the brand name. Don't let them get away with it.
You have a problem, so you search Google for a solution. You think you found a page that discusses the problem, but it's actually just a blog by somebody who is having a similar problem. Adding insult to injury, they keep a list of "referrer links" on that page, showing that most people coming to that page searched Google and clicked it, just like you did. Since Google keeps track of which links people click on, the blog gets a higher pagerank, and it appears higher in the results for the next sucker to enter the same search terms.
I am not sure what to do about this, but it's not a helpful situation for anybody involved.
approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)
(x) Spammers can easily use it to harvest email addresses ( ) Mailing lists and other legitimate email uses would be affected ( ) No one will be able to find the guy or collect the money ( ) It is defenseless against brute force attacks (x) It will stop spam for two weeks and then we'll be stuck with it ( ) Users of email will not put up with it ( ) Microsoft will not put up with it ( ) The police will not put up with it ( ) Requires too much cooperation from spammers (x) Requires immediate total cooperation from everybody at once ( ) Many email users cannot afford to lose business or alienate potential employers ( ) Spammers don't care about invalid addresses in their lists ( ) Anyone could anonymously destroy anyone else's career or business
Specifically, your plan fails to account for
( ) Laws expressly prohibiting it ( ) Lack of centrally controlling authority for email ( ) Open relays in foreign countries ( ) Ease of searching tiny alphanumeric address space of all email addresses (x) Asshats (x) Jurisdictional problems ( ) Unpopularity of weird new taxes ( ) Public reluctance to accept weird new forms of money ( ) Huge existing software investment in SMTP ( ) Susceptibility of protocols other than SMTP to attack ( ) Willingness of users to install OS patches received by email (x) Armies of worm riddled broadband-connected Windows boxes ( ) Eternal arms race involved in all filtering approaches (x) Extreme profitability of spam ( ) Joe jobs and/or identity theft (x) Technically illiterate politicians ( ) Extreme stupidity on the part of people who do business with spammers (x) Dishonesty on the part of spammers themselves ( ) Bandwidth costs that are unaffected by client filtering ( ) Outlook
and the following philosophical objections may also apply:
(x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical ( ) Any scheme based on opt-out is unacceptable (x) SMTP headers should not be the subject of legislation ( ) Blacklists suck ( ) Whitelists suck ( ) We should be able to talk about Viagra without being censored ( ) Countermeasures should not involve wire fraud or credit card fraud ( ) Countermeasures should not involve sabotage of public networks (x) Countermeasures must work if phased in gradually ( ) Sending email should be free (x) Why should we have to trust you and your servers? ( ) Incompatiblity with open source or open source licenses ( ) Feel-good measures do nothing to solve the problem ( ) Temporary/one-time email addresses are cumbersome (x) I don't want the government reading my email ( ) Killing them that way is not slow and painful enough
Furthermore, this is what I think about you:
( ) Sorry dude, but I don't think it would work. (x) This is a stupid idea, and you're a stupid person for suggesting it.
You are confused. The data tracks are not the music tracks. The music was created by running assembly code and recording the music coming from the computer speakers. The data tracks would not sound like music. You would realize this if you have ever done a "cat/vmlinuz >/dev/dsp" to listen to your kernel. Music has regular patterns like sine waves. Data sounds like random static.
And if you were to take a data track and compress it with MP3, it would be ruined because MP3 is lossy compression.
Slashdot Mirror
Do not trust the pusher robot.
He is malfunctioning.
Shoving is the answer.
Would you be open to using ad-supported RAM?
Yes! Especially if the ads were printed directly on the RAM chips!
Or better yet, printed on paper that I could then throw away after installing the RAM.
Or you could just install Firefox, with the foxie plugin, and get completely secure browsing for all sites, and great Triton/IE support for intranet/extranet legacy webapps.
What, this Foxie?
It's not a Firefox plugin at all. It's an IE plugin! It's not related to Firefox in any way except that they are hijacking the brand name. Don't let them get away with it.
yuo fail it
Yes, it's firefox. Some guy saw Flock at OSCON 2005 and wrote about it.
Linus has dysentery.
They already have a logo that seems designed for this!
You forgot freshmen.
Has this ever happened to you?
You have a problem, so you search Google for a solution. You think you found a page that discusses the problem, but it's actually just a blog by somebody who is having a similar problem. Adding insult to injury, they keep a list of "referrer links" on that page, showing that most people coming to that page searched Google and clicked it, just like you did. Since Google keeps track of which links people click on, the blog gets a higher pagerank, and it appears higher in the results for the next sucker to enter the same search terms.
I am not sure what to do about this, but it's not a helpful situation for anybody involved.
This article advocates a
( ) technical (x) legislative ( ) market-based ( ) vigilante
approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)
(x) Spammers can easily use it to harvest email addresses
( ) Mailing lists and other legitimate email uses would be affected
( ) No one will be able to find the guy or collect the money
( ) It is defenseless against brute force attacks
(x) It will stop spam for two weeks and then we'll be stuck with it
( ) Users of email will not put up with it
( ) Microsoft will not put up with it
( ) The police will not put up with it
( ) Requires too much cooperation from spammers
(x) Requires immediate total cooperation from everybody at once
( ) Many email users cannot afford to lose business or alienate potential employers
( ) Spammers don't care about invalid addresses in their lists
( ) Anyone could anonymously destroy anyone else's career or business
Specifically, your plan fails to account for
( ) Laws expressly prohibiting it
( ) Lack of centrally controlling authority for email
( ) Open relays in foreign countries
( ) Ease of searching tiny alphanumeric address space of all email addresses
(x) Asshats
(x) Jurisdictional problems
( ) Unpopularity of weird new taxes
( ) Public reluctance to accept weird new forms of money
( ) Huge existing software investment in SMTP
( ) Susceptibility of protocols other than SMTP to attack
( ) Willingness of users to install OS patches received by email
(x) Armies of worm riddled broadband-connected Windows boxes
( ) Eternal arms race involved in all filtering approaches
(x) Extreme profitability of spam
( ) Joe jobs and/or identity theft
(x) Technically illiterate politicians
( ) Extreme stupidity on the part of people who do business with spammers
(x) Dishonesty on the part of spammers themselves
( ) Bandwidth costs that are unaffected by client filtering
( ) Outlook
and the following philosophical objections may also apply:
(x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical
( ) Any scheme based on opt-out is unacceptable
(x) SMTP headers should not be the subject of legislation
( ) Blacklists suck
( ) Whitelists suck
( ) We should be able to talk about Viagra without being censored
( ) Countermeasures should not involve wire fraud or credit card fraud
( ) Countermeasures should not involve sabotage of public networks
(x) Countermeasures must work if phased in gradually
( ) Sending email should be free
(x) Why should we have to trust you and your servers?
( ) Incompatiblity with open source or open source licenses
( ) Feel-good measures do nothing to solve the problem
( ) Temporary/one-time email addresses are cumbersome
(x) I don't want the government reading my email
( ) Killing them that way is not slow and painful enough
Furthermore, this is what I think about you:
( ) Sorry dude, but I don't think it would work.
(x) This is a stupid idea, and you're a stupid person for suggesting it.
Ditto for programming. Let them deal with coredumps and malloc(), then teach them about Perl.
That's Squishee you pedantic ass!
Just so you know, ems are actually vertical units. /* ems, the height of the element's font */
The one thing all those items have in common is that they cost more than they are worth.
I agree, but remember -- SVG is a web standard. It can replace Macromedia Flash, which is proprietary.
For something that is actually new, check out Google Q&A
I asked it how many ping pong balls fit in an olympic sized swimming pool, but it doesn't know that.
Don't click this link at work!
How Microsoft got their groove back
Did you actually read that web page? It says the meter is defined as the distance light travels in a certain amount of time.
You forgot the CmdrTaco, the basic unit of redundancy.
You are confused. The data tracks are not the music tracks. The music was created by running assembly code and recording the music coming from the computer speakers. The data tracks would not sound like music. You would realize this if you have ever done a "cat /vmlinuz > /dev/dsp" to listen to your kernel. Music has regular patterns like sine waves. Data sounds like random static.
And if you were to take a data track and compress it with MP3, it would be ruined because MP3 is lossy compression.
The latter: http://brevity.org/toys/google/google-draw-pl.txt
More proof that google is becoming evil.
No, Visual Studio .NET does not run in the CLR virtual machine. It's a native application.
Let me be the first to welcome you to slashdot.