Search Ideas
780 ideas match your query.:
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.
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.
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.
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.
On mobile, there needs to be more of a padding on the right, inside the code block.
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. See activity 3207 in dev.
Would be nice if the copy button was sticky-top so that it scrolled with the user.
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.
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.
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’.
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.
Valid. As of 7af3c7b, the site uses ‘USD’ throughout.
I implemented this a while back.
X caches link previews, so old previews remain the same. But new previews feature the discussion title, see eg https://www.opengraph.xyz/url/https%3A%2F%2Fveritula.com%2Fdiscussions%2Fcriticisms-of-zcash.
Feature idea: pay people to criticize an idea.
You start a ‘criticism bounty’ of 100 bucks, say, which is prorated among eligible critics after some deadline.
The amount should be arbitrarily customizable (while covering transaction costs). Minimum of $5.
There could then be a page for bounties at /bounties. And a page listing a user’s bounties at /:username/bounties.
When starting a bounty, the user indicates terms such as what kinds of criticism they want. This way, they avoid having to pay people pointing out typos, say.
Anyone can start a bounty on any idea. There can only be one bounty per idea at a time.
To ensure a criticism is worthy of the bounty, the initiator gets a grace period of 24 hours at the end to review pending criticisms. Inaction automatically awards the bounty to all pending criticisms at the end of the grace period.
Feature idea: pay people to criticize your idea.
You start a ‘criticism bounty’ of 100 bucks, say, which is prorated among eligible critics after some deadline.
The amount should be arbitrarily customizable (while covering transaction costs). Minimum of $5.
There could then be a page for bounties at /bounties. And a page listing a user’s bounties at /:username/bounties.
When starting a bounty, the user indicates terms such as what kinds of criticism they want. This way, they avoid having to pay people pointing out typos, say.
Anyone can start a bounty on any idea. There can only be one bounty per idea at a time.
To ensure a criticism is worthy of the bounty, the initiator gets a grace period of 24 hours at the end to review pending criticisms. Inaction automatically awards the bounty to all pending criticisms at the end of the grace period.
This is now a feature, see the ‘Funding’ section of a bounty.