Veritula – Meta

  Dennis Hackethal addressed criticism #3951.

Done as of cc1ab95.

Ruby example:

ruby
def criticized? idea

  pending_criticisms(idea).any?

end



def pending_criticisms idea

  criticisms(idea).filter { |c| pending_criticisms(c).none? }

end



def criticisms idea

  children(idea).filter(&:criticism?)

end

JS example (h/t ChatGPT):

javascript
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);

}
#3951​·​Dennis HackethalOP, 3 months ago

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.

  Dennis Hackethal archived idea #3986 along with any revisions.
  Dennis Hackethal addressed criticism #3986.

Bounties should be clear about what currency they are being paid out in.

#3986​·​Benjamin Davies, 3 months ago

Valid. As of 7af3c7b, the site uses ‘USD’ throughout.

  Dennis Hackethal archived idea #3107 along with any revisions.
  Dennis Hackethal addressed criticism #3107.

Preview links of discussions should show the name of the discussion being linked.

See eg https://x.com/agentofapollo/status/1991252721618547023

h/t @benjamin-davies*

#3107​·​Dennis HackethalOP, 5 months ago

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.

  Dennis Hackethal revised criticism #4001.

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.

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.

  Dennis Hackethal revised criticism #3481.

Feature idea: pay people to criticize your idea.

You start a ‘criticism bounty’ of ten bucks, say, per pending criticism received by some deadline.

The amount should be arbitrarily customizable (while covering transaction costs). The user also indicates a ceiling for the maximum amount they are willing to spend.

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. They may even award a bounty to problematic criticisms, at their discretion. Inaction automatically awards the bounty to all pending criticisms at the end of the grace period. If doing so would exceed the ceiling, more recent criticisms do not get the bounty.

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.

  Dennis Hackethal criticized idea #3061.

Could this feature be unified with #2669 somehow?

#3061​·​Dennis HackethalOP, 5 months ago

No need, see #3420.

  Dennis Hackethal addressed criticism #3912.

Been trying a slight modification of bounties in prod for a couple of weeks or so. Working well so far.

@dirk-meulenbelt recently offered to chip in for a bounty I want to run. That got me thinking: multiple people should be able to fund bounties.

#3912​·​Dennis HackethalOP, 3 months ago

This is now a feature, see the ‘Funding’ section of a bounty.

  Dennis Hackethal revised criticism #2430.

I notice that when I amend a criticism I have made, I’m not able to see what I am criticising. It would be good if the edit screen showed the comment I am disagreeing with similar to how it does when I first go to write a criticism.

When 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.

  Dennis Hackethal archived idea #1789 along with any revisions.
  Dennis Hackethal addressed criticism #2717.

Feature to collapse all criticized ideas of a discussion? Useful for todo lists.

#2717​·​Dennis HackethalOP revised 6 months ago

Archiving covers this.

  Dennis Hackethal archived idea #2669 along with any revisions.
  Dennis Hackethal revised idea #3062 and marked it as a criticism.

Could this feature be unified with #2811 somehow?

Could this feature be unified with #2811 somehow?

  Benjamin Davies posted criticism #3986.

Bounties should be clear about what currency they are being paid out in.

  Dennis Hackethal revised criticism #3953. The revision addresses idea #3955.

There’s still an issue on ideas#show. When an idea has nothing but a code block, there’s too much of a margin at the bottom, between the block and the border of the highlight.

When an idea has nothing but a code block, there’s too much of a margin at the bottom, between the block and the border of the highlight.

  Dennis Hackethal addressed criticism #3953.

There’s still an issue on ideas#show. When an idea has nothing but a code block, there’s too much of a margin at the bottom, between the block and the border of the highlight.

#3953​·​Dennis HackethalOP, 3 months ago

This issue didn’t only occur on ideas#show.

  Dennis Hackethal archived idea #3950 along with any revisions.
  Dennis Hackethal addressed criticism #3953.

There’s still an issue on ideas#show. When an idea has nothing but a code block, there’s too much of a margin at the bottom, between the block and the border of the highlight.

#3953​·​Dennis HackethalOP, 3 months ago

Fixed as of a44c6c0.

  Dennis Hackethal addressed criticism #3951.

Done as of cc1ab95.

Ruby example:

ruby
def criticized? idea

  pending_criticisms(idea).any?

end



def pending_criticisms idea

  criticisms(idea).filter { |c| pending_criticisms(c).none? }

end



def criticisms idea

  children(idea).filter(&:criticism?)

end

JS example (h/t ChatGPT):

javascript
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);

}
#3951​·​Dennis HackethalOP, 3 months ago

There’s still an issue on ideas#show. When an idea has nothing but a code block, there’s too much of a margin at the bottom, between the block and the border of the highlight.

  Dennis Hackethal commented on criticism #3950.

Code blocks need syntax highlighting.

Veritula used to have this feature but I removed it when diffing changed.

#3950​·​Dennis HackethalOP, 3 months ago

When the code overflows horizontally, a subtle inset shadow on the side shows that you can scroll:

javascript
const posts = [

  {id: 1, title: "Understanding JavaScript Closures in Depth", url: "https://example.com/articles/javascript-closures-deep-dive"},

  {id: 2, title: "A Complete Guide to Modern Web Development Practices", url: "https://example.com/articles/modern-web-dev-guide"},

  {id: 3, title: "Exploring the Node.js Event Loop and Async Patterns", url: "https://example.com/articles/nodejs-event-loop"}

];



function formatPost(post) {

  return `${post.id}: ${post.title} -> ${post.url}`;

}



function prettyPrint(posts) {

  return posts.map(formatPost).join(" | ");

}



console.log(prettyPrint(posts));
  Dennis Hackethal addressed criticism #3950.

Code blocks need syntax highlighting.

Veritula used to have this feature but I removed it when diffing changed.

#3950​·​Dennis HackethalOP, 3 months ago

Done as of cc1ab95.

Ruby example:

ruby
def criticized? idea

  pending_criticisms(idea).any?

end



def pending_criticisms idea

  criticisms(idea).filter { |c| pending_criticisms(c).none? }

end



def criticisms idea

  children(idea).filter(&:criticism?)

end

JS example (h/t ChatGPT):

javascript
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);

}
  Dennis Hackethal posted criticism #3950.

Code blocks need syntax highlighting.

Veritula used to have this feature but I removed it when diffing changed.

  Dennis Hackethal addressed criticism #3481.

Feature idea: pay people to criticize your idea.

You start a ‘criticism bounty’ of ten bucks, say, per pending criticism received by some deadline.

The amount should be arbitrarily customizable (while covering transaction costs). The user also indicates a ceiling for the maximum amount they are willing to spend.

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. They may even award a bounty to problematic criticisms, at their discretion. Inaction automatically awards the bounty to all pending criticisms at the end of the grace period. If doing so would exceed the ceiling, more recent criticisms do not get the bounty.

#3481​·​Dennis HackethalOP revised 4 months ago

Been trying a slight modification of bounties in prod for a couple of weeks or so. Working well so far.

@dirk-meulenbelt recently offered to chip in for a bounty I want to run. That got me thinking: multiple people should be able to fund bounties.

  Dennis Hackethal addressed criticism #3906.

How would you preview text in nodes?

#3906​·​Dennis HackethalOP, 3 months ago

Tyler says:

No preview necessarily, or the first sentence upon mouse-over could work. I’m imagining a structural view independent of the main view. (Though still suggest looking at columns for each idea in the main view).