2. RFC 2396 replaces the parts that also defined in RFC 1783, but the definition of specific URL schemes aren't specified in RFC 2396 (BUT makes references to them!), so obvioulsy the RFC 1783 still covers the definition of specific URL schemes.
3. RFC 2396 now allows all URI schemes to use <userinfo>@<host>:<port>.
4. Furthermore is says: "Some URL schemes use the format "user:password" in the userinfo field. This practice is NOT RECOMMENDED, [...]".
Now think. Why does it say "Some URL schemes"? Well, 2.) tells us that RFC 2396 doesn't say which ones do use them and which ones don't. Thats specified in RFC 1738!
We also know from 1.) that e.g. HTTP URL scheme doesn't allow the user:password format!
So in 4.) the words "NOT RECOMMENDED" doesn't apply to HTTP URL in the first place. And I never denied 3.)
Nice wordsmithing though - apparently the Microsoft apologists amongst the moderators bought it
Actually you are much better in wordsmithing than I am!
1. I responded to a post that claimed that according to RFC 1738 the user:pass@host scheme is allowed in combination with http://-URLs. The RFC 1738 doen't allow the use of user:pass@host.
2. You say that RFC 2396 supercedes RFC 1738, but you fail to mention whether this RFC is considered mandatory or not.
3. Even though RFC 2396 supercedes RFC 1738, it still doesn't allow the user:pass@host scheme for http://-URLs. Excerpt from RFC 2396:
Some URL schemes use the format "user:password" in the userinfo
field. This practice is NOT RECOMMENDED, because the passing of
authentication information in clear text (such as URI) has proven to
be a security risk in almost every case where it has been used.
The "some URL schemes" are those defined in RFC 1738 (since there are no definitions of specific URL schemes in this RFC 2396). So user:pass@host is STILL NOT ALLOWED or even mandatory by RFC 2396.
I love people referencing to some RFC, but then not reading it themselves:-P
You said "the user:pass@host" scheme is optional. This is right and wrong. This is described in Section 3.1 of RFC 1738, which describes the Common Internet Scheme Syntax, or the general form that URL can take.
The user:pass@host scheme is described as "optional" in the meaning that specific URL schemes can make use of them or not. A URL scheme can decide not to adopt/allow the 'user:pass@host' scheme at all.
Specific URL schemes for FTP, HTTP, MAILTO etc. are defined in Sections 3.2 - 3.11. These Sections describe what is allowed for each URL scheme (protocol ) and not.
Let's look at HTTP (excerpt from the RFC):
An HTTP URL takes the form:
http://<host>:<port>/<path>?<searchpart>
where and are as described in Section 3.1. If:<port>
is omitted, the port defaults to 80. No user name or password is
allowed.
Also your remark "They're just being dumb. As usual." is wrong. Actually they finally conform to a open specification!
The 5.3 tesla value (and the referenced article) is for the japanese Maglev, which uses supercons (and the 'motor' is inside the train).
The Transrapid only uses conventional electromagnets in the train and tracks, and the motor is actually embedded in the track. IIRC the Transrapid website says that the electromagnetic field inside and outside the train is no concern for the environment, there is only a strong field within a foot-wide area around the magnets.
I'll try to answer some of your questions and comment on some of your statements:
No matter. $5 says that the Archos battery is not anything of any remarkable uniqueness, anyway. The greatest involvement Archos had in the design of this battery was the shape and color of the plastic shell that it comes in[1]. Otherwise, it's just an off-the-shelf part from a catalog, much like the LCD, hard drive, microswitches, DSP, and other comprising hardware. Like these other generic parts, this particular battery is probably used in a number of different products.
Certainly the Archos Li-Ion is not a very special or unique battery. But it is nothing you can get at the supermarket either. Exaclty what you implied: it is not a off-the-shelf part. BTW, did you deliberately skipped my question whether this/these companies will still produce the replacement batteries for the Archos in 5 or 10 years?
1: Do you really think a small company is going to tool up a factory and start making specialized lithium batteries for their miniscule market? Niet.
Usually s.o asks a question, and expects it to be answered.
Anyway, of course I doubt that aswell. But that's why there are standards you can follow/implement. Or form an alliance with a larger company.
2: Of course this costs more than a few 2300mAH AA NiMH cells. It's also more convenient[3][4].
How is it more convenient for the customer to have to order batteries if they are broken? Or even not being able to replace them at all? I'd rather like to be able to go to the shop around the corner to get replacements, at a cheap price. And by the way, you can't make up an new argument by simply referencing other arguments.
3: You do realize that lithium batteries are lighter and more space-efficient than NiMH AAs, don't you? This translates directly to extra space in your pocket.
And you realize that Li-Ion are practically useless after 3 years?
And that Li-Ion batteries can't be used in all applications where NiCd and NiMH-batteries can be used (Heavy-Duty)? IMHO I consider the idea of using Li-Ion batteries in MP3-players not to be a very good one, at least for most cases!
Li-Ion batteries *have* their advantages, but they cannot replace NiMH in every area.
4: And don't say "but I can carry several 2300mAH AA NiMH battery sets and have several times as much runtime!" Who cares? If I'm removed from my usual surroundings long enough that I'm afraid my batteries will die, I'll just plug it in while I sleep. (You do SLEEP, don't you?) This means I'll have to have charging gear, which consumes space, but then so do AAs.
You really don't understand why somebody uses battery-powered portable devices, do you? BTW, this also applies to non-rechargeable batteries: to be able to travel without the need to connect to a power socket. And they would prefer if they could do that as long as possible. Sometimes you just don't have the possibility to recharge batteries for a couple of days, and that's when replaceable batteries come handy.
If you really want to save space, standardize on USB as a charging system for all of your gear[2]. Plug it into the wall, or the car, or even the laptop (if you want to borrow some juice from another big-honkin' Li-ion battery). Do the same with your phone, or anything else that can charge from 5 volts. 2 cables and 2 adapters instead of at least 4 combination units and a USB cable to accomplish the same. USB is, dreadfully, not going away anytime soon - one might as well use it for something.
I'm not primarily interested in (USB) charging systems, or that the device is the smallest and lightest possible when looking for a portable device. It's nice if it has these features, but the most important part is that I can use it (does the job), and use it while travelling, and use it as long as possible!
If I have to open the device to replace batteries, since
Yeah, ONE company that is specialized in manufacturing custom batteries. Do you believe they will still produce this batteries in 5 or even 10 years? I seriously doubt it.
Not to mention that you propably don't have this possibility for no so popular MP3 players!
And come on, $69 for a battery? 4 AA (2300 NiMH) batteries cost FAR less than that, and you still be able to buy AA batteries for the next 20 years.
Yes, there are some (design) problems with Archos FM Recoder.
Probably the most important one is that you can't change the (Li-Ion) batteries. And unfortunately Li-Ion batteries degrade after 2-3 years due to a chemical process, regardless how often you use/recharge the batteries. Look at your mobile telephones, and you know what I mean...
BTW, this problem also affects the Archos 'Recorder V2' (which is basically a FM Recorder without the FM Radio) and the Apple IPod and actually most MP3 Players/Jukeboxes. Don't buy anything that doesn't use ordinary, replaceable AA(A) NiMH-batteries, otherwise you can throw your MP3-Player away after 4 years.
The best (Archos) choice is an old Archos 'Recorder 20', (without FM or V2) which is powered with 4 AA-NiMH-Batteries, graphical b/w display USB 2.0 and Digital/Analog IN/OUT and builtin-MIC. Unfortunately they are rather difficult to get these days, as they were the predecessor of the FM-Recorder and are not officially sold by Archos anymore.
N.B.: the 'Studio' Series is basically a 'Recorder Light', with only USB1.1, no Digita/Analog IN, no MIC, and only a text display (no graphics).
According to the IRC logs of last week some guy claims that he has access to the neccessary docus, but the rockbox-developer don't even consider looking at it, unless they get official permission to use it. They just want to get sure that they don't break any (ie. DMCA) laws.
There very likely existed at some time german physics professors who would speak in nested clauses two or three deep (making note-taking difficult) and this probably gave rise to the [humorous anecdote/urban legend] of the professor who spoke only in one long string of nested sentences.
When I was studying at a german university (until 3 years ago) I had a computer science professor that was still using nested sentences, usually about two or three levels deep.
The unfortunate thing was that the professor often (deliberately or not) forgot to 'pop' the verbs at the end of the mostrous sentence, so you had to figure out what he actually wanted to say.
Mhh, I didn't line up at all (just went there 5mins before the show and STILL got a decent seat). Obviously most people here in Ireland were not really keen in watching the 3rd episode of the Matrix.
I also just paid 4 Euro (not prepaid) which was - in my opinion - a fair price for the movie (I enjoyed the entertainment, but didn't expect much after seeing 'Reloaded'). I would say it IS somehow different than the 2nd one (more action), but the overall atmosphere and quality is the same as Reloaded. No wonder, since both were actually filmed in one go.
If somebody is looking for an final answer/explanation for how the things could have happened as shown in 'Reloaded', well, at least I didn't get it. Revolutions doesn't really clear the confusion the 2nd movie created, and some moves of the character seemed to deliberately even try to confuse you more.
All in all, not bad, but not much better (or worse) than Reloaded.
Arggl, well 36hours and no sleep obvioulsly are not good for me. What I WANTED to write in the parent post was this:
You'll easily get a subnet with a/64-prefix, ie. the first 64bits are fixed, leaving you with 64bit address space to play with. Why 64bit? Because with IPv6 something called EUI-64 (previously EUI-48) is now replacing the use of MAC as a unique identifier. And the/64-prefix (64bit) together with the EUI-64 (also 64bit) is what usually your IPv6 address (128bit) is made of.
Some tunnelbrokers even give you subnets with a/48 prefix, ie. you have a 80bit address space.
If you go an get IPv6 access (via a tunnelbroker like www.freenet6.net) you'll get a/48 ADDRESS, ie. one IPv6 address with a 48bit netmask. But you can easily also get a whole/48 subnet if you want - some tunnelbrokers will give you even a/64 subnet.
Please note that 6bone (prefix 3ffe::) is NOT a production network and was supposed to be shut down (well, it seems it will be still there for a couple of years).
There is also an production network (2001::) that is a little bit more 'organized', ie. you have to register at the RIPE/WHOIS database to be able to be assigned a specific (static) IPv6 address/subnet. Moreover they try to enforce a stable network, ie. PCs with wrong/odd network settings are likely to be permanently disconnected from their tunnelbrokers.
6bone on the other hand is more like a IPv6 playground - you can do whatever you want. It is also likely that your 6bone (3ffe::) addresses might change from time to time. Eg Freenet6 has the policy that your allocated subnet will be re-assigned to other users if you don't use it for more than a week or so.
As long as it's not available from ftp://ftp.kernel.org or http://www.kernel.org, there is no newer version of the linux kernel.
The same applies to the ftp://gcc.gnu.org and GCC (not the website, they are always a little bit lame updating it).
So if you say
'Mandrake has already put the "2.4.21" kernel in their 9.1 release'
your are wrong! They didn't. They lied to you. Or you are mistaken. Or they used a prerelease and renamed it 2.4.21.
And no, 2.4.21 it's not 'too late'. Look at the Changelog and what huge amount of bugfixing has been done. And all those updates to the drivers!
True, 2.6 will feature a log of nice extra stuff, but I guess 99.9% of all linux users are happy with just the features 2.4 has. They simply don't need support for NUMA, 64bit dev_t or Zero-copy NFS.
Hehe, perhaps the 3% you usually use. If I go to the pharmacy and buy 30% H2O2 (70% water) I'm a little bit more careful, because it HURTS when my skin comes in contact with it. Not only that, it gets totally white, like snow, and the skin feels somewhat strange (rough). And I'm not talking about wound here, but healthy skin!
Moreover it's a really good bleach, very good for desinfection and also a good catalyt for some chemical reactions (that's why I buy it).
Slashdot Mirror
No, you missed my point. Maybe this is a little bit easier to understand.
1. Learn to read RFCs.
2. If you are too stupid, try to read and understand my explanation for dummies
3. Yes, I'm indeed in software development.
RFC 2396 allows URIs in the form of @:
... I never denied that! However you missed entirely what I was saying in my last post.
... to be used by the URL schemes. Try learning to read RFCs. I know it can be a little bit confusing...
The user:pass@host scheme is explicitly defined and absoluteley allowed in the URL syntax.
From my previous posts:
1. RFC 1783 says the HTTP URL scheme doesn't allow "user:password".
2. RFC 2396 replaces the parts that also defined in RFC 1783, but the definition of specific URL schemes aren't specified in RFC 2396 (BUT makes references to them!), so obvioulsy the RFC 1783 still covers the definition of specific URL schemes.
3. RFC 2396 now allows all URI schemes to use <userinfo>@<host>:<port>.
4. Furthermore is says: "Some URL schemes use the format "user:password" in the userinfo field. This practice is NOT RECOMMENDED, [...]".
Now think. Why does it say "Some URL schemes"?
Well, 2.) tells us that RFC 2396 doesn't say which ones do use them and which ones don't. Thats specified in RFC 1738!
We also know from 1.) that e.g. HTTP URL scheme doesn't allow the user:password format!
So in 4.) the words "NOT RECOMMENDED" doesn't apply to HTTP URL in the first place.
And I never denied 3.)
Nice wordsmithing though - apparently the Microsoft apologists amongst the moderators bought it
Actually you are much better in wordsmithing than I am!
Bogomips
'nuff said.
2. You say that RFC 2396 supercedes RFC 1738, but you fail to mention whether this RFC is considered mandatory or not.
3. Even though RFC 2396 supercedes RFC 1738, it still doesn't allow the user:pass@host scheme for http://-URLs. Excerpt from RFC 2396:
The "some URL schemes" are those defined in RFC 1738 (since there are no definitions of specific URL schemes in this RFC 2396). So user:pass@host is STILL NOT ALLOWED or even mandatory by RFC 2396.
I love people referencing to some RFC, but then not reading it themselves :-P
:<port>
You said "the user:pass@host" scheme is optional. This is right and wrong. This is described in Section 3.1 of RFC 1738, which describes the Common Internet Scheme Syntax, or the general form that URL can take.
The user:pass@host scheme is described as "optional" in the meaning that specific URL schemes can make use of them or not. A URL scheme can decide not to adopt/allow the 'user:pass@host' scheme at all.
Specific URL schemes for FTP, HTTP, MAILTO etc. are defined in Sections 3.2 - 3.11. These Sections describe what is allowed for each URL scheme (protocol ) and not.
Let's look at HTTP (excerpt from the RFC):
An HTTP URL takes the form:
http://<host>:<port>/<path>?<searchpart>
where and are as described in Section 3.1. If
is omitted, the port defaults to 80. No user name or password is
allowed.
Also your remark "They're just being dumb. As usual." is wrong.
Actually they finally conform to a open specification!
Send donations to:
...
wenNOdoy@SPAMconsolidated.net
I tried to send you some money, but alas "wenNOdoy@SPAMconsolidated.net" is not a registered PayPal user
This looks like the (english?) manual of my 'Made in China' calculator I bought last week ...
Try to press F7 ...
The 5.3 tesla value (and the referenced article) is for the japanese Maglev, which uses supercons (and the 'motor' is inside the train).
The Transrapid only uses conventional electromagnets in the train and tracks, and the motor is actually embedded in the track.
IIRC the Transrapid website says that the electromagnetic field inside and outside the train is no concern for the environment, there is only a strong field within a foot-wide area around the magnets.
I'll try to answer some of your questions and comment on some of your statements:
No matter. $5 says that the Archos battery is not anything of any remarkable uniqueness, anyway. The greatest involvement Archos had in the design of this battery was the shape and color of the plastic shell that it comes in[1]. Otherwise, it's just an off-the-shelf part from a catalog, much like the LCD, hard drive, microswitches, DSP, and other comprising hardware. Like these other generic parts, this particular battery is probably used in a number of different products.
Certainly the Archos Li-Ion is not a very special or unique battery. But it is nothing you can get at the supermarket either. Exaclty what you implied: it is not a off-the-shelf part.
BTW, did you deliberately skipped my question whether this/these companies will still produce the replacement batteries for the Archos in 5 or 10 years?
1: Do you really think a small company is going to tool up a factory and start making specialized lithium batteries for their miniscule market? Niet.
Usually s.o asks a question, and expects it to be answered.
Anyway, of course I doubt that aswell. But that's why there are standards you can follow/implement. Or form an alliance with a larger company.
2: Of course this costs more than a few 2300mAH AA NiMH cells. It's also more convenient[3][4].
How is it more convenient for the customer to have to order batteries if they are broken? Or even not being able to replace them at all? I'd rather like to be able to go to the shop around the corner to get replacements, at a cheap price.
And by the way, you can't make up an new argument by simply referencing other arguments.
3: You do realize that lithium batteries are lighter and more space-efficient than NiMH AAs, don't you? This translates directly to extra space in your pocket.
And you realize that Li-Ion are practically useless after 3 years?
And that Li-Ion batteries can't be used in all applications where NiCd and NiMH-batteries can be used (Heavy-Duty)? IMHO I consider the idea of using Li-Ion batteries in MP3-players not to be a very good one, at least for most cases!
Li-Ion batteries *have* their advantages, but they cannot replace NiMH in every area.
4: And don't say "but I can carry several 2300mAH AA NiMH battery sets and have several times as much runtime!" Who cares? If I'm removed from my usual surroundings long enough that I'm afraid my batteries will die, I'll just plug it in while I sleep. (You do SLEEP, don't you?) This means I'll have to have charging gear, which consumes space, but then so do AAs.
You really don't understand why somebody uses battery-powered portable devices, do you? BTW, this also applies to non-rechargeable batteries: to be able to travel without the need to connect to a power socket. And they would prefer if they could do that as long as possible.
Sometimes you just don't have the possibility to recharge batteries for a couple of days, and that's when replaceable batteries come handy.
If you really want to save space, standardize on USB as a charging system for all of your gear[2]. Plug it into the wall, or the car, or even the laptop (if you want to borrow some juice from another big-honkin' Li-ion battery). Do the same with your phone, or anything else that can charge from 5 volts. 2 cables and 2 adapters instead of at least 4 combination units and a USB cable to accomplish the same. USB is, dreadfully, not going away anytime soon - one might as well use it for something.
I'm not primarily interested in (USB) charging systems, or that the device is the smallest and lightest possible when looking for a portable device. It's nice if it has these features, but the most important part is that I can use it (does the job), and use it while travelling, and use it as long as possible!
If I have to open the device to replace batteries, since
Yeah, ONE company that is specialized in manufacturing custom batteries. Do you believe they will still produce this batteries in 5 or even 10 years? I seriously doubt it.
Not to mention that you propably don't have this possibility for no so popular MP3 players!
And come on, $69 for a battery? 4 AA (2300 NiMH) batteries cost FAR less than that, and you still be able to buy AA batteries for the next 20 years.
Yes, there are some (design) problems with Archos FM Recoder.
...
Probably the most important one is that you can't change the (Li-Ion) batteries. And unfortunately Li-Ion batteries degrade after 2-3 years due to a chemical process, regardless how often you use/recharge the batteries. Look at your mobile telephones, and you know what I mean
BTW, this problem also affects the Archos 'Recorder V2' (which is basically a FM Recorder without the FM Radio) and the Apple IPod and actually most MP3 Players/Jukeboxes. Don't buy anything that doesn't use ordinary, replaceable AA(A) NiMH-batteries, otherwise you can throw your MP3-Player away after 4 years.
The best (Archos) choice is an old Archos 'Recorder 20', (without FM or V2) which is powered with 4 AA-NiMH-Batteries, graphical b/w display USB 2.0 and Digital/Analog IN/OUT and builtin-MIC. Unfortunately they are rather difficult to get these days, as they were the predecessor of the FM-Recorder and are not officially sold by Archos anymore.
N.B.: the 'Studio' Series is basically a 'Recorder Light', with only USB1.1, no Digita/Analog IN, no MIC, and only a text display (no graphics).
According to the IRC logs of last week some guy claims that he has access to the neccessary docus, but the rockbox-developer don't even consider looking at it, unless they get official permission to use it. They just want to get sure that they don't break any (ie. DMCA) laws.
There very likely existed at some time german physics professors who would speak in nested clauses two or three deep (making note-taking difficult) and this probably gave rise to the [humorous anecdote/urban legend] of the professor who spoke only in one long string of nested sentences.
When I was studying at a german university (until 3 years ago) I had a computer science professor that was still using nested sentences, usually about two or three levels deep.
The unfortunate thing was that the professor often (deliberately or not) forgot to 'pop' the verbs at the end of the mostrous sentence, so you had to figure out what he actually wanted to say.
Mhh, I didn't line up at all (just went there 5mins before the show and STILL got a decent seat). Obviously most people here in Ireland were not really keen in watching the 3rd episode of the Matrix.
I also just paid 4 Euro (not prepaid) which was - in my opinion - a fair price for the movie (I enjoyed the entertainment, but didn't expect much after seeing 'Reloaded'). I would say it IS somehow different than the 2nd one (more action), but the overall atmosphere and quality is the same as Reloaded. No wonder, since both were actually filmed in one go.
If somebody is looking for an final answer/explanation for how the things could have happened as shown in 'Reloaded', well, at least I didn't get it. Revolutions doesn't really clear the confusion the 2nd movie created, and some moves of the character seemed to deliberately even try to confuse you more.
All in all, not bad, but not much better (or worse) than Reloaded.
Arggl, well 36hours and no sleep obvioulsly are not good for me. What I WANTED to write in the parent post was this:
/64-prefix, ie. the first 64bits are fixed, leaving you with 64bit address space to play with. Why 64bit? Because with IPv6 something called EUI-64 (previously EUI-48) is now replacing the use of MAC as a unique identifier. And the /64-prefix (64bit) together with the EUI-64 (also 64bit) is what usually your IPv6 address (128bit) is made of.
/48 prefix, ie. you have a 80bit address space.
You'll easily get a subnet with a
Some tunnelbrokers even give you subnets with a
If you go an get IPv6 access (via a tunnelbroker like www.freenet6.net) you'll get a /48 ADDRESS, ie. one IPv6 address with a 48bit netmask. But you can easily also get a whole /48 subnet if you want - some tunnelbrokers will give you even a /64 subnet.
Please note that 6bone (prefix 3ffe::) is NOT a production network and was supposed to be shut down (well, it seems it will be still there for a couple of years).
There is also an production network (2001::) that is a little bit more 'organized', ie. you have to register at the RIPE/WHOIS database to be able to be assigned a specific (static) IPv6 address/subnet. Moreover they try to enforce a stable network, ie. PCs with wrong/odd network settings are likely to be permanently disconnected from their tunnelbrokers.
6bone on the other hand is more like a IPv6 playground - you can do whatever you want. It is also likely that your 6bone (3ffe::) addresses might change from time to time. Eg Freenet6 has the policy that your allocated subnet will be re-assigned to other users if you don't use it for more than a week or so.
Oh no!
Now I'm trapped in an endless recursion!
Chill dude ...
Thanks. I needed that!
It's Friday, 13th, you know
No this was done after SCO was bitching about Linux. Here an explanation what it actually does:
> o [Bluetooth] Use very short disconnect timeout for SCO connections.
The timeout is actually 0 seconds. Once a connection with a SCO machine is already established, kill it immeadiately! We don't like SCO!
> o [Bluetooth] Kill incoming SCO connection when SCO socket is closed.
The socket is closed by default. So this actually means, never accept new connections from SCO machines!
> o [Bluetooth] Support for SCO (voice) over HCI USB
This allows using your USB Modem to call and harass the SCO support center.
(Note for SCO employees: don't take this post too seriously)
I can't believe some still don't get this:
As long as it's not available from ftp://ftp.kernel.org or http://www.kernel.org, there is no newer version of the linux kernel.
The same applies to the ftp://gcc.gnu.org and GCC (not the website, they are always a little bit lame updating it).
So if you say
'Mandrake has already put the "2.4.21" kernel in their 9.1 release'
your are wrong! They didn't. They lied to you. Or you are mistaken. Or they used a prerelease and renamed it 2.4.21.
And no, 2.4.21 it's not 'too late'. Look at the Changelog and what huge amount of bugfixing has been done. And all those updates to the drivers!
True, 2.6 will feature a log of nice extra stuff, but I guess 99.9% of all linux users are happy with just the features 2.4 has. They simply don't need support for NUMA, 64bit dev_t or Zero-copy NFS.
Unfortunately the most important part of the source code is missing ...
... but here you go:
WorldWideWeb homepage
original WorldWideWeb docu
WorldWideWeb source code
Yes, indeed. See the Plan9 FAQfrom comp.os.plan9.
Hehe, perhaps the 3% you usually use. If I go to the pharmacy and buy 30% H2O2 (70% water) I'm a little bit more careful, because it HURTS when my skin comes in contact with it. Not only that, it gets totally white, like snow, and the skin feels somewhat strange (rough). And I'm not talking about wound here, but healthy skin! Moreover it's a really good bleach, very good for desinfection and also a good catalyt for some chemical reactions (that's why I buy it).