Search Ideas

I could get rid of the count everywhere, even on unfiltered views. That would have the added benefit that users wouldn’t prefer one problematic idea over another just because it has fewer pending criticisms.

I could get rid of the count everywhere, even on unfiltered views.

The displayed criticism count for a filtered parent can differ from the number of displayed criticisms.

But users are expecting a count.

For any filtered parent, the criticism badge could be shown without a count.

For any filtered parent, the criticism badge could be shown without any count.

I have this working to the point that it shows n / m, but getting the counter to update properly when new criticisms are posted on filtered parents is surprisingly difficult – so difficult the juice may not be worth the squeeze.

Fixed as of 27123bd.

Done as of 27123bd.

Bug: as you cycle through a parent’s versions on ideas#show, the children are suddenly not being filtered anymore, and the highlighted idea suddenly has siblings.

Bug when cycling through ‘filtered’ revisions: on page render, no matter how many children/criticisms a parent of the highlighted idea has, only the highlighted idea is shown – that’s fine so far – but the displayed criticism count may be higher if there are criticisms that are not being shown. So there’s a mismatch.

Shouldn’t have more than one criticism at a time.

That in and of itself isn’t a bug if the different revisions leading to the highlighted idea have different numbers of criticisms.

The issue also isn’t that there are other revisions that don’t lead to the highlighted idea.

The real issue is twofold:

1. On page render, no matter how many children/criticisms a parent of the highlighted idea has, only the highlighted idea is shown – that’s fine so far – but the displayed criticism count may be higher if there are criticisms that are not being shown. So there’s a mismatch.
2. As you cycle through the parent’s versions, the children are suddenly not being filtered anymore, and the highlighted idea suddenly has siblings. Now the criticism count on the parent does always match the number of shown criticisms, but it seems arbitrary to suddenly not filter the children anymore.

Bugs when cycling through ‘filtered’ revisions:

1. On page render, no matter how many children/criticisms a parent of the highlighted idea has, only the highlighted idea is shown – that’s fine so far – but the displayed criticism count may be higher if there are criticisms that are not being shown. So there’s a mismatch.
2. As you cycle through the parent’s versions, the children are suddenly not being filtered anymore, and the highlighted idea suddenly has siblings. Now the criticism count on the parent does always match the number of shown criticisms, but it seems arbitrary to suddenly not filter the children anymore.

That it and of itself isn’t a bug if the different revisions leading to the highlighted idea have different numbers of criticisms.

The issue also isn’t that there are other revisions that don’t lead to the highlighted idea.

The real issue is twofold:

1. On page render, no matter how many children/criticisms a parent of the highlighted idea has, only the highlighted idea shown – that’s fine so far – but the displayed criticism count may be higher if there are criticisms that are not being shown. So there’s a mismatch.
2. As you cycle through the parent’s versions, the children are suddenly not being filtered anymore, and the highlighted idea suddenly has siblings. Now the criticism count on the parent does always match the number of shown criticisms, but it seems arbitrary to suddenly not filter the children anymore.

The red ‘Criticized’ label shows how many pending criticisms an idea has. For example ‘Criticized (5)’ means the idea has five pending criticisms.

But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify pending criticisms.

There should be an easy way to filter comments of a given idea down to only pending criticisms.

The feature wasn’t quite polished. For example, arrow navigation through the dropdown menu was missing. And there were some bugs. But it’s polished now and the bugs should be fixed as of 4ced719.

Similarity is fine if it is less narrow, but ‘thread’ doesn’t seem any less narrow than ‘discussion’ to me. A ‘thread’ usually means a reply chain.

Why is similarity a bad thing in and of itself? It can be reminiscent of discussions as long as it’s less narrow.

I can’t decide if this communicates a grouping of ideas. Seems borderline.

“Go check out the Karl Popper context on Veritula” would only make sense if you are already a Veritula user who is accustomed to using this terminology.

Makes me think of “subject of discussion”.

I have an inexplicit criticism of this relating to “school subject”.

This actually seems anti-discussion. Sounds like a grouping of ideas that are only related by conceptual proximity, rather than building on each other.

This makes me think of “discussion topic”.