Dennis Hackethal’s avatar

Dennis Hackethal

@dennis.hackethal​·​Joined Jun 2024​·​Ideas
Log in or sign up to follow Dennis or post on their wall.

Founder Veritula.
Author. Software engineer. Ex Apple. Translator of The Beginning of Infinity.
dennishackethal.com

New Check out Dennis Hackethal’s adoptable and rejectable ideas.
  Dennis Hackethal posted idea #5223.

Just stumbled upon this tip in my Insta feed to deal with noisy neighbors: https://www.instagram.com/reel/Db4gheyx9WP/?igsh=NTc4MTIwNjQ2YQ==

Apparently you can buy a device that cancels out vibrations in your walls. Not sure I’m understanding exactly how it works.

  Dennis Hackethal reposted idea #5084.

Now also available on PhilPapers: https://philpapers.org/archive/HACTSO-6.pdf

#5084​·​Dennis HackethalOP, about 2 months ago
  Dennis Hackethal posted idea #5185.

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.

  Dennis Hackethal addressed criticism #5183.

@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.

#5183​·​Dennis HackethalOP, about 1 month ago

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.

  Dennis Hackethal addressed criticism #3718.

From 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.

#3718​·​Dennis HackethalOP, 8 months 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.

  Dennis Hackethal addressed criticism #5175.

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.

#5175​·​Liberty Fitz-Claridge, about 1 month ago

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.

  Dennis Hackethal posted idea #5174.

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.

  Dennis Hackethal commented on idea #5106.

For 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.

#5106​·​Tyler MillsOP, about 2 months ago

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…

  Dennis Hackethal commented on idea #5101.

Claim: It is useful (if not crucial) to distinguish between two notions of novelty: inferential and non-inferential.

Knowledge that is inferentially novel may never have been seen before, but was already implicit in existing knowledge; it results from application and composition of existing knowledge (e.g. the running of programs). What is novel in this way can be instantiated without any external epistemic (knowledge-related) influence. A program needs infrastructure to allow its computation to occur; it does not need another program, in an epistemic sense: If there's a dependency, we should consider the two to be part of the same "epistemic system." Let's say the dependent target has no "implication space" until its needed source is causally linked to it. The source may have its own implication space. Once "joined," a new implication space is defined.

Inferentially novel output (the instantiation of knowledge in an implication space) is all that current computer software (and all AI) is capable of. These systems "create" knowledge only in this sense.

#5101​·​Tyler MillsOP, about 2 months ago

How much overlap is there between the concept of inferential novelty and reach, if any?

  Dennis Hackethal posted idea #5171.

Paul Raymond-Robichaud tells me (I think in this space) that in math, you can have a formalized notion of HTV. From what I recall he said, it sounded like that would be trivial to develop (for a mathematician like Paul – not for me).

Anyone who’s both mathematically and epistemologically inclined could give this a shot at generalization.

  Dennis Hackethal criticized idea #5164.

I don't think so; just having a Wall of posts on my profile is fine, no funny business. Here I was only hoping to delete an accidental mis-post. Maybe allowing deletion of exact duplicates with no parents is reasonable? But this is just a cleanliness/organizational thing, and kind of a fluke, probably not an issue worth spending much time on. (But I stand by #5143, and regardless of the size of the revision. Seems cleaner to me to only show the latest version, no diff.)

#5164​·​Tyler Mills, about 1 month ago

Maybe allowing deletion of exact duplicates with no parents is reasonable?

Too niche/specific for an extra feature tbh. If accidental duplicates happened often, then maybe.

  Dennis Hackethal commented on idea #4977.

Are pacifism, socialism and compromise all short-termist?

Pacifism reduces casualties --- in the short term.

Socialism reduces poverty --- in the short term.

Compromise reduces disappointment --- in the short term.

#4977​·​Tyler Mills, 4 months ago

Did you know you can type em dashes (on Mac) by hitting alt + shift + hyphen?

  Dennis Hackethal commented on idea #5145.

No way to delete posts. Posted same thing twice by mistake (unexpected Chrome behavior). Choices are to leave the duplicate, which seems inelegant, or to revise it into another whole post, which I did, but that contributed to the issue in #5143 (creates an unclear green and red update post).

#5145​·​Tyler Mills, about 1 month ago

Discussions have an ‘Archive’ button for top-level posts. It looks like a box you’d put on a shelf in an archive.

Top-level profile posts could have such a button, too. And I could add an ‘Archived’ tab.

Would that help you achieve what you’re looking for?

  Dennis Hackethal reposted idea #5083.

I’ve formalized some of these ideas in my first paper, ‘The Structure of Rational Thought’.

https://www.academia.edu/170297518/The_Structure_of_Rational_Thought

#5083​·​Dennis HackethalOP, about 2 months ago
  Dennis Hackethal criticized idea #5148.

I question whether previous versions of a criticism should contribute to the battle-tested count, as they do currently. Someone can make a spelling correction to the criticism, which creates the "supersedes" criticism of that previous version of the criticism, and that then contributes to the battle-tested count. This seems wrong, since that counter-criticism is not substantive, and even if it were, OP only generally responds to the latest version of a criticism (may not even have known about previous versions; all of this happened in: https://veritula.com/ideas/5089-knowledge-growth-such-as-in-genes-in-the-biospher).

#5148​·​Tyler Mills, about 1 month ago

… OP only generally responds to the latest version of a criticism …

I’m not sure that’s generally true. But regardless, OP should address all pending versions of a criticism.

  Dennis Hackethal commented on idea #5145.

No way to delete posts. Posted same thing twice by mistake (unexpected Chrome behavior). Choices are to leave the duplicate, which seems inelegant, or to revise it into another whole post, which I did, but that contributed to the issue in #5143 (creates an unclear green and red update post).

#5145​·​Tyler Mills, about 1 month ago

I’m open to letting people contact me for serious cases (like accidentally posting their password or credit-card details). And then I can delete that content manually in the database.

Aside from that, we’d need to identify a case where simply criticizing a post isn’t enough. The criticism can state the reasons one would otherwise have for deleting a post.

  Dennis Hackethal criticized idea #5145.

No way to delete posts. Posted same thing twice by mistake (unexpected Chrome behavior). Choices are to leave the duplicate, which seems inelegant, or to revise it into another whole post, which I did, but that contributed to the issue in #5143 (creates an unclear green and red update post).

#5145​·​Tyler Mills, about 1 month ago

Another problem with letting people delete posts is that others may have written a comment in the meantime, which they then can’t submit.

  Dennis Hackethal addressed criticism #5147.

Okay to allow for posts that have no comments or criticisms? Or only for posts on one's profile (perhaps also meeting that criterion)?

#5147​·​Tyler Mills, about 1 month ago

It can still mess up the continuity of discussions when the post to be deleted has parents.

  Dennis Hackethal criticized idea #5145.

No way to delete posts. Posted same thing twice by mistake (unexpected Chrome behavior). Choices are to leave the duplicate, which seems inelegant, or to revise it into another whole post, which I did, but that contributed to the issue in #5143 (creates an unclear green and red update post).

#5145​·​Tyler Mills, about 1 month ago

Another choice: criticize one for being a duplicate. In the criticism, link to the original and instruct people to ignore the duplicate.

  Dennis Hackethal addressed criticism #5154.

But the system does have a way to identify automatically generated criticisms.

#5154​·​Dennis HackethalOP, about 1 month ago

It does, but it has no universal way to semantically check why a criticism was generated this way. All it knows is that the criticism was generated as part of a superseding revision, but it doesn’t know the meaning of the contents of that revision.

  Dennis Hackethal criticized idea #5153.

Yep. Was going to say this, too. The system has no semantic way to check the content of a criticism. So it has to assume that every unaddressed criticism is substantive.

#5153​·​Dennis HackethalOP, about 1 month ago

But the system does have a way to identify automatically generated criticisms.

  Dennis Hackethal commented on criticism #5150.

But sometimes revisions can be substantive, and OP could defend against one version, and in that case it should count toward the battle-tested badge!

#5150​·​Tyler Mills revised about 1 month ago

Yep. Was going to say this, too. The system has no semantic way to check the content of a criticism. So it has to assume that every unaddressed criticism is substantive.