... there was a regular roundabout at the same site before, which was the town's single most accident-prone intersection. The new one, amazingly, greatly reduced accidents. The locals seem to like it, although strangers do tend to be a bit confused the first time they encounter it.
Now where did I put that link...
Re:Has the atmosphere DRASTICALLY changed in 20 yr
on
Beagle 2 Failure Theories
·
· Score: 2, Informative
RTFA. The point is that this data is inaccurate, because the atmosphere shows hitherto-unkown extreme fluctuations of pressure and temperature. It was not a problem for the NASA landers which decelerated on rockets, but it could have been a problem for Beagle since it relied on parachutes to turn a fall into a landing.
2) If I did open-source one of my apps, including this shared code, and contributors submitted changes or patches, any changes to my shared code would end up in my one and only commercial app (since it shares the code.) It's one thing contributing to freeware, and quite another to contribute to an app which is being sold.
Well, since you're the copyright holder, that's not a problem. You can continue to use your shared code in closed applications just as long as you don't use the modifications made by other people (which would be submitted, most likely, under the (L)GPL, or whatever license you chose to publish under). This means, essentially, forking your shared code: One GPL version which the community may alter, and your personal version for use in your closed source apps.
Alternative: Release your shared code as a library under the LGPL. That way, your closed source apps can reap the benefits of community development without them having to be open. Basically, the LGPL states that you may happily link whatever program to the LGPL'd code, it is only the modifications to the LGPL'd code itself that you have to release under the LGPL. That's how its possible for commercial apps to link to the libc.
The national anthem used to be the entire "Lied der Deutschen" until 1990, while only the last (third) verse was sung. In the verge of the unification, the national anthem was changed to be only the third verse.
If you say something that could hurt somebody else, you have to be able to prove it, or stop saying it.
Sucks replying to my own post, but just to clear things up: In Germany, cooperations do not have the same rights as persons, that is, freedom of speech applies much less liberally, especially when infringing on another business.
Yes, it does. E.g., they may not say that Linux contains unlicensed SCO IP prior to this claim being proven in court. Standard procedure in Germany, really: If you say something that could hurt somebody else, you have to be able to prove it, or stop saying it.
Well, it's an out-of-court settlement, so who knows what they paid. And settling out of court is nothing a law system can prevent.
But normally, in Germany, the losing party bears the entire cost of a lawsuit, including the other party's expenses. It's quite common, therefore, to settle out of court when it becomes clear that one side will lose. Normally, the deal is that the losing side sais "we agree to give you what you wanted to get by this lawsuit, in return, you drop it so we have to pay less". This especially makes sense because dropping a lawsuit is orders of magnitudes cheaper than losing one.
Actually, yes, the brain uses a lot of brute force. The CogSci community was long trying to find out how the brain went about recognizing edges and shapes, since computers were so bad and/or slow at it. The answer was somewhat disheartening: The brain uses up to 70% of its capacity (depending on the situation, of course) for optical processing - that is, edge detection, shape detection, movement detection and prediction, filtering of all sorts. That's also (in part) why people close their eyes, unfocus or look at unmoving objects when they're thinking - they're freeing up resources.
Here in Germany, we traditionally have different "area codes" assigned to the different providers. That is, by looking at the area code, you know which provider the mobile is on. This was a good thing, since the cost of calling a mobile depends on the provider (e.g. I refuse to call an O2 mobile before 8 p.m., it's too expensive). With the advent of number portability, this association could get lost. It hasn't yet, since nobody uses it, but the possibility is there. How will I know how expensive my call is going to be?
[...] they did all the work of making the HTML standards compliant, and now they're withholding the patches.
Exactly... They made the page standards compliant. That is, they took the HTML for a particular/. page, and then manually crunched it until the result was a standards-compliant XHTML/CSS page. By doing so, they showed that it is possible to implement/.'s layout in a standards-compliant way and could demonstrate the advantages that this would bring. Nowhere in the article do they say that they changed slash to generate that new markup.
Yes. However, to elaborate my point: Usually such solutions are not implemented on a per-site basis, but in a software package. It then only becomes a matter of gaining access to that database (heck, buy the software) and all sites protected by that package are protected no longer.
That's even simple to enforce. You would have a pool of words, out of which, for every try, a new combination is automatically generated. Problem: Once you are dealing with any kind of dictionnary (as we have here), it can be recreated on the attacker's side - with considerable effort, but with time, this'll get cracked. Only solution is to continuously (sp?) update the database, thus engaging in yet another arms race.
To me, at least, "kostenlos" (literally: without cost) implies really not having any cost at all. That is not true even of most free software: While you have to pay nothing to obtain the software, you still have to administer it, and that costs you. So kostenlos would be TCO==0.
... but I, being a karma whore, will spell it out for you: The LiCo asssigns a unique ID to a registrated user. The registration, however, is only counted in the statistics if the user has logged in during the past year. Hence, to keep being counted, you have to periodically revalidate your registration by logging in or by using a script. This is to weed out inactive users who didn't bother to unregister at LiCo.
The page you go to will usually have two options: "remove me from your list" and "Please continue to alert me of special offers". Select the latter, and submit the form. The e-mail address you substituted into the CGI script will probably start receiving spam real soon.
But as soon as you tell the spammer you want their email, it's not spam anymore, is it?
Slashdot Mirror
... there was a regular roundabout at the same site before, which was the town's single most accident-prone intersection. The new one, amazingly, greatly reduced accidents. The locals seem to like it, although strangers do tend to be a bit confused the first time they encounter it. Now where did I put that link...
RTFA. The point is that this data is inaccurate, because the atmosphere shows hitherto-unkown extreme fluctuations of pressure and temperature. It was not a problem for the NASA landers which decelerated on rockets, but it could have been a problem for Beagle since it relied on parachutes to turn a fall into a landing.
2) If I did open-source one of my apps, including this shared code, and contributors submitted changes or patches, any changes to my shared code would end up in my one and only commercial app (since it shares the code.) It's one thing contributing to freeware, and quite another to contribute to an app which is being sold.
Well, since you're the copyright holder, that's not a problem. You can continue to use your shared code in closed applications just as long as you don't use the modifications made by other people (which would be submitted, most likely, under the (L)GPL, or whatever license you chose to publish under). This means, essentially, forking your shared code: One GPL version which the community may alter, and your personal version for use in your closed source apps.
Alternative: Release your shared code as a library under the LGPL. That way, your closed source apps can reap the benefits of community development without them having to be open. Basically, the LGPL states that you may happily link whatever program to the LGPL'd code, it is only the modifications to the LGPL'd code itself that you have to release under the LGPL. That's how its possible for commercial apps to link to the libc.
The national anthem used to be the entire "Lied der Deutschen" until 1990, while only the last (third) verse was sung. In the verge of the unification, the national anthem was changed to be only the third verse.
If you say something that could hurt somebody else, you have to be able to prove it, or stop saying it.
Sucks replying to my own post, but just to clear things up: In Germany, cooperations do not have the same rights as persons, that is, freedom of speech applies much less liberally, especially when infringing on another business.
The article doesn't mention what they can't say
Yes, it does. E.g., they may not say that Linux contains unlicensed SCO IP prior to this claim being proven in court. Standard procedure in Germany, really: If you say something that could hurt somebody else, you have to be able to prove it, or stop saying it.
Well, it's an out-of-court settlement, so who knows what they paid. And settling out of court is nothing a law system can prevent.
But normally, in Germany, the losing party bears the entire cost of a lawsuit, including the other party's expenses. It's quite common, therefore, to settle out of court when it becomes clear that one side will lose. Normally, the deal is that the losing side sais "we agree to give you what you wanted to get by this lawsuit, in return, you drop it so we have to pay less". This especially makes sense because dropping a lawsuit is orders of magnitudes cheaper than losing one.
Nope. For example, there's a dual-citizenship contract with turkey, and IIRC, it's possible with all EU countries.
Actually, yes, the brain uses a lot of brute force. The CogSci community was long trying to find out how the brain went about recognizing edges and shapes, since computers were so bad and/or slow at it. The answer was somewhat disheartening: The brain uses up to 70% of its capacity (depending on the situation, of course) for optical processing - that is, edge detection, shape detection, movement detection and prediction, filtering of all sorts. That's also (in part) why people close their eyes, unfocus or look at unmoving objects when they're thinking - they're freeing up resources.
well, dear lameness filter, i hvae nothing more to say. let me through already.
Well, X is officially the X Window System. The shorthand XWindows is entirely colloquial.
Ever tried to quote the string, i.e. "I want to find exactly this string"?
Apache can serve asp-pages. And according to Netcraft, Orkut is running Linux.
I know that in days of yore, MENSA used to support Nazi-style politics and "science", but are you some kind of white supremacist?
Mensa (latin: table) is the German word for the university mess hall.
but the Mandrake control center and SuSE YaST seem to do it in a friendlier way.
*pfff* Ever heard of "vim /etc/"?
It'a joke. Laugh.He's only following AAlib. In German small children speak, both A-A and Kacka (or caca, if you will) mean poo or shit.
Here in Germany, we traditionally have different "area codes" assigned to the different providers. That is, by looking at the area code, you know which provider the mobile is on. This was a good thing, since the cost of calling a mobile depends on the provider (e.g. I refuse to call an O2 mobile before 8 p.m., it's too expensive). With the advent of number portability, this association could get lost. It hasn't yet, since nobody uses it, but the possibility is there. How will I know how expensive my call is going to be?
[...] they did all the work of making the HTML standards compliant, and now they're withholding the patches.
Exactly... They made the page standards compliant. That is, they took the HTML for a particular /. page, and then manually crunched it until the result was a standards-compliant XHTML/CSS page. By doing so, they showed that it is possible to implement /.'s layout in a standards-compliant way and could demonstrate the advantages that this would bring. Nowhere in the article do they say that they changed slash to generate that new markup.
Oh pretty, pretty please... What happened to sysadmin?
Yes. However, to elaborate my point: Usually such solutions are not implemented on a per-site basis, but in a software package. It then only becomes a matter of gaining access to that database (heck, buy the software) and all sites protected by that package are protected no longer.
one try would be all that should be allowed
That's even simple to enforce. You would have a pool of words, out of which, for every try, a new combination is automatically generated. Problem: Once you are dealing with any kind of dictionnary (as we have here), it can be recreated on the attacker's side - with considerable effort, but with time, this'll get cracked. Only solution is to continuously (sp?) update the database, thus engaging in yet another arms race.
Why "umsonst" and not "kostenlos" though?
To me, at least, "kostenlos" (literally: without cost) implies really not having any cost at all. That is not true even of most free software: While you have to pay nothing to obtain the software, you still have to administer it, and that costs you. So kostenlos would be TCO==0.
kopete 0.7.2 works just fine.
... but I, being a karma whore, will spell it out for you: The LiCo asssigns a unique ID to a registrated user. The registration, however, is only counted in the statistics if the user has logged in during the past year. Hence, to keep being counted, you have to periodically revalidate your registration by logging in or by using a script. This is to weed out inactive users who didn't bother to unregister at LiCo.
The page you go to will usually have two options: "remove me from your list" and "Please continue to alert me of special offers". Select the latter, and submit the form. The e-mail address you substituted into the CGI script will probably start receiving spam real soon.
But as soon as you tell the spammer you want their email, it's not spam anymore, is it?