Search Ideas
914 ideas match your query.:
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.)
Idea: showing the quickest way to rehabilitate an idea.
Could be a visual feature showing something like the shortest path down a discussion tree where a criticism needs to be addressed.
Or all such branches.
Such a thing has probably been done in graph theory before, could look for existing algorithms.
I’ve experimentally turned off pretty text wrapping in paragraphs. I’ll give it some time to see how ideas look around the site now. If they look worse on the whole (orphans etc), I can always undo fd699cd.
It’s because of text-wrap: pretty;
Chromium renders it properly. Desktop and mobile Safari doesn’t.
Ben found a UI bug:

The text shouldn’t wrap after “trust”.
Maybe allowing deletion of exact duplicates with no parents is reasonable?
Too niche/specific for an extra feature tbh. If accidental duplicates happened often, then maybe.
I don't think so; just having a Wall of posts on my profile is fine, no funny business. Here I was only hoping to delete an accidental mis-post. Maybe allowing deletion of exact duplicates with no parents is reasonable? But this is just a cleanliness/organizational thing, and kind of a fluke, probably not an issue worth spending much time on. (But I stand by #5143, and regardless of the size of the revision. Seems cleaner to me to only show the latest version, no diff.)
Discussions have an ‘Archive’ button for top-level posts. It looks like a box you’d put on a shelf in an archive.
Top-level profile posts could have such a button, too. And I could add an ‘Archived’ tab.
Would that help you achieve what you’re looking for?
… OP only generally responds to the latest version of a criticism …
I’m not sure that’s generally true. But regardless, OP should address all pending versions of a criticism.
I’m open to letting people contact me for serious cases (like accidentally posting their password or credit-card details). And then I can delete that content manually in the database.
Aside from that, we’d need to identify a case where simply criticizing a post isn’t enough. The criticism can state the reasons one would otherwise have for deleting a post.
Another problem with letting people delete posts is that others may have written a comment in the meantime, which they then can’t submit.
It can still mess up the continuity of discussions when the post to be deleted has parents.
Another choice: criticize one for being a duplicate. In the criticism, link to the original and instruct people to ignore the duplicate.
It does, but it has no universal way to semantically check why a criticism was generated this way. All it knows is that the criticism was generated as part of a superseding revision, but it doesn’t know the meaning of the contents of that revision.
But the system does have a way to identify automatically generated criticisms.
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 toward the battle-tested badge!
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).