Activity Feed
#5203·Tyler MillsOP, 22 days agoStandard melatonin backfires, causing me (and at least one other person I know) to wake up at around hour 5 after falling asleep (maybe when it has finished metabolizing). This is bad, especially if it means you cannot fall back asleep (as in my case, more than half the time).
Time-release melatonin has solved the backfire problem for me. But I don't want to be dependent on it forever to get a good 8 hours.
Standard melatonin backfires, causing me (and at least one other person I know) to wake up at around hour 5 after falling asleep (maybe when it has finished metabolizing). This is bad, especially if it means you cannot fall back asleep (as in my case, more than half the time).
#5201·Tyler MillsOP, 22 days agoFalling asleep has been a lifelong challenge for me. I suspect there is a "preference fight" going on, among other things, keeping my thoughts highly active.
I am sometimes physically tired by hour 16 of the day, but I can easily stay up and continue working to hour 18 or 20. I have no caffeine or nighttime sugar.
Sleep is a challenge for many, including me. Let's see what we know.
Falling asleep has been a lifelong challenge for me. I suspect there is a "preference fight" going on, among other things, keeping my thoughts highly active.
#5139·Tyler MillsOP, about 1 month agoThe capital allocated to a business is non-specific to its content? Conflating with the prices of a good?
The capital a business receives from a buyer is feedback that is non-specific to the content of the product or the business which produced it. It's not knowledge bearing. It's a fungible, universal form of feedback, like energy -- and like the number of instances of a replicator..?
#5182·Tyler MillsOP, 30 days agoSo reach should only ever be invoked with respect to existing knowledge? So a program's reach is the intersection of its codomain and the solutions to known problems.
The appropriate term is range, not codomain. Correcting that and the redundancy per #5189: A program's reach is the intersection of its range and the solutions to current problems.
Fun question. Say the reach of a program is the set of all problems it can solve or help solve (whether anyone knows, or whether the problems exist yet). All of that program's possible outputs together comprise the implication space -- it sounds like "codomain" is actual term. The instantiation of each item in the codomain is an occurrence of my "inferential novelty". The codomain is implicit in a program when it is created, but not all of that output will help solve problems. The program's reach is the subset that does.
Fun question. Say the reach of a program is the set of all problems it can solve or help solve (whether anyone knows, or whether the problems exist yet). All of that program's possible outputs together comprise the implication space -- it sounds like "range" is the actual term. The instantiation of each item in the range is an occurrence of my "inferential novelty". The range is implicit in a program when it is created, but not all of that output will help solve problems. The program's reach is the subset that does.
#5182·Tyler MillsOP, 30 days agoSo reach should only ever be invoked with respect to existing knowledge? So a program's reach is the intersection of its codomain and the solutions to known problems.
I think all problems are known, so we can just say "solutions to problems."
A problem is a conflict between theories, meaning it relates to knowledge currently instantiated.
#5163·Dennis Hackethal, about 1 month agoDid you know you can type em dashes (on Mac) by hitting alt + shift + hyphen?
I'm on PC, and alt+shift+hyphen does not work—but alt+0151 on numpad does... which is a very Windows way to do it, but I'll take it.
#5186·Tyler MillsOP, 23 days agoThis framing seems good, sure. So what does "critical" really mean?
Does it mean: "Can change an existing thing"..? But that criticism program is dogmatic w.r.t. itself, isn't it? This is the whole question, here (or I'm confused), in your terms:
Can criticism, the variation of a dogmatic program, only happen at the hands of another dogmatic program? There's only "externally facing" criticism..? There are no critical programs? Only dogmatic ones criticizing other dogmatic ones.
But then there would need to be a preprogrammed dogmatic program at the bottom. (Or would there..?)
#5174·Dennis Hackethal, about 1 month agoWould it help to distinguish between dogmatic vs. critical information processing?
That’s a distinction I’ve been using. All programs written to date are dogmatic. Whereas a genuine evolutionary algorithm would be critical, at least in part.
We don’t know how to write critical code. We only know how to write dogmatic code that looks critical.
This framing seems good, sure. So what does "critical" really mean?
Does it mean: "Can change an existing thing"..? But that criticism program is dogmatic w.r.t. itself, isn't it? This is the whole question, here (or I'm confused), in your terms:
Can criticism, the variation of a dogmatic program, only happen at the hands of another dogmatic program? There's only "externally facing" criticism..? There are no critical programs? Only dogmatic ones criticizing other dogmatic ones.
#5084·Dennis HackethalOP, about 1 month agoNow also available on PhilPapers: https://philpapers.org/archive/HACTSO-6.pdf
I’ve been using Spotify for over a decade.
Every few months I try Apple Music only to run into bugs and switch back.
But this most recent switch is actually decent.
Transferring my favorited songs from Spotify finally worked.
AutoMix song transitions are fantastic.
Spatial Audio is a win.
Fingers crossed I won’t have a reason to return to Spotify this time.
#5183·Dennis HackethalOP, 29 days ago@edwin-de-wit recently asked Deutsch about this:
… hard to vary can also be a property that you don’t want. Sometimes they say that complicated systems are just so entangled that they’re no longer changeable. You could call that hard to vary but it’s not a property you pursue.
Deutsch’s reply:
Quite so. So hard to vary is about explanations, not about end products. So the end product should be easy to vary, if you want to. But it should be hard to vary in the sense that you don’t want to.
Explanations are functions. In other words, explanations are software. There’s no sharp distinction between explanations and end products here. So the concern about tight coupling still applies.
#3718·Dennis HackethalOP, 8 months agoFrom my article:
[D]epending on context, being hard to change can be a bad thing. For example, ‘tight coupling’ is a reason software can be hard to change, and it’s considered bad because it reduces maintainability.
@edwin-de-wit recently asked Deutsch about this:
… hard to vary can also be a property that you don’t want. Sometimes they say that complicated systems are just so entangled that they’re no longer changeable. You could call that hard to vary but it’s not a property you pursue.
Deutsch’s reply:
Quite so. So hard to vary is about explanations, not about end products. So the end product should be easy to vary, if you want to. But it should be hard to vary in the sense that you don’t want to.
#5181·Tyler MillsOP, 30 days agoBut this depends on what a "problem" is; any output will be the solution to some problem, somewhere, so all programs would have unlimited reach.
So reach should only ever be invoked with respect to existing knowledge? So a program's reach is the intersection of its codomain and the solutions to known problems.
#5180·Tyler MillsOP, 30 days agoMaybe this definition accommodates both the multiversal and atemporal aspects of reality: a program's reach is the set of its outputs that solve problems in any universe (past, present or adjacent).
But this depends on what a "problem" is; any output will be the solution to some problem, somewhere, so all programs would have unlimited reach.
#5179·Tyler MillsOP, 30 days agoFun question. Say the reach of a program is the set of all problems it can solve or help solve (whether anyone knows, or whether the problems exist yet). All of that program's possible outputs together comprise the implication space -- it sounds like "codomain" is actual term. The instantiation of each item in the codomain is an occurrence of my "inferential novelty". The codomain is implicit in a program when it is created, but not all of that output will help solve problems. The program's reach is the subset that does.
Maybe this definition accommodates both the multiversal and atemporal aspects of reality: a program's reach is the set of its outputs that solve problems in any universe (past, present or adjacent).
#5172·Dennis Hackethal, about 1 month agoHow much overlap is there between the concept of inferential novelty and reach, if any?
Fun question. Say the reach of a program is the set of all problems it can solve or help solve (whether anyone knows, or whether the problems exist yet). All of that program's possible outputs together comprise the implication space -- it sounds like "codomain" is actual term. The instantiation of each item in the codomain is an occurrence of my "inferential novelty". The codomain is implicit in a program when it is created, but not all of that output will help solve problems. The program's reach is the subset that does.
Taking Popper Too Far, Again: https://libertythroughreason.com/taking-popper-too-far-again/
Rationality as Computation: https://libertythroughreason.com/rationality-as-computation/
#5175·Liberty Fitz-Claridge, about 1 month agoI think we agree that the conjecturing and criticising of explanations is where the progress happens, and this choice you're saying people make at the end among conjectured theories is (relatively) mechanical. But I would also point out that trying to measure how HTV a theory is is as futile and scientistic as trying to measure moral worth. Yet it's still possible to have meaningful discussions about morality. I can't measure the moral value of murder but I can meaningfully argue it's worse than theft. So I think the claim that "if you can't program it you don't understand it" doesn't apply so universally as #3020 implies.
I think you may have misunderstood me. I asked how I can know that our discussion about HTV will be productive if we continue it now. (For context and for others: I’ve found that Liberty and I have roughly the same discussion in various venues every few months or so. I raised this issue in the linked X thread.)
I didn’t ask you to continue the object-level discussion itself.
Please address my concern before continuing the discussion.
#3924·Dennis HackethalOP, 8 months agoIt seems that you've taken the idea of hard to vary as saying that the process of choosing between competing theories is just about measuring how much of this trait they have. One clearly wouldn’t get better explanations from doing that, as it would just be a mechanical way of judging theories.
Yes, but as I understood Deutsch, this process of choosing happens after one has conjectured and criticized a bunch of explanations. I don’t think he suggests that the application of the HTV criterion makes theories better, only that we should use it to choose between explanations after they have been guessed and improved.
So the process of choosing between already existing explanations really is “just about measuring how much of this trait they have.”
I think we agree that the conjecturing and criticising of explanations is where the progress happens, and this choice you're saying people make at the end among conjectured theories is (relatively) mechanical. But I would also point out that trying to measure how HTV a theory is is as futile and scientistic as trying to measure moral worth. Yet it's still possible to have meaningful discussions about morality. I can't measure the moral value of murder but I can meaningfully argue it's worse than theft. So I think the claim that "if you can't program it you don't understand it" doesn't apply so universally as #3020 implies.
Would it help to distinguish between dogmatic vs. critical information processing?
That’s a distinction I’ve been using. All programs written to date are dogmatic. Whereas a genuine evolutionary algorithm would be critical, at least in part.
We don’t know how to write critical code. We only know how to write dogmatic code that looks critical.
#5106·Tyler MillsOP, about 1 month agoFor the changes made by a source of variation to be dependent on the content of any knowledge in the target, the source would have to contain knowledge itself. (The DNA mutation sources do not.) Blind changes are dependent on the medium in which information is contained, like an A versus a G in a strand of DNA (assuming these are information media). But the change made to the A or G by the cosmic ray is independent of the information they are hosting, if any. Any changes by the ray are dependent on the physical/chemical structure of the target, the substrate. Information is substrate independent. It is not the information stored in the A or G that is determining what changes are made to them.
Cosmic rays have been known to flip bits in computers, eg impacting election results: https://ui.adsabs.harvard.edu/abs/2021arXiv210505103N/abstract
However, due to computational universality, we should be able to simulate a knowledge-growing system plus cosmic rays impacting that system.
So then at that point the source of the mutation is part of the program again…