Veritula – Meta
Fixed as of 76299a2.
Fixed as of 76299a2, see eg https://veritula.com/ideas/3951-done-as-of-cc1ab95-ruby-example-ruby-def/revisions/2. (Click on “Expand unchanged parts”.)
#2712·Dennis HackethalOP, 12 months agoNow that diffs are formatted, they don’t omit unchanged lines anymore.
Fixed as of 76299a2.
Done as of cc1ab95.
Ruby example:
def criticized? ideapending_criticisms(idea).any?enddef pending_criticisms ideacriticisms(idea).filter { |c| pending_criticisms(c).none? }enddef criticisms ideachildren(idea).filter(&:criticism?)end
JS example (h/t ChatGPT):
function criticized(idea) {return pendingCriticisms(idea).length > 0;}function pendingCriticisms(idea) {return criticisms(idea).filter(c => pendingCriticisms(c).length === 0);}function criticisms(idea) {return children(idea).filter(c => c.isCriticism);}
Done as of 65dba4b.
Ruby example:
def criticized? ideapending_criticisms(idea).any?enddef pending_criticisms ideacriticisms(idea).filter { |c| pending_criticisms(c).none? }enddef criticisms ideachildren(idea).filter(&:criticism?)end
JS example (h/t ChatGPT):
function criticized(idea) {return pendingCriticisms(idea).length > 0;}function pendingCriticisms(idea) {return criticisms(idea).filter(c => pendingCriticisms(c).length === 0);}function criticisms(idea) {return children(idea).filter(c => c.isCriticism);}
#4013·Dennis HackethalOP, 9 months agoThere’s a small issue related to previewing changes in code blocks: even when there are no changes yet, if the code overflows horizontally, the scroll shadow is shown through DOM manipulation, which in turn triggers the diffing library into thinking the user made a change.
So then the same code block is shown without any changes, under the ‘Changes’ tab, which is confusing. It should still just say ‘No changes’.
Fixed as of 7134d27.
#4024·Dennis HackethalOP revised 9 months agoThe diff view can’t handle the removal/replacement of entire code blocks yet. The removed block looks broken, the new block doesn’t show at all. See activity 3207 in dev.
Fixed as of b2a2a32 at the latest.
#4023·Dennis HackethalOP, 9 months agoWould be nice if the copy button was sticky-top so that it scrolled with the user.
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.)
#3904·Dennis HackethalOP, 9 months ago@tyler-mills says:
I keep coming back to a graph-based presentation. Every comment a node, edges red if ending in criticisms. I crave a way to see structurally how many red criticism threads and grey comment threads are stemming from a given idea. The red ones could be bold and bright if they lead to an uncriticized idea, else dim and thin. Then we can see at a glance which ideas are sources of more criticisms, and/or hold greater opportunities for further criticism — can see which ideas are “deeper” niches, one might say (..!). Have greater evolvability…
Basically not doable for the user with the current bubble+hashtag method. But again it could just be an optional view. I think I mentioned I find that Kialo does a cool job with their sun dial diagrams (which are optional).
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.
#5164·Tyler Mills, 3 months agoI 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.)
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.
#5161·Dennis HackethalOP, 3 months agoDiscussions 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?
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.)
#5145·Tyler Mills, 3 months agoNo 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).
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?
#5148·Tyler Mills, 3 months agoI 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).
… 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.
#5145·Tyler Mills, 3 months agoNo 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).
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.
#5145·Tyler Mills, 3 months agoNo 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).
Another problem with letting people delete posts is that others may have written a comment in the meantime, which they then can’t submit.
#5147·Tyler Mills, 3 months agoOkay to allow for posts that have no comments or criticisms? Or only for posts on one's profile (perhaps also meeting that criterion)?
It can still mess up the continuity of discussions when the post to be deleted has parents.
#5145·Tyler Mills, 3 months agoNo 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).
Another choice: criticize one for being a duplicate. In the criticism, link to the original and instruct people to ignore the duplicate.
#5154·Dennis HackethalOP, 3 months agoBut the system does have a way to identify automatically generated criticisms.
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.
#5153·Dennis HackethalOP, 3 months agoYep. 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 the system does have a way to identify automatically generated criticisms.