There is such a thing though as psychotic depression, which is depression that is severe enough to the point that it actually does cause psychotic symptoms, due to the extreme mood states involved, just like how bipolar disorder, another mood disorder, can very often cause psychosis (albeit usually with bipolar disorder psychosis is caused by extremely high moods rather than extremely low moods, as in the case of psychotic depression). Even though depression and bipolar are both mood disorders, they can cause psychotic symptoms in turn, even though such is more common in the case of bipolar than in the case of depression.
The problem is that neither of these drugs are in practice suitable here. Heroin has too much risk associated with it, even if pharmaceutical-grade and not injected, because the overall effect it produced is too context dependent (which means that people often overdose if they take a dose that they're normally used to, but take it in an unfamiliar environment). Furthermore, heroin makes you more lethargic, not less lethargic, which would definitely be a problem in the case of individuals with depression, as lethargy is one thing that very regularly is a significant part of it. As for marijuana, it can often produce (sometimes quite severe) anxiety and paranoia, especially in individuals who already have preexisting psychological problems. Even though depression itself may not necessary predispose one that much to getting very bad reactions from marijuana, depression is very often comorbid with things like anxiety disorders and like, which aren't necessary diagnosed per se (but that doesn't mean that they aren't there), and anxiety disorders very significantly predispose one to having very adverse reactions to marijuana. And likewise, marijuana is likely to make one more lethargic rather than less, which would not be exactly helpful for individuals with depression.
You obviously don't live in Wisconsin then, I see. Hell, I myself elide the two/b/ phonemes and the intervening vowel in "probably" more often than not. On the other hand, I find variants which elide one but not the other of the/b/ phonemes to sound really strange, and hear them very rarely in general. By the way, where are you located (this might explain this)?
I would not call "prolly" to be a specifically UK variant of "probably" at all. I live in and am from the Upper Midwest region of the US, and it is used very heavily here, to the point that it has pretty much displaced the original word "probably" in most spoken English here except in very formal registers. However, it is still usually written as "probably" except in informal sorts of writing such as chatting and like.
Note that what was referred to is the pronunciation of "probably" in many cases, usually in registers which are not ridiculously formal. Yes, the formal pronunciation of that word does contain two/b/ phonemes, those along with the vowel between them have been elided in many cases in actual speech. These cases are what the spelling "prolly" represents.
The use of + versus +. is necessary in OCaml so that the compiler knows what types to properly infer in an expression. Otherwise, if there are nothing else that provides fixed types in the expression which could help limit the types of other parameters and the result of the expression, then explicit types have to be used to force types to those wanted, which is a major problem in SML, which doesn't use + versus +.
As for the use of let versus let rec, this is necessary as the two scope differently. With let the scope in the function or binding is that before it, whereas with let rec the scope in the function or binding includes the new function or binding. You imply above that let should always have let rec semantics, but this would have the problem that functions could not use previous functions of the same name, and bindings could not refer to previous bindings of the same name, as they would already have themselves in their own scope, which would mask any previous functions or bindings of the same name.
Re:Anyone gotten it to do anything usefull?
on
Freenet 0.5 Released
·
· Score: 1
You should be using fproxy/mainport, which is accessed by default through http://localhost:8888/ (it is accessible as long as your node is fully started up). This is far more useful at the present for actually accessing content in Freenet than Frost, and unlike Frost does not flood Freenet with requests.
Damn, why did OCaml and Scheme have to be left out of the fun of beating the shit out of the evil that is known as XML? Especially considering that OCaml could fuckin annihilate most of the other languages present, except for Lisp and C (and that's just because C does its bidding outside of the world of high level languages); with that in mind, it could really pound the crap out of XML.
This wasn't a node - it was a client library named freenetlib. How do I know this - I was one of its two authors. I've been slowly (I'm often quite busy) working with the other person who worked with me on freenetlib and another person on its successor, Freenet-Python. Freenet-Python was in the recent past ripped apart because the first version of Freenet-Python only supported KSKs and wasn't very easy to use or to extend to support all key types.
bosnia-herzegovina is definitely not anarchy, and iirc somalia is in a state of warlordism. warlordism is *not* anarchy. read some of the writings of Mikhail Bakunin before you try to say that Bosnia-Herzegovina and Somalia are anarchist.
The content cabal will then just try to attack free media and such. They will say that free software is for circumventing copy and access controls and therefore is illegal under the DMCA. Remember that the judges are very unlikely to overturn the DMCA - they've already been bought. Overall, the current system is completely screwed; the only way to really fix it at this point is to destroy it (literally). The politicians and judges have all been bought, and the other side has armies of lawyers at their disposal. It appears that the only way out may be bombing facilities, torching houses, and hauling the executives and lawyers at the base of this along with all the whoring politicians and judges before the wall. This would be quite bloody and violent - but if it is the only way out then it shall be.
There is a specific mechanism in Freenet to handle this exact kind of problem. It is called subspaces. Subspaces give people PK encrypted (anyone who knows of a particular subspace and a file in it can access it, but only one with the proper private key can put files in a particular subspace) private namespaces. Since they're PK encrypted so that only one with the private key can add files to it, you can trust a particular subspace to be safe. It is actually *more* secure than the web - on the web you could theoretically change the packets in HTTP connections on the fly, because normal HTTP connections are not PK encrypted like subspaces are.
Sorry, but files on Freenet are favored not only on popularity but also on *size*. Small files are favored over large files. The main purpose of this is to keep huge unpopular files from wasting gigabytes of space on Freenet, while keeping smaller files such as textfiles and HTML files which are just as unpopular, but don't take up nearly as much space.
KHKs are quite obsolete now (they were the only type of key in Freenet 0.2). They have been superseded by KSKs where the key transmitted is essentially the SHA1 hash of a public key generated from a textual key, and the file is encrypted under the corresponding private key generated from that same textual key.
Mail over Freenet has already been figured out and implemented (not by me - I only designed and created. In-Freenet indices (fnindex), and Freenet newsgroups (fnnews) have already been implemented, but that was in the summer of 2000, and now that everyone is more busy, no one has had the time to reimplement them for Freenet 0.3.
That's why fnnews was created. It hasn't been updated for Freenet 0.3 (I'm very busy and some other people who are thinking of reimplementing it such as Brandon Wiley haven't gotten around to doing so). What it is a Usenet-like enumeration-based newsgroup system. Individual posts are static content, but fnnews newsgroups behave like dynamic content (of course, you have to have a client which supports it - and fnclient hasn't been updated for Freenet 0.3.x). Once fnnews is updated, then Freenet can really have discussion over it. There also is fnindex, IIRC may have been updated by Brandon. It is an index system similar to fnnews except that it is designed for in-Freenet key indices rather than discussion.
Re:Python to perl interpreter
on
Perl 6 Showcase
·
· Score: 1
But why would someone want to convert something to Perl if it is written in a language which is already implemented in a good compiled language like C?
Yeah, but it is much easier to write unmaintainable and generally bad code in Perl than in other languages, such as Python and Scheme.
Re:Python to perl interpreter
on
Perl 6 Showcase
·
· Score: 2
But why would anyone want to interpret Python in Perl?! It would be slower than using real Python or even JPython, and it would convey no advantages. Anyways, why would you want to convert your Python code into Perl. Python is a much nicer language than Perl - I don't think that much would be gained from converting it to Perl.
However, Perl is a very bad language when compared to a clean and simple programming languages like Python, C, and Scheme. And yes, C++ is a pile of bloated crap. That's why I don't use it.
As for VB, that is the beginning language for many people in the *Winblows* world. Perl is the beginning programming language for a lot of kiddies in the Unix/Linux world.
Yes, human stupidity does result in bad programming. However, the way functions are done in Perl is cumbersome and generally bad.
Perl does promote the use of global variables because variables in Perl are global in scope by default. It is better practice to force people to declare stuff as global (like in Python) than to force people to declare stuff local.
I also really dislike Perl. Perl is a badly designed mutant hybrid of bourne shell, sed, awk, and C. Python is a far better scripting language than Perl - it is far cleaner and simpler, it promotes good programming practice, it was well designed from the start instead of being a mishappen pile of hacks, and it IMHO just sucks. I've tried to program nontrivial programs in Perl and it was a major pain in the ass. There are a lot of things which are simple in Python which are a pain in Perl. Object orientation in Perl is poorly designed, function syntax and handling is badly designed, error handling is badly designed, and so on.
Perl: the BASIC of the 90s and the 00s. People should start to learn to program in Python - it is a much better language than Perl and doesn't destroy the minds of beginning coders who hack in it. I'm one of the lucky ones who programmed in old Applesoft BASIC and didn't get their code skills wrecked from the start.
Actually, news capabilities already exist in Freenet do to a Freenet client for Unix/Linux named fnclient (which is written in Python). fnclient (which is admittedly somewhat slow) uses guessable enumerated keys to implement in-Freenet key indices and newsgroups. It is available from http://freenet.sourceforg e.net/contrib/fnclient-0.0.8.tgz. fnclient also can request normal files on Freenet. Note that there is a top-level index at index and a top-level newsgroup index at news/index. These indices are meant to provide master lists of various stuff (news/index is meant to be the primary newsgroup index). Be patient when using indices and newsgroups with fnclient - it is quite slow due to inherent architectural limitations imposed by Freenet 0.2. Note that these will be much faster in the future when searchin appears (which will *not* be Freenet 0.3, or Freenet 0.4).
Note that the bold italics are something that the person that I am responding to is responding to. The italics is the person that I am responding to.
You sure sound like a troll, but I'll bite...
Heh
stop criticizing the very people who are trying to protect your safety even as our civilization is crumbling around us
Yes, our civilization is crumbling about us, but the criminal(s) that we should be worried about is not ordinary criminals, but the government itself.
And you should stop watching crap like America's Most Wanted and read some real statistics for a change. Crime rates are down but this is not being noticed due to the crime hysteria, fed by the law enforcement agency sponsored cop shows and other propaganda.
I agree with you on this point. Stuff like Cops is just pure jingoistic government propaganda
Government is not your enemy, but it is not your friend either.
ONLY CRIMINALS NEED WORRY ABOUT THIS
Ok. You must be a troll. History has proven this claim false so many times that we've lost count.
Not just this, but anyone who doesn't have full support for and loyalty to the government should have the shit scared out of them right now. You should be worried about getting shot by the government death squads which will most surely come our way with the way our country is currently going.
Geez, time zones, daylight savings time, and 12 clocks are incredibly annoying IMHO. I wished the whole world used 24 hour UTC (and I don't live in UK)
Slashdot Mirror
There is such a thing though as psychotic depression, which is depression that is severe enough to the point that it actually does cause psychotic symptoms, due to the extreme mood states involved, just like how bipolar disorder, another mood disorder, can very often cause psychosis (albeit usually with bipolar disorder psychosis is caused by extremely high moods rather than extremely low moods, as in the case of psychotic depression). Even though depression and bipolar are both mood disorders, they can cause psychotic symptoms in turn, even though such is more common in the case of bipolar than in the case of depression.
The problem is that neither of these drugs are in practice suitable here. Heroin has too much risk associated with it, even if pharmaceutical-grade and not injected, because the overall effect it produced is too context dependent (which means that people often overdose if they take a dose that they're normally used to, but take it in an unfamiliar environment). Furthermore, heroin makes you more lethargic, not less lethargic, which would definitely be a problem in the case of individuals with depression, as lethargy is one thing that very regularly is a significant part of it. As for marijuana, it can often produce (sometimes quite severe) anxiety and paranoia, especially in individuals who already have preexisting psychological problems. Even though depression itself may not necessary predispose one that much to getting very bad reactions from marijuana, depression is very often comorbid with things like anxiety disorders and like, which aren't necessary diagnosed per se (but that doesn't mean that they aren't there), and anxiety disorders very significantly predispose one to having very adverse reactions to marijuana. And likewise, marijuana is likely to make one more lethargic rather than less, which would not be exactly helpful for individuals with depression.
You obviously don't live in Wisconsin then, I see. Hell, I myself elide the two /b/ phonemes and the intervening vowel in "probably" more often than not. On the other hand, I find variants which elide one but not the other of the /b/ phonemes to sound really strange, and hear them very rarely in general. By the way, where are you located (this might explain this)?
I would not call "prolly" to be a specifically UK variant of "probably" at all. I live in and am from the Upper Midwest region of the US, and it is used very heavily here, to the point that it has pretty much displaced the original word "probably" in most spoken English here except in very formal registers. However, it is still usually written as "probably" except in informal sorts of writing such as chatting and like.
Note that what was referred to is the pronunciation of "probably" in many cases, usually in registers which are not ridiculously formal. Yes, the formal pronunciation of that word does contain two /b/ phonemes, those along with the vowel between them have been elided in many cases in actual speech. These cases are what the spelling "prolly" represents.
The use of + versus +. is necessary in OCaml so that the compiler knows what types to properly infer in an expression. Otherwise, if there are nothing else that provides fixed types in the expression which could help limit the types of other parameters and the result of the expression, then explicit types have to be used to force types to those wanted, which is a major problem in SML, which doesn't use + versus +.
As for the use of let versus let rec, this is necessary as the two scope differently. With let the scope in the function or binding is that before it, whereas with let rec the scope in the function or binding includes the new function or binding. You imply above that let should always have let rec semantics, but this would have the problem that functions could not use previous functions of the same name, and bindings could not refer to previous bindings of the same name, as they would already have themselves in their own scope, which would mask any previous functions or bindings of the same name.
You should be using fproxy/mainport, which is accessed by default through http://localhost:8888/ (it is accessible as long as your node is fully started up). This is far more useful at the present for actually accessing content in Freenet than Frost, and unlike Frost does not flood Freenet with requests.
Damn, why did OCaml and Scheme have to be left out of the fun of beating the shit out of the evil that is known as XML? Especially considering that OCaml could fuckin annihilate most of the other languages present, except for Lisp and C (and that's just because C does its bidding outside of the world of high level languages); with that in mind, it could really pound the crap out of XML.
This wasn't a node - it was a client library named freenetlib. How do I know this - I was one of its two authors. I've been slowly (I'm often quite busy) working with the other person who worked with me on freenetlib and another person on its successor, Freenet-Python. Freenet-Python was in the recent past ripped apart because the first version of Freenet-Python only supported KSKs and wasn't very easy to use or to extend to support all key types.
bosnia-herzegovina is definitely not anarchy, and iirc somalia is in a state of warlordism. warlordism is *not* anarchy. read some of the writings of Mikhail Bakunin before you try to say that Bosnia-Herzegovina and Somalia are anarchist.
The content cabal will then just try to attack free media and such. They will say that free software is for circumventing copy and access controls and therefore is illegal under the DMCA. Remember that the judges are very unlikely to overturn the DMCA - they've already been bought. Overall, the current system is completely screwed; the only way to really fix it at this point is to destroy it (literally). The politicians and judges have all been bought, and the other side has armies of lawyers at their disposal. It appears that the only way out may be bombing facilities, torching houses, and hauling the executives and lawyers at the base of this along with all the whoring politicians and judges before the wall. This would be quite bloody and violent - but if it is the only way out then it shall be.
The GPL would not be necessary if it wasn't for copyright law.
There is a specific mechanism in Freenet to handle this exact kind of problem. It is called subspaces. Subspaces give people PK encrypted (anyone who knows of a particular subspace and a file in it can access it, but only one with the proper private key can put files in a particular subspace) private namespaces. Since they're PK encrypted so that only one with the private key can add files to it, you can trust a particular subspace to be safe. It is actually *more* secure than the web - on the web you could theoretically change the packets in HTTP connections on the fly, because normal HTTP connections are not PK encrypted like subspaces are.
Sorry, but files on Freenet are favored not only on popularity but also on *size*. Small files are favored over large files. The main purpose of this is to keep huge unpopular files from wasting gigabytes of space on Freenet, while keeping smaller files such as textfiles and HTML files which are just as unpopular, but don't take up nearly as much space.
KHKs are quite obsolete now (they were the only type of key in Freenet 0.2). They have been superseded by KSKs where the key transmitted is essentially the SHA1 hash of a public key generated from a textual key, and the file is encrypted under the corresponding private key generated from that same textual key.
Mail over Freenet has already been figured out and implemented (not by me - I only designed and created. In-Freenet indices (fnindex), and Freenet newsgroups (fnnews) have already been implemented, but that was in the summer of 2000, and now that everyone is more busy, no one has had the time to reimplement them for Freenet 0.3.
That's why fnnews was created. It hasn't been updated for Freenet 0.3 (I'm very busy and some other people who are thinking of reimplementing it such as Brandon Wiley haven't gotten around to doing so). What it is a Usenet-like enumeration-based newsgroup system. Individual posts are static content, but fnnews newsgroups behave like dynamic content (of course, you have to have a client which supports it - and fnclient hasn't been updated for Freenet 0.3.x). Once fnnews is updated, then Freenet can really have discussion over it. There also is fnindex, IIRC may have been updated by Brandon. It is an index system similar to fnnews except that it is designed for in-Freenet key indices rather than discussion.
But why would someone want to convert something to Perl if it is written in a language which is already implemented in a good compiled language like C?
Yeah, but it is much easier to write unmaintainable and generally bad code in Perl than in other languages, such as Python and Scheme.
But why would anyone want to interpret Python in Perl?! It would be slower than using real Python or even JPython, and it would convey no advantages. Anyways, why would you want to convert your Python code into Perl. Python is a much nicer language than Perl - I don't think that much would be gained from converting it to Perl.
However, Perl is a very bad language when compared to a clean and simple programming languages like Python, C, and Scheme. And yes, C++ is a pile of bloated crap. That's why I don't use it.
As for VB, that is the beginning language for many people in the *Winblows* world. Perl is the beginning programming language for a lot of kiddies in the Unix/Linux world.
Yes, human stupidity does result in bad programming. However, the way functions are done in Perl is cumbersome and generally bad.
Perl does promote the use of global variables because variables in Perl are global in scope by default. It is better practice to force people to declare stuff as global (like in Python) than to force people to declare stuff local.
I also really dislike Perl. Perl is a badly designed mutant hybrid of bourne shell, sed, awk, and C. Python is a far better scripting language than Perl - it is far cleaner and simpler, it promotes good programming practice, it was well designed from the start instead of being a mishappen pile of hacks, and it IMHO just sucks. I've tried to program nontrivial programs in Perl and it was a major pain in the ass. There are a lot of things which are simple in Python which are a pain in Perl. Object orientation in Perl is poorly designed, function syntax and handling is badly designed, error handling is badly designed, and so on.
Perl: the BASIC of the 90s and the 00s. People should start to learn to program in Python - it is a much better language than Perl and doesn't destroy the minds of beginning coders who hack in it. I'm one of the lucky ones who programmed in old Applesoft BASIC and didn't get their code skills wrecked from the start.
Actually, news capabilities already exist in Freenet do to a Freenet client for Unix/Linux named fnclient (which is written in Python). fnclient (which is admittedly somewhat slow) uses guessable enumerated keys to implement in-Freenet key indices and newsgroups. It is available from http://freenet.sourceforg e.net/contrib/fnclient-0.0.8.tgz. fnclient also can request normal files on Freenet. Note that there is a top-level index at index and a top-level newsgroup index at news/index. These indices are meant to provide master lists of various stuff (news/index is meant to be the primary newsgroup index). Be patient when using indices and newsgroups with fnclient - it is quite slow due to inherent architectural limitations imposed by Freenet 0.2. Note that these will be much faster in the future when searchin appears (which will *not* be Freenet 0.3, or Freenet 0.4).
Note that the bold italics are something that the person that I am responding to is responding to. The italics is the person that I am responding to.
You sure sound like a troll, but I'll bite...
Heh
stop criticizing the very people who are trying to protect your safety even as our civilization is crumbling around us
Yes, our civilization is crumbling about us, but the criminal(s) that we should be worried about is not ordinary criminals, but the government itself.
And you should stop watching crap like America's Most Wanted and read some real statistics for a change. Crime rates are down but this is not being noticed due to the crime hysteria, fed by the law enforcement agency sponsored cop shows and other propaganda.
I agree with you on this point. Stuff like Cops is just pure jingoistic government propaganda
Government is not your enemy, but it is not your friend either.
ONLY CRIMINALS NEED WORRY ABOUT THIS
Ok. You must be a troll. History has proven this claim false so many times that we've lost count.
Not just this, but anyone who doesn't have full support for and loyalty to the government should have the shit scared out of them right now. You should be worried about getting shot by the government death squads which will most surely come our way with the way our country is currently going.
Geez, time zones, daylight savings time, and 12 clocks are incredibly annoying IMHO. I wished the whole world used 24 hour UTC (and I don't live in UK)