Veritula – Meta
#2999·Dennis HackethalOP revised about 13 hours agoFor any filtered parent, the criticism badge could be shown without a count.
But users are expecting a count.
For any filtered parent, the criticism badge could be shown without any count.
For any filtered parent, the criticism badge could be shown without a count.
#2970·Dennis HackethalOP revised 2 days agoBug 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.
For any filtered parent, the criticism badge could be shown without any count.
#2098·Dennis HackethalOP revised about 1 month agoAny filtered ideas should show a criticism label displaying
n / mfor the count, wherenis the number of rendered criticisms andmis the number of total criticisms.An explanation could accompany the
n / mdisplay, like a title on hover.That way, there should never be any confusion as to a mismatch between the total vs rendered number of pending criticisms.
In addition, when looking at a deeply nested idea on ideas#show and submitting a criticism on a parent, I need to make sure the updated badges take into account that newly submitted criticism, even though the new criticism would not show after refreshing the page.
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.
#2972·Dennis HackethalOP, 2 days agoBug: 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.
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.
Bugs 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.
- 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.
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.
#2965·Dennis HackethalOP revised 2 days agoBugs 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.
- 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.
Shouldn’t have more than one criticism at a time.
Fix typos
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:
- 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.
- 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 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:
- 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.
- 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.
Bug: when cycling through ‘filtered’ revisions (meaning there are more revisions that don’t lead to the highlighted idea), the criticism badge can change count for the same revision.
Bugs 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.
- 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.
#1986·Dennis HackethalOP revised about 1 month agoBug: when cycling through ‘filtered’ revisions (meaning there are more revisions that don’t lead to the highlighted idea), the criticism badge can change count for the same revision.
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:
- 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.
- 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.
Simplify language
The red ‘Criticized’ label shows how many outstanding criticisms an idea has. For example ‘Criticized (5)’ means the idea has five outstanding criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify outstanding criticisms.
There should be an easy way to filter comments of a given idea down to only outstanding criticisms.
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.
#2940·Dennis HackethalOP, 4 days agoWhy is similarity a bad thing in and of itself? It can be reminiscent of discussions as long as it’s less narrow.
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.
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.