If I release a free VoIP app, how could they expect to collect taxes on it? It'd just be sending an audio stream to another computer while at the same time receiving another stream back from that computer. Why tax just one form of two way communication? Especially the one most closely matching resembling speech, as in the free speech guaranteed by the first amendment? They wouldn't tax it just for the money. They'd tax it as a sneaky way to require call logging. Private voice communications would be a form of tax evasion. And by classifying VoIP as a type of telephone communication, they could require that all encrypted VoIP apps support wiretapping.
If they had auto-framerate off, frameskip set to zero, and vsync or triple buffering enabled, as many emulator users do to get the smoothest gameplay, it would have run at whatever is their current refresh rate, maybe 75hz, as opposed to 60hz, unless they took the time to change the default. So they could play a faster game without having intended to do so. Another possible speedup would be using a pal rom instead of an ntsc rom, though their site says that they only allow ntsc.
I doubt they a have desire to claim official speed records, but rather to find the fastest times possible through perfect gameplay. If a recording is found to be fast due to emulator or recording tricks and not because of optimized (slow motion + heavy save state use) gameplay, they'd probably remove it without hesitation.
The original movie file which you could use to verify the speed is at: http://bisqwit.iki.fi/jutut/kuvat/nesvideos/sleepz team-zelda.fmv You'll need an emulator called Famtasia to play it. If it doesn't play back correctly under the default settings, you're probably using a different version of the emulator or they've tweaked it, like increasing the cpu execute % to speed through rarely occuring cpu bound delays.
Tiny sensor (9mm vs 23mm) = less light, increased noise or longer shutter time, and increased blur. Seperate color elements = roughly 1/2 effective resolution.
The result is an image with effectively half the resolution advertised, and less information per pixel due to the signal to noise ratio.
Personally, 2 megapixels with the cheaper sensor is adequate for my non-professional needs.
JPEG2000 is too bulky in my opinion. It's like 20 image formats packed into one, rather than just the cool wavelet format everyone was looking forward to. And it's probably patent encumbered.
We had their implied consent. They knew the world was using JPEG and by not acting to license it for 13 years they've consented to its free use. I'm not saying this legally but ethically, hoping that one day the US will have a government that's concerned for the freedom of its citizens enough to put a stop to the sorts of patent abuse that's destroying our software economy.
Before his death, Leary wrote one last book entitled "Design for Dying" that I found to be a very interesting read, considering that I normally don't read books. I doubt he could have cared less where his ashes went.
It's not like they will be reading your email. It should come as no surprise to privacy advocates that email servers store email, parsing through it every step of the way. It doesn't matter because it's a black box operation. What their web server does with it, like selecting ads more appropriate to my interests, doesn't offend me at all as long as my email doesn't appear before human eyes other than my own.
What should worry privacy advocates is that their email is never encrypted unless they do so manually. It goes across the internet as plain text, and can readily scanned and logged by anyone who wants along the way, like spammers, identity theifs, the government, etc. Most likely your password isn't even encrypted. If you use wireless, most likely that isn't encrypted either. The least of your privacy worries should be GMail deciding that you're interested in enlargement pills and home loans.
It's an interesting way to exchange keys, but does this have any practical use in the field of cryptography? We can already exchange keys very securely, and can do it quickly over any communication medium.
All you need is for some man in the middle to tap the line before you've finished hooking it all up and tested the line conditions, and you probably won't be able to detect it at that point.
As far as speed, both MySQL and Oracle have their place. MySQL has a good price/performance ratio, while Oracle scales well. There are situations where one server with a couple processors and lots of ram just isn't enough for a single database. It could take hundreds of servers, several processors each, sharing hundreds of disks, and Oracle can supposedly handle that fine while still guaranteeing transactional consistency and zero down-time when one of them bites the dust.
It appears he used "alsamixer" to set the volume, but didn't run "alsactl store" to save his configuration. This is an annoying problem for many new Linux users though.
Veteran programmers tend to know all the common mistakes, the proven design strategies, and generally can code anything in a short amount of time and have it be efficient, reliable, scalable, maintainable, and extendable. A two year programmer might know the syntax, and the api's, but usually won't be able to produce good code. Generally, though not certainly, you often end up with something that seems to work, slowly, and fails under any sort of stress. They take 10 times as long to produce anything complex. They code themselves into corners. They can turn anything into spaghetti. They write more code to do less. They spend too much time on the little things. They fail to use all the tools available to them. They may lack business and communication skills. They reinvent the wheel. They're inconsistent. And anyone you bring in to clean up their mess will likely end up rewriting the whole thing anyway.
Not to say that they're useless for coding or that they're all that way, there are certainly a lot of trivial programming tasks out there, but you can't expect the same quality and value hiring underexperienced programmers as with veteran programmers.
Their figure of 28 pieces of spyware per computer considers identifying cookies to be spyware. When counting just spyware programs, the number drops to about 5 per computer. That's still quite high. They didn't need to redefine spyware to include things undeserving of the "-ware" suffix to get their point across.
They hope you're bad at math.
on
Paid To Spam
·
· Score: 2, Informative
At 0.2% CPU usage: 24x365x.002 = $17.52/yr
You can bet they've optimized it for minimal cpu usage, and that it'll suck up nearly all of your bandwidth. You'd be paid about $20 a year for most of what you pay over $300 a yr for. A very raw deal, not to mention the high probability of it getting you in trouble with your isp.
Just get two, maybe even thirty full-time work-at-home jobs. Then outsource them all to India, two workers for each job. They'll work overnight and during the days you take over, inspecting the quality, making sure the style is consistent, and writing out plans for the next night's work.
I'd never do that myself, knowing how it hurts the US job market, but it is a tried and proven strategy for success.
I recently discovered that screensaver.com is distributing screensavers that I wrote with their own custom installer that includes several spyware programs, some of the worst I know of, hijacks their home page, puts advertisement links all over their computers, and requires them to agree to receive spam before they're finally allowed to install my screensaver. I've dropped their affiliate commission and demanded that they stop distribute my screensavers with spyware, particularly because it hurts my reputation and is responsible for some of my support email, but so far no response (I'll give them another day or so). Spyware bundling was not a problem I had anticipated when I wrote the EULA. Next I'll be contacting other authors I who's screensavers are being distributed in this fashion.
We can have more deadly crashes at intersections. Sounds like a bad idea to me. Like Oregon's law that if even your back bumper is in the intersection when the light turns red, you can get a ticket. That causes a lot of deadly accidents too, as yellow lights have not been lengthened to account for the reduced stopping time.
The idea of a master password is nothing new. A lot of pc bioses were like that. It allowed their tech support to easily "recover" a system where the malicious user (like ex-admin or ex-girlfriend) set a random bios password, at the cost of giving a false, but often effective sense of security.
What would happen if a neutron star the size of the moon smacked into the earth at the speed of light?
Inputs: Projectile Diameter: 10000000.00 m = 32800000.00 ft = 6210.00 miles Projectile Density: 80000 kg/m3 (ironx10, probably an underestimate) Impact Velocity: 300000.00 km/s = 186300.00 miles/s (speed of light) Impact Angle: 45 degrees
Output: Energy: 1.88 x 1042 Joules = 4.50 x 1026 MegaTons TNT Transient Crater Diameter: 2897115.48 km = 1799108.71 miles Final Crater Diameter: 20162191.03 km = 12520720.63 miles
Ethereal has easy to use gui. Good for interactive use, like debugging problems or eavesd^H^H^H^H^H^Hjust browsing.
Snort works well for logging, intrusion detection, virus detection, alerts, and with a little extra work, intrusion prevention. It takes some work to set up, but may be worth it.
Slashdot Mirror
If I release a free VoIP app, how could they expect to collect taxes on it? It'd just be sending an audio stream to another computer while at the same time receiving another stream back from that computer. Why tax just one form of two way communication? Especially the one most closely matching resembling speech, as in the free speech guaranteed by the first amendment? They wouldn't tax it just for the money. They'd tax it as a sneaky way to require call logging. Private voice communications would be a form of tax evasion. And by classifying VoIP as a type of telephone communication, they could require that all encrypted VoIP apps support wiretapping.
The code looks so simple, as though .Net did all the work for him. Does this make .Net illegal under the DMCA?
If they had auto-framerate off, frameskip set to zero, and vsync or triple buffering enabled, as many emulator users do to get the smoothest gameplay, it would have run at whatever is their current refresh rate, maybe 75hz, as opposed to 60hz, unless they took the time to change the default. So they could play a faster game without having intended to do so. Another possible speedup would be using a pal rom instead of an ntsc rom, though their site says that they only allow ntsc.
z team-zelda.fmv
I doubt they a have desire to claim official speed records, but rather to find the fastest times possible through perfect gameplay. If a recording is found to be fast due to emulator or recording tricks and not because of optimized (slow motion + heavy save state use) gameplay, they'd probably remove it without hesitation.
The original movie file which you could use to verify the speed is at:
http://bisqwit.iki.fi/jutut/kuvat/nesvideos/sleep
You'll need an emulator called Famtasia to play it. If it doesn't play back correctly under the default settings, you're probably using a different version of the emulator or they've tweaked it, like increasing the cpu execute % to speed through rarely occuring cpu bound delays.
Tiny sensor (9mm vs 23mm) = less light, increased noise or longer shutter time, and increased blur.
Seperate color elements = roughly 1/2 effective resolution.
The result is an image with effectively half the resolution advertised, and less information per pixel due to the signal to noise ratio.
Personally, 2 megapixels with the cheaper sensor is adequate for my non-professional needs.
to everyone who left their bittorrent running. Got an awesome download rate this time.
JPEG2000 is too bulky in my opinion. It's like 20 image formats packed into one, rather than just the cool wavelet format everyone was looking forward to. And it's probably patent encumbered.
We had their implied consent. They knew the world was using JPEG and by not acting to license it for 13 years they've consented to its free use. I'm not saying this legally but ethically, hoping that one day the US will have a government that's concerned for the freedom of its citizens enough to put a stop to the sorts of patent abuse that's destroying our software economy.
I would add:
4) Does not want to break my spirit.
I heard about that.
Before his death, Leary wrote one last book entitled "Design for Dying" that I found to be a very interesting read, considering that I normally don't read books. I doubt he could have cared less where his ashes went.
Don't use it.
It's not like they will be reading your email. It should come as no surprise to privacy advocates that email servers store email, parsing through it every step of the way. It doesn't matter because it's a black box operation. What their web server does with it, like selecting ads more appropriate to my interests, doesn't offend me at all as long as my email doesn't appear before human eyes other than my own.
What should worry privacy advocates is that their email is never encrypted unless they do so manually. It goes across the internet as plain text, and can readily scanned and logged by anyone who wants along the way, like spammers, identity theifs, the government, etc. Most likely your password isn't even encrypted. If you use wireless, most likely that isn't encrypted either. The least of your privacy worries should be GMail deciding that you're interested in enlargement pills and home loans.
With some parallelism, the sky's the limit.
It's an interesting way to exchange keys, but does this have any practical use in the field of cryptography? We can already exchange keys very securely, and can do it quickly over any communication medium.
All you need is for some man in the middle to tap the line before you've finished hooking it all up and tested the line conditions, and you probably won't be able to detect it at that point.
As far as speed, both MySQL and Oracle have their place. MySQL has a good price/performance ratio, while Oracle scales well. There are situations where one server with a couple processors and lots of ram just isn't enough for a single database. It could take hundreds of servers, several processors each, sharing hundreds of disks, and Oracle can supposedly handle that fine while still guaranteeing transactional consistency and zero down-time when one of them bites the dust.
My mod points just expired.
It appears he used "alsamixer" to set the volume, but didn't run "alsactl store" to save his configuration. This is an annoying problem for many new Linux users though.
Veteran programmers tend to know all the common mistakes, the proven design strategies, and generally can code anything in a short amount of time and have it be efficient, reliable, scalable, maintainable, and extendable. A two year programmer might know the syntax, and the api's, but usually won't be able to produce good code. Generally, though not certainly, you often end up with something that seems to work, slowly, and fails under any sort of stress. They take 10 times as long to produce anything complex. They code themselves into corners. They can turn anything into spaghetti. They write more code to do less. They spend too much time on the little things. They fail to use all the tools available to them. They may lack business and communication skills. They reinvent the wheel. They're inconsistent. And anyone you bring in to clean up their mess will likely end up rewriting the whole thing anyway.
Not to say that they're useless for coding or that they're all that way, there are certainly a lot of trivial programming tasks out there, but you can't expect the same quality and value hiring underexperienced programmers as with veteran programmers.
Their figure of 28 pieces of spyware per computer considers identifying cookies to be spyware. When counting just spyware programs, the number drops to about 5 per computer. That's still quite high. They didn't need to redefine spyware to include things undeserving of the "-ware" suffix to get their point across.
At 0.2% CPU usage:
24x365x.002 = $17.52/yr
You can bet they've optimized it for minimal cpu usage, and that it'll suck up nearly all of your bandwidth. You'd be paid about $20 a year for most of what you pay over $300 a yr for. A very raw deal, not to mention the high probability of it getting you in trouble with your isp.
Just get two, maybe even thirty full-time work-at-home jobs. Then outsource them all to India, two workers for each job. They'll work overnight and during the days you take over, inspecting the quality, making sure the style is consistent, and writing out plans for the next night's work.
I'd never do that myself, knowing how it hurts the US job market, but it is a tried and proven strategy for success.
I recently discovered that screensaver.com is distributing screensavers that I wrote with their own custom installer that includes several spyware programs, some of the worst I know of, hijacks their home page, puts advertisement links all over their computers, and requires them to agree to receive spam before they're finally allowed to install my screensaver. I've dropped their affiliate commission and demanded that they stop distribute my screensavers with spyware, particularly because it hurts my reputation and is responsible for some of my support email, but so far no response (I'll give them another day or so). Spyware bundling was not a problem I had anticipated when I wrote the EULA. Next I'll be contacting other authors I who's screensavers are being distributed in this fashion.
We can have more deadly crashes at intersections. Sounds like a bad idea to me. Like Oregon's law that if even your back bumper is in the intersection when the light turns red, you can get a ticket. That causes a lot of deadly accidents too, as yellow lights have not been lengthened to account for the reduced stopping time.
Remove the dashes and you have one of my online passwords. I won't say what it goes to.
The idea of a master password is nothing new. A lot of pc bioses were like that. It allowed their tech support to easily "recover" a system where the malicious user (like ex-admin or ex-girlfriend) set a random bios password, at the cost of giving a false, but often effective sense of security.
What would happen if a neutron star the size of the moon smacked into the earth at the speed of light?
Inputs:
Projectile Diameter: 10000000.00 m = 32800000.00 ft = 6210.00 miles
Projectile Density: 80000 kg/m3 (ironx10, probably an underestimate)
Impact Velocity: 300000.00 km/s = 186300.00 miles/s (speed of light)
Impact Angle: 45 degrees
Output:
Energy: 1.88 x 1042 Joules = 4.50 x 1026 MegaTons TNT
Transient Crater Diameter: 2897115.48 km = 1799108.71 miles
Final Crater Diameter: 20162191.03 km = 12520720.63 miles
We might not make it.
Ethereal has easy to use gui. Good for interactive use, like debugging problems or eavesd^H^H^H^H^H^Hjust browsing.
Snort works well for logging, intrusion detection, virus detection, alerts, and with a little extra work, intrusion prevention. It takes some work to set up, but may be worth it.