Veritula – Meta

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.

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

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

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

Deleting posts can really mess up the continuity of discussions, and allow for dishonesty.

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

My profile shows my revision to #5126 under Wall and under Activity, but not the post itself under the Wall. The revision is a jumble of red and green highlighted text (in this case, because the revision was significant), hard to read. Wall should only show latest versions of posts, not edits to them. Edits should go under Activity. And/or have the previous post versions viewable with the little arrows, as usual (and as done in the idea-focused view, after you click on the idea itself). Always show latest versions of ideas on the Wall so it's clear and easy to read.

I agree this feature should be optional and toggleable but that doesn’t address its (potential) shortcomings. It just kinda hides them.

I’m saying it’s not clear to be how deeply nested comments would be shown.

If I’m understanding you correctly, you dislike having to scroll up and down in a discussion. You see empty space on the right and you think it should be filled. Hence your suggestion to put top-level ideas next to each other rather than on top of each other.

But then where do comments on each top-level idea go? Do they still go underneath? Nesting needs indentation. So that means deep nesting gets lots of indentation. So there’ll still be plenty of empty space.

Those are the kinds of things we’d need to figure out to have a mature design proposal ready for implementation.

Removed hyphenation

This may be too subjective, but I've always really disliked end-of-line hyphenation, of the kind currently used here. I find it pretty disruptive to the flow of reading, AND a source of visual clutter. That's a heavy cost for the supposed benefit of a justified margin, but we don't seem to be getting that benefit here either; the margin still appears jagged. A justified margin itself is unnecessary, if you ask me, but it can in any case be accomplished the other way, where small spaces are distributed between words in each line as needed. To me the latter method of the two is better for readability, no contest. I would advocate for the third/default method, here (jagged margin, no funny business), since justified margins seems needlessly formal.

Yeah, I'm not sure why I wrote this... I remember the option for number of criticisms now. I guess it slipped my mind.

Thanks, fixed.

Maybe I’m misunderstanding you, but that’s how standing bounties work already.

When you fund a standing bounty, you set the number of criticisms you’re willing to pay for, and the amount for each.

If that’s something you want to do for your current bounty, you still can, before current funding runs out.

See also “How Do Bounties Work?”

The "Battle tested" badge should have a hyphen!
https://www.merriam-webster.com/dictionary/battle-tested

Bounties could pay out multiplicatively, up to a limit (e.g. 10$ per criticism, up to 3). This would preserve the incentive for bounty hunting after one criticism has already been posted.

Related to this or not, it could be useful to be able to set a bounty on a set of ideas, rather than just one. "Criticize any of these ideas for n$".

The main thread is ambiguous currently, by that reasoning: it's always gray. Having the whole thing red to indicate one or more pending criticisms below seems useful, and cool. And the offshoots from the main thread (the little curly part leading to each sub-idea) can have the new colors.

E.g.: User scrolls down the main bright red thread, past gray comment offshoots and dim red refuted criticism offshoots, until reaching the bright red pending criticisms offshoot that is the cause of the main thread being bright red. (!)

Currently, a single gray "thread" comes off an idea, and splits off into sub-ideas. A single criticism in the above scheme would turn the whole thread red, which is ambiguous.

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

The link could be put in a new tooltip, or something. Or kept as is, just without the yellow bubble, frankly.

It should be made not red. Gray. Arguable even without the red criticism line idea above, since it already conflicts with the "red = criticism" motif.