The built-in popup blocker is more rigorous than anything else I've seen
The new popups mentioned here aren't blocked at all by the IE SP2 popup blocker. Unfortunately, there is no way to modify what type of popups are blocked by IE. It's either "kinda on" or "completely off".
Zophar and other sites that pop in Firefox seem to be using javascript that traps the click and mouseup methods on all links. If they don't get you when you click, they get you when you let up on the button. Technically, these are user-initiated pops, so FF doesn't block them.
You don't have to kill all allowed events, just hash out click and mouseup.
dom.popup_allowed_events = "change #click dblclick #mouseup reset submit" works well and still alows legitmate popups when you click form buttons and other user-requested behavior.
As always, you can always allow a site you need popups on.
The BOINC versions of Seti@Home and Climateprediction are similar. You can attach to all of them and have the client devide your CPU time any way you want. BOINC also has a folding client (predictor@home), but there's no eye candy.
This quite possibly has a simple explanation if you make a couple of assumptions that have largely been proven:
The quantum states of subatomic particles are entwined with and affect the states of other particles. Essentially, entangled particles are the same particle existing in two or more places at once.
Space and time are relative and functions of each other. Therefore, if a quantum particle or more precisely a unique quantum state can coexist in multiple spatial locations, it most certainly can coexist in multiple temporal locations. The "information" of quantum state changes is transferred between entangled particles instantly and over infinite distances without the use of any matter or energy. Therefore, the domains and constraints of space and time do not apply to quantum information.
Ok, here comes the big assumption: If we assume consciousness is in part a function of quantum states, then consciousness can directly affect the universe without transfer of matter or energy and is not constrained by "real" space or time.
The fact that ordinary random number generators are detecting an anomaly vs. some kind of specialized instrument just contributes more evidence to this theory. "True" random number generators typically work by amplifying and digitizing the static produced in an intentionally noisy circuit. Random electromagnetic energy is essentially the product of random quantum states. If something is influencing those states it will produce a pattern in the randomness.
At the risk of being too vague (much like the article), I get the feeling this law will be used selectively in cases of "I know it when I see it."
There's a big difference between services that COULD be exploited (SSH, AD, VNC), data-miners or adbots (Claria, MyWebSearch) and the real nasties.
Think CoolWebSearch *spit!*, VX2/NicTech and SecondThought. Each of those is considered malicious software in addition to spyware/adware because they install via exploits and use backdoor access to generate revenue.
SecondThought can change your start page to kiddie porn. That is a major liability. CoolWebSearch is next to impossible to remove. VX2 compromises Winlogon: it's a rootkit. The methods by which these things work already fall under the existing definition of computer crime.
Provide information in plain English as to what part of the code the violation occurs in, what might have caused it, and how it may be possibly prevented in the future. If it's possible to take immediate recovery steps, offer to do so.
Offer to inform the developers of their mistake or oversight, and to them provide a detailed technical description of the violation and the steps leading to it, but don't make this last step mandatory. Privacy matters.
Oh... what's that... GPL violation? I thought it said GPF. I have no idea what to do about a GPL violation.
My Panasonic EB-310TX (ATT) nearly blew up in my car. I left it on the cig lighter charger overnight.
Didn't think twice about doing so, cause:
A) It's a genuine Panasonic charger sold to me at an ATTWS store 2) Original Panasonic Li-Ion battery. No 3rd party junk here, and all of about 30 minutes of talk time. D) The AC charger shuts off when the battery is charged.
Apparently the car charger isn't so smart. When I picked up that phone the next morning I dropped it real quick. It was too hot to hold. The battery pack had swelled enough to force it away from the phone body.
Needless to say, the phone was cooked. It would stay operational for all of about 10 seconds before powering off or rebooting. The ATTWS store tried a new battery for me, didn't help.
I ended up getting the Motorola T721. Now this is a nice phone, and I've yet to run down the battery, even after talking on it for 3 hours straight.
My point is, any Lithium/-ion/-polymer battery is made with a very reactive metal. If overcharged, it will get hot and leak gases, and lithium+gases+heat = Boom.
>>..until you can operate the system either by discovering your monitor and listening or by discarding your keyboard and speaking.
>>
>>(This message written using Windows-based speech recognition)
I think HD sizes are what they are today cause modern sizes are multiples of old sizes...
at one point, HDs really were 120,200,500 MB, etc... for MB=1024*1024 bytes.
as drives got bigger and bigger, they wanted tp keep the convention of even sizes... 10,20,40,80,100 GB.... but to do that, they needed to get creative.
Fact is, the actual capacity of a disk is determined by several factors: how many platters, how many tracks, how many sectors per track, how those sectors translate into addressable blocks, what small fraction of the disk may or may not be usable on each unit due to acceptable defects, etc...
In reality, hard drive sizes vary slightly from model to model and unit to unit, all supposedly of the same capacity. The actual capacity probably isn't a number anywhere NEAR an integral X*2^n or X*10^n.
Even with flash disks, calculating capacity from the number of blocks may not be a convenient number.
So, we take the actual or estimated capacity and round to the closest X*10^n that looks good. Exact size down to the byte doesn't matter, drives aren't byte-level addressable.
Memory is still done with X*2^n cause it's byte addressable: The exact amount DOES matter, MUST always be that much on every unit, and has to be added or removed in some 2^n increment.
Now, I do believe HD manufacturers changed from 2^n to 10^n and rounded up to get whole numbers. Remember 1.2, 2.1, 3.2, 4.3 GB drives? That's what you get when you force youself to use powers of 2. If you can only make a good estimate to start with, what do you think looks better, "approximately 96.240 GB" or "100 GB"?
It's not really false advertising when everyone does it the same way. I mean, you're not going to pay more for a "100 GB" drive only to find out it's the same size as the "96 GB" drive that was cheaper. There are no "96 GB" drives.
1) Now every domain resolves. Your own browser has no chance to fail the query gracefully. Verisign has just hijacked whatever browser auto-search you prefer. When browser plugins do this kind of thing it's called spyware. As for timeouts: I watched sitefinder.verisign.com get wedged at least half a dozen times in 2 hours last night. A failure response from your DNS for a TLD should be instantaneous. Waiting for this overburdened verisign machine to time out takes a lot longer. Not to mention DNS caches filling with lots of junk.
2) The page starts with "We can't find..." but then offers a not-so-helpful search field that all the lusers are going to use, and only "sponsored" results are returned, with the top billing given to whoever paid verisign the most. Verisign is holding the web hostage, plain and simple.
3) It appears to be static for now, but if DNS admins get wise to it Verisign will most likely either:
a) sue or block access to the root servers under some bizarre "Root server terms of service" clause
or
b) change it frequently, to lots of different networks, similar to what the RIAA did with their website.
What they don't realize is not everything querying for DNS is going to be fetching HTTP. I wonder how much strange traffic they are getting to that sitefinder box, and how many scripts/apps/daemons/etc are crashing or hanging 'cause of this.
Slashdot Mirror
The process that bootstraps a baby is still the Holy Grail for a lot of geeks.
The built-in popup blocker is more rigorous than anything else I've seen
The new popups mentioned here aren't blocked at all by the IE SP2 popup blocker. Unfortunately, there is no way to modify what type of popups are blocked by IE. It's either "kinda on" or "completely off".
Firefox does have one time popup authorization. When you click the "popup blocked" notification there is a list of recent popups you can choose from.
Zophar and other sites that pop in Firefox seem to be using javascript that traps the click and mouseup methods on all links. If they don't get you when you click, they get you when you let up on the button. Technically, these are user-initiated pops, so FF doesn't block them.
You don't have to kill all allowed events, just hash out click and mouseup.
dom.popup_allowed_events = "change #click dblclick #mouseup reset submit" works well and still alows legitmate popups when you click form buttons and other user-requested behavior.
As always, you can always allow a site you need popups on.
From: webmaster@berkeley.edu
Subject: using BOINC to handle web requests.
Help! Someone put us on Slashdot!
If you want to fold run the predictor@home module as well as E@H.
That's the beauty of BOINC, you can plug in to different projects with the same platform.
Einstein@Home is analyzing data from LIGO.
The kickass OpenGL screensaver it gives you!
The BOINC versions of Seti@Home and Climateprediction are similar.
You can attach to all of them and have the client devide your CPU time any way you want.
BOINC also has a folding client (predictor@home), but there's no eye candy.
This quite possibly has a simple explanation if you make a couple of assumptions that have largely been proven:
The quantum states of subatomic particles are entwined with and affect the states of other particles. Essentially, entangled particles are the same particle existing in two or more places at once.
Space and time are relative and functions of each other. Therefore, if a quantum particle or more precisely a unique quantum state can coexist in multiple spatial locations, it most certainly can coexist in multiple temporal locations. The "information" of quantum state changes is transferred between entangled particles instantly and over infinite distances without the use of any matter or energy. Therefore, the domains and constraints of space and time do not apply to quantum information.
Ok, here comes the big assumption: If we assume consciousness is in part a function of quantum states, then consciousness can directly affect the universe without transfer of matter or energy and is not constrained by "real" space or time.
The fact that ordinary random number generators are detecting an anomaly vs. some kind of specialized instrument just contributes more evidence to this theory. "True" random number generators typically work by amplifying and digitizing the static produced in an intentionally noisy circuit. Random electromagnetic energy is essentially the product of random quantum states. If something is influencing those states it will produce a pattern in the randomness.
At the risk of being too vague (much like the article), I get the feeling this law will be used selectively in cases of "I know it when I see it."
There's a big difference between services that COULD be exploited (SSH, AD, VNC), data-miners or adbots (Claria, MyWebSearch) and the real nasties.
Think CoolWebSearch *spit!*, VX2/NicTech and SecondThought. Each of those is considered malicious software in addition to spyware/adware because they install via exploits and use backdoor access to generate revenue.
SecondThought can change your start page to kiddie porn. That is a major liability. CoolWebSearch is next to impossible to remove. VX2 compromises Winlogon: it's a rootkit. The methods by which these things work already fall under the existing definition of computer crime.
And that is the beauty of SecureIM.
The voting machine I used had this friendly purple gorilla on it that helped me decide who to vote for!
The Piraha tribe in the Amazon has only three words used in counting, that mean one, two, and many.
Geez, what a two-bit language.
what monolith? We didn't see no black 1 x 4 x 9 monolith! Ook.
..the site hasn't suffered a sudden total existance failure yet.
'I clicked on the installer file, and to my horror in 10 seconds the attachment had wiped my entire Home folder!'
...Ten seconds. Feel the raw power of *BSD!
Provide information in plain English as to what part of the code the violation occurs in, what might have caused it, and how it may be possibly prevented in the future.
If it's possible to take immediate recovery steps, offer to do so.
Offer to inform the developers of their mistake or oversight, and to them provide a detailed technical description of the violation and the steps leading to it, but don't make this last step mandatory. Privacy matters.
Oh... what's that... GPL violation? I thought it said GPF. I have no idea what to do about a GPL violation.
Exactly. Under plain-vanilla PPC Linux that cluster would be literally smokin'. The G5's thermal management must be software controlled.
My Panasonic EB-310TX (ATT) nearly blew up in my car. I left it on the cig lighter charger overnight.
Didn't think twice about doing so, cause:
A) It's a genuine Panasonic charger sold to me at an ATTWS store
2) Original Panasonic Li-Ion battery. No 3rd party junk here, and all of about 30 minutes of talk time.
D) The AC charger shuts off when the battery is charged.
Apparently the car charger isn't so smart. When I picked up that phone the next morning I dropped it real quick. It was too hot to hold. The battery pack had swelled enough to force it away from the phone body.
Needless to say, the phone was cooked. It would stay operational for all of about 10 seconds before powering off or rebooting. The ATTWS store tried a new battery for me, didn't help.
I ended up getting the Motorola T721. Now this is a nice phone, and I've yet to run down the battery, even after talking on it for 3 hours straight.
My point is, any Lithium/-ion/-polymer battery is made with a very reactive metal. If overcharged, it will get hot and leak gases, and lithium+gases+heat = Boom.
Go ahead, make your MsCock bigger, we won't mind a bit!
>>..until you can operate the system either by discovering your monitor and listening or by discarding your keyboard and speaking.
>>
>>(This message written using Windows-based speech recognition)
Yup.
I think HD sizes are what they are today cause modern sizes are multiples of old sizes...
at one point, HDs really were 120,200,500 MB, etc... for MB=1024*1024 bytes.
as drives got bigger and bigger, they wanted tp keep the convention of even sizes... 10,20,40,80,100 GB.... but to do that, they needed to get creative.
Fact is, the actual capacity of a disk is determined by several factors: how many platters, how many tracks, how many sectors per track, how those sectors translate into addressable blocks, what small fraction of the disk may or may not be usable on each unit due to acceptable defects, etc...
In reality, hard drive sizes vary slightly from model to model and unit to unit, all supposedly of the same capacity. The actual capacity probably isn't a number anywhere NEAR an integral X*2^n or X*10^n.
Even with flash disks, calculating capacity from the number of blocks may not be a convenient number.
So, we take the actual or estimated capacity and round to the closest X*10^n that looks good. Exact size down to the byte doesn't matter, drives aren't byte-level addressable.
Memory is still done with X*2^n cause it's byte addressable: The exact amount DOES matter, MUST always be that much on every unit, and has to be added or removed in some 2^n increment.
Now, I do believe HD manufacturers changed from 2^n to 10^n and rounded up to get whole numbers. Remember 1.2, 2.1, 3.2, 4.3 GB drives? That's what you get when you force youself to use powers of 2. If you can only make a good estimate to start with, what do you think looks better, "approximately 96.240 GB" or "100 GB"?
It's not really false advertising when everyone does it the same way. I mean, you're not going to pay more for a "100 GB" drive only to find out it's the same size as the "96 GB" drive that was cheaper. There are no "96 GB" drives.
1) Now every domain resolves. Your own browser has no chance to fail the query gracefully. Verisign has just hijacked whatever browser auto-search you prefer. When browser plugins do this kind of thing it's called spyware. As for timeouts: I watched sitefinder.verisign.com get wedged at least half a dozen times in 2 hours last night. A failure response from your DNS for a TLD should be instantaneous. Waiting for this overburdened verisign machine to time out takes a lot longer. Not to mention DNS caches filling with lots of junk. 2) The page starts with "We can't find..." but then offers a not-so-helpful search field that all the lusers are going to use, and only "sponsored" results are returned, with the top billing given to whoever paid verisign the most. Verisign is holding the web hostage, plain and simple. 3) It appears to be static for now, but if DNS admins get wise to it Verisign will most likely either: a) sue or block access to the root servers under some bizarre "Root server terms of service" clause or b) change it frequently, to lots of different networks, similar to what the RIAA did with their website. What they don't realize is not everything querying for DNS is going to be fetching HTTP. I wonder how much strange traffic they are getting to that sitefinder box, and how many scripts/apps/daemons/etc are crashing or hanging 'cause of this.
Wow, I share a birthday with Google. Somehow, that means more to me than any celebrity would.
In one episode, that Bender is powered by a 6502.