Search Ideas

Having implemented this, a problem has surfaced: when linking to an old version of an idea, the alert “You’re about to comment on an old version of this idea. Are you sure …” shows. That’s jarring if you didn’t want to comment but merely look at the idea.

Great, looks like you learned something new. You’ve found a bit of truth :)

Done as of b423e18.

As of acb14e3, the revision button is an icon button that lives next to the collapse icon button.

Therefore, the button doesn’t need to be hidden anymore.

Done as of acb14e3.

The idea is not good if it has outstanding criticisms.

Don’t worry about which ideas are better than others. That’s a remnant of justificationism. Only go by whether an idea has outstanding criticisms.

You’ve since made the change to “a few changes” (as of #1894) but I think that change was premature.

Don’t make changes you don’t understand. Take questions literally and answer them.

https://www.britannica.com/dictionary/eb/qa/The-Difference-Between-Few-and-A-Few-

No.

I went over it first and made a few changes. After that, Grammarly recommended that I remove the 'a' before 'criticism' and to remove the 'they are'.

This comment doesn’t belong here. It should have been a comment on #1885. And you shouldn’t have removed #1885. I’ll recover it.

It could go both ways. Someone may have already read an idea and just wants to revise it, in which case having to scroll to the bottom is cumbersome.

That would mean the revise button would be at the top of the idea. But presumably, people would typically want to revise an idea after they finish reading it. Meaning after they reach the bottom.

I could turn the ‘Revise…’ button into an icon button that lives next to the collapse icon button. It could just have a pencil for an icon.

That way, the button wouldn’t need to be hidden anymore.

Should I be showing the comment form by default on ideas#show?

To avoid scrolling past content, I could remove the autofocus on the textarea unless a certain query parameter is given.

The ‘Revise…’ button is hidden when the comment form is open. It makes sense to hide it because it doesn’t belong in that context. But once hidden, the user has no quick way to revise an idea. Maybe the first thing they want to do after opening ideas#show is not comment but revise.

Then the autofocus on the textarea would force a scroll basically to the bottom of the page. For sufficiently long ideas, that means scrolling past content the user wants to see.

Should I be showing the comment form by default on ideas#show?

… made few changes.

Did you mean to say ‘a few changes’?
Do you know what the difference is?

When it has received criticism and until the current criticism is resolved, that idea is seen as false.

‘The idea is considered false until all criticism is resolved.’

We accept that idea as true until it has received criticism.

‘until it receives criticism’

Cool. As discussed privately, I think you’d benefit from working on spelling and grammar.

Try pasting #1874 into Grammarly and revising the idea based on the improvements Grammarly suggests. (Don’t blindly accept word substitutions! Make sure any edits still make sense in the context of how Veritula works.)

Pasting anything you write into Grammarly before you submit it is probably a good policy to adopt in general.

Could probably use Turbo frames instead.

That would probably be stretching the capabilities of Stimulus…

There could be a separate button to filter comments down.

Now I’m submitting a criticism that contains a flaw. It has a tpyo.

Try counter-critizing my criticism by pointing out the typo. Observe that the red label saying ‘Criticized’ on #1874 disappears once you submit your criticism.

In other words, your counter-criticism ‘neutralizes’ my criticism.

Revising ideas and submitting counter-criticisms are the two ways to address criticisms.