Veritula – Meta

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, 18 days ago

Done as of cc1ab95.

Ruby example:

1
2
3
4
5
6
7
8
9
10
11

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):

1
2
3
4
5
6
7
8
9
10
11

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, 18 days ago

Code blocks need syntax highlighting.

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

#3950·Dennis HackethalOP, 18 days ago

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

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

Code blocks need syntax highlighting.

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

#3950·Dennis HackethalOP, 18 days ago

1
2
3
4
5
6
7
8
9
10
11

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

1
2
3
4
5
6
7
8
9
10
11

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

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 about 2 months ago

How would you preview text in nodes?

#3906·Dennis HackethalOP, 23 days 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).

#3904·Dennis HackethalOP, 23 days ago

Let’s say somebody starts a bounty with permissive terms, asking for virtually any kind of criticism. They set a high ceiling, hoping for many submissions. $200, say.

If they only end up getting one or two small criticisms, for typos, say, they won’t like having to pay 100 bucks a pop.

In other words, the few criticisms you end up getting may not be worth the ceiling.

#3504·Dennis HackethalOP, about 2 months ago

Rather than set a fixed amount for each pending criticism (#3421), the ceiling could be divided among all pending criticisms equally.

#3474·Dennis HackethalOP revised about 2 months ago

The initiator of the bounty could choose a ceiling for the total they are willing to spend. They could additionally specify the amount per pending criticism.

For example, a user would indicate that they are willing to spend a total of $100 at $10 per criticism.

#3472·Dennis HackethalOP revised about 2 months ago

But that would mean that the first criticism receives a payout at the same time the last criticism receives a payout. That creates an incentive to ignore new bounties in favor of older ones.

#3430·Dennis HackethalOP, about 2 months ago