Search Ideas

But this thread, about my English possibly being a problem, doesn’t seem like a relevant or substantive criticism.

As I’ve pointed out previously, I wouldn’t try to assign strengths (or ‘substantiveness’) to arguments.

Any criticism no matter how small destroys its target decisively if unaddressed. Whether or not its decisive is determined by whether or not there are any counter-criticisms, not by assigning some strength score (a remnant of justificationism). A criticism is decisive as long as there are no counter-criticisms. In the absence of counter-criticisms, how could it not be decisive?

In the current situation, this epistemology is actually to your benefit because, if some idea (such as #1731) is off topic, simply pointing this out in a criticism completely neutralizes the idea you deem off topic.

If a criticism really is tiny (or ‘weak’), it’s easier to just correct the error it points to than to counter-criticize. (For example, it’s usually quicker to fix a typo than to argue about the merits of pointing out typos.)

This is how Veritula is built. If you have an epistemological disagreement about its functionality or want to continue this broader epistemological discussion, submit an idea or criticism in ‘How Does Veritula Work?’.

Since you asked, I suggest you do both of the following:

1. Submit a criticism of #1731, suggesting that your English is off topic because the carelessness you suggest caused your typos had no effect on your choice of new terminology (‘Statements’ etc).
2. Since you agree that #1738 is not a criticism, revise it to unmark it as a criticism. At the bottom of the revision form, uncheck #1799 to indicate that it does not apply anymore.

You make a good point. Maybe the definition ‘information with causal power’ on its own isn’t very good since virtually any statement can have causal power yet presumably even Deutsch would agree that merely saying ‘hi’ isn’t knowledge even though it can have causal power (eg prompting someone to say ‘hi’ back).

Cool, appreciate it. Since you agree and plan to be more precise, should this really be marked as a criticism?

By the way, you don’t need to put disclaimers like “Addition 01-09-2025”. The versioning system records and displays all that information automatically :)

[J]oy may signal a resolved problem […]

But then the conflict is gone. So I don’t think revision #1741 addresses #1730.

To be clear, when I asked about the conflict behind joy, I meant ongoing conflict.

Your addition seems to agree with my criticism, not address it.

Or the existing search page could be filtered by discussion. For example, I could link to that page with an additional query param discussion_id=1 or something like that.

Or each discussion could have a search/filter form to filter ideas not just by criticized or not but also content and potentially other attributes.

Fixed as of 76b7ab4.

Make sure cycling between a leaf revision with children and a leaf revision without children properly toggles the gutter.

Sometimes you just want to hide the comments without collapsing the parent idea.

Because that would mean hiding each comment individually if you ever do want to hide all comments of an idea.

Bulk

Done as of fcf578c.

As noted in #1777, fetching the idea actually helps. Well worth the overhead.

This actually helps to prevent rendering links with IDs that don’t point to any existing idea.

Wouldn’t even need friendly ID for that since the URL would contain the ID. Would only need to override to_param to concatenate the idea’s ID and content.

Seems like minor overhead. It’s not like there are tons of user-generated hashtags everywhere.

Facebook does it this way, too.

Reddit is a bit different because they have multiple subreddits/communities, but each community has top-level posts which people can then comment on. They have a completely separate page/UI for top-level posts. And then directly underneath a top-level post, there’s a textarea saying “Join the conversation”.

Could have backwards compatibility for the short version and continue using the hashtag in the UI. Best of both worlds?

The way IG solves this is by rendering the form in a fixed position. It’s still on the bottom but always remains visible.

Done as of e6a90e5.

Done as of 9c14b22.

Fixed as of 985430e.