Search Ideas

A sticky button can't work here: the main content area has to be a horizontal scroll container so deeply nested trees can grow sideways, and that stops position: sticky from sticking. The workarounds (reworking the global layout, or JavaScript positioning that jitters on mobile) are too risky for such a small benefit.

Tyler suggested (#3904) we use the chart type from Kialo:

Could be a useful visualization in addition to trees.

Each top-level idea would be the center node. Then red segments around it for pending criticisms. Gray for non-pending criticisms and neutral comments.

Unlike Kialo, though, each segment would have the same size as the other segments on its circle.

Offer easy way to link to latest version of an idea. The ability already exists – an idea link + /latest will always go to the latest version – but isn’t directly exposed in the form of a link or button yet.

Done as of c00ed18.

Reiterating/refining #3904: There should be a graphical indication for pending criticisms. The dropdown line should be red if the comment it leads to is a pending criticism. The yellow pills can be turned gray to be easier on the eyes.

This says nothing about the yellow color of the criticisms pills, which I think Tyler is saying are too harsh on the eyes.

That doesn’t mean the pill has to stay yellow. Too harsh.

That doesn’t mean the pill has to say yellow. Too harsh.

And dimmer red for refuted criticisms, brighter red for pending ones! Default gray for comments.

Would get alternating dim and bright depending on insertion order. Confusing!

Reiterating/refining #3904: There should be a graphical indication for pending criticisms. The dropdown line should be red if the comment it leads to is a pending criticism.

Reiterating/refining #3904: I think the yellow "Criticism of" bubbles can and should be replaced by a graphical indication that is much easier on the eyes. The dropdown line can be made red if the comment it leads to is a criticism, and the bubble on the criticism can be eliminated. Reading the yellow bubble to get the idea # it is referring to, then searching the ideas above for the matching # is inelegant (even if it is usually the one right above).

And dimmer red for refuted criticisms, brighter red for pending ones! Default gray for comments.

It’s more in line with refute.us if non-pending criticisms are neutralized, ie gray as well.

And dimmer red for refuted criticisms, brighter red for pending ones! Default gray for comments.

Tried it – unfortunately, there aren’t enough shades of red to easily tell the difference.

Not red anymore. Gray as of 5b3358f.

Reiterating/refining #3904: I think the yellow "Criticism of" bubbles can and should be replaced by a graphical indication that is much easier on the eyes. The dropdown line can be made red if the comment it leads to is a criticism, and the bubble on the criticism can be eliminated. Reading the yellow bubble to get the idea # it is referring to, then searching the ideas above for the matching # is inelegant (even if it is usually the one right above).

And dimmer red for refuted criticisms, brighter red for pending ones! Default gray for comments.

Best to put additional information in a revision of the target idea, not as a comment. Comments aren’t for chronological addition of information like on X or Reddit.

Would avoid putting it in a tooltip. Best to keep it for accessibility. Communicating only with lines and colors is too little information.

I have yet to want to open the criticized idea in a new tab

I do that on occasion and like being able to do it. Other users may, too.

Fixed as of d633dc3.

Fixed as of 76299a2, see eg https://veritula.com/ideas/3951-done-as-of-cc1ab95-ruby-example-ruby-def/revisions/2. (Click on “Expand unchanged parts”.)

Fixed as of 76299a2.

Done as of 65dba4b.

Ruby example:

1
2
3
4
5
6
7
8
9
10
11

def criticized? idea
  pending_criticisms(idea).any?
end

def pending_criticisms idea
  criticisms(idea).filter { |c| pending_criticisms(c).none? }
end

def criticisms idea
  children(idea).filter(&:criticism?)
end

JS example (h/t ChatGPT):

1
2
3
4
5
6
7
8
9
10
11

function criticized(idea) {
  return pendingCriticisms(idea).length > 0;
}

function pendingCriticisms(idea) {
  return criticisms(idea).filter(c => pendingCriticisms(c).length === 0);
}

function criticisms(idea) {
  return children(idea).filter(c => c.isCriticism);
}

Fixed as of 7134d27.

Fixed as of b2a2a32 at the latest.

A sticky button can't work here: the main content area has to be a horizontal scroll container so deeply nested trees can grow sideways, and that stops position: sticky from sticking. The workarounds (reworking the global layout, or JavaScript positioning that jitters on mobile) are too risky for such a small benefit.

(Generated with Claude.)