Veritula – Meta
#420·Dennis HackethalOP revised over 1 year agoNow that there are user profiles (#408), each profile can have a tab for unproblematic ideas. Among all the ideas a user has submitted, those are the ones he can rationally hold. And another tab for problematic ideas, ie ideas he has submitted that he cannot rationally hold.
No need for new tabs. This feature could be integrated with the search page by filtering ideas by user. That page already has filters for problematic vs unproblematic ideas.
Ah, but I can reproduce when I manually make the selection by clicking and dragging to cover the entire quote.
Ah, but I can reproduce when I manually make the selection by clicking and dragging to cover the entire quote (and only the quote, nothing above or below).
#2637·Benjamin Davies, 6 months agoWhen copying a box quote from Veritula, the box quote formatting (>) is lost.
There’s a way to get what you want: if you select some text in an idea before hitting its criticize or comment button, the selected text should always be inserted as a box quote.
Archiving this criticism for now, but if you’re still seeing any issues, let me know and I’ll take another look.
#2637·Benjamin Davies, 6 months agoWhen copying a box quote from Veritula, the box quote formatting (>) is lost.
When you copy text for an inline quote, you wouldn’t want the box-quote formatting.
Done as of 19009b2. Discussions now have a link to search ideas, which points to the search page with that discussion already preselected in a new discussion dropdown.
#2912·Dennis HackethalOP, 6 months ago‘Discussions’ are too narrow a term for a collection of ideas. See #2878.
While ideas should always be ‘discussable’, that doesn’t mean everyone who wants to share an idea always wants to start a discussion. Maybe they just want to put some information out there.
Tyler recently wrote to me, in the context of a question he wanted to figure out, “would be good to Veritula this.” Cool seeing ‘Veritula’ used as a verb.
I have found myself using this term naturally, as in ‘starting a thread on Veritula’. I believe I’ve heard others say this, too.
#3997·Dennis HackethalOP revised 3 months agoWhen I revise a criticism, I can’t see what it criticises. The edit screen should show the parent idea, similar to when I write a new criticism.
Valid. As of c310cbb, the most recent parent is shown above the idea you’re editing.
I spoke to soon. Rolling this back for now. Too jittery when scrolling on mobile. Non-trivial to implement. Need to see how other sites do it.
#4023·Dennis HackethalOP, 3 months agoWould be nice if the copy button was sticky-top so that it scrolled with the user.
Done as of 43c4ecc.
#4027·Dennis HackethalOP revised 3 months agoOn mobile, there needs to be more of a padding on the right, inside the code block.
Done as of 609b5c3.
There needs to be more of a padding on the right, inside the code block.
On mobile, there needs to be more of a padding on the right, inside the code block.
#3951·Dennis HackethalOP, 3 months agoDone as of
cc1ab95.Ruby example:
rubydef criticized? ideapending_criticisms(idea).any?enddef pending_criticisms ideacriticisms(idea).filter { |c| pending_criticisms(c).none? }enddef criticisms ideachildren(idea).filter(&:criticism?)endJS example (h/t ChatGPT):
javascriptfunction 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);}
There needs to be more of a padding on the right, inside the code block.
The 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.
The 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.
#3951·Dennis HackethalOP, 3 months agoDone as of
cc1ab95.Ruby example:
rubydef criticized? ideapending_criticisms(idea).any?enddef pending_criticisms ideacriticisms(idea).filter { |c| pending_criticisms(c).none? }enddef criticisms ideachildren(idea).filter(&:criticism?)endJS example (h/t ChatGPT):
javascriptfunction 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);}
Would be nice if the copy button was sticky-top so that it scrolled with the user.
#4016·Dennis HackethalOP, 3 months agoThere’s an issue with horizontal scroll for overflowing code blocks in the activity feed on mobile. Can’t scroll all the way to the right.
Fixed as of e49cd8d.
#3951·Dennis HackethalOP, 3 months agoDone as of
cc1ab95.Ruby example:
rubydef criticized? ideapending_criticisms(idea).any?enddef pending_criticisms ideacriticisms(idea).filter { |c| pending_criticisms(c).none? }enddef criticisms ideachildren(idea).filter(&:criticism?)endJS example (h/t ChatGPT):
javascriptfunction 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);}
There’s an issue with horizontal scroll for overflowing code blocks in the activity feed on mobile. Can’t scroll all the way to the right.
#1867·Dennis HackethalOP revised 7 months agoThe red ‘Criticized’ label could be a link leading to a filtered version of
ideas#show.
Yeah or see #2628.
#2886·Benjamin Davies, 6 months agoI am currently unable to zoom out to the full width when accessing Veritula on mobile.
Give this another shot. Should be fixed as of 6c7e74b.
For very deeply nested discussions, you may still need to scroll sideways to see some ideas. But you should now be able to zoom out far enough to always fit any idea into the viewport.
#3951·Dennis HackethalOP, 3 months agoDone as of
cc1ab95.Ruby example:
rubydef criticized? ideapending_criticisms(idea).any?enddef pending_criticisms ideacriticisms(idea).filter { |c| pending_criticisms(c).none? }enddef criticisms ideachildren(idea).filter(&:criticism?)endJS example (h/t ChatGPT):
javascriptfunction 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);}
There’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’.