Search

Words match in any order. "many worlds" matches the phrase exactly; -gravity excludes ideas with “gravity”.

Ideas that are…

Search Ideas


914 ideas match your query.:

That seems like a tough sell. Users might not be willing to spend money without knowing whether anyone will submit any criticisms.

#3437·​Dennis HackethalOP, 11 months ago·​CriticismArchived

What if Veritula charges the card immediately and holds the funds?

#3436·​Dennis HackethalOP, 11 months ago·​Criticism1 pending criticismArchived

Maybe, but what if re-authorization fails? Then nobody gets paid.

#3435·​Dennis HackethalOP, 11 months ago·​CriticismArchived

Couldn’t I let the initial authorization expire and then re-authorize the card?

#3433·​Dennis HackethalOP revised 11 months ago·​Original #3432·​Criticism1 pending criticismArchived

Couldn’t I re-authorize the card?

#3432·​Dennis HackethalOP, 11 months ago·​Criticism1 pending criticismArchived

The bounty initiator’s card will have to be authorized when starting the bounty. Card authorizations presumably have a deadline, so resetting the deadline won’t be an option.

#3431·​Dennis HackethalOP, 11 months ago·​Criticism Battle-tested · 4Archived

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, 11 months ago·​Criticism2 pending criticismsArchived

Unlike #3424, however, having a set amount per criticisms means there’s zero incentive for anyone to submit more criticisms, whereas divvying up the amount among criticisms means the incentive is gradually reduced, and it’s up to people to decide for themselves whether contributions are still worth making.

#3428·​Dennis HackethalOP revised 11 months ago·​Original #3425·​Criticism1 pending criticismArchived

Unlike #3424, however, having a set amount per criticisms means there’s zero incentive for anyone to submit more criticisms, whereas divvying up the amount among criticisms means the incentive is gradually reduced, and it’s up to people to decide for themselves whether the reduction is still worth contributing.

#3426·​Dennis HackethalOP revised 11 months ago·​Original #3425·​Criticism1 pending criticismArchived

Unlike #3424, however, having a set amount per criticisms means there’s zero incentive for anyone to submit more criticisms, whereas divvying up the amount among criticisms means the incentive is gradually reduced, and it’s up to people to decide for themselves whether the reduction is still worth contributing.

#3425·​Dennis HackethalOP, 11 months ago·​1 pending criticismArchived

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

#3424·​Dennis HackethalOP, 11 months ago·​1 pending criticismArchived

That could be a good thing in that people won’t completely overwhelm OP with criticisms.

#3423·​Dennis HackethalOP, 11 months ago·​Criticism1 pending criticismArchived

But that means that additional criticisms don’t get any payout.

#3422·​Dennis HackethalOP, 11 months ago·​Criticism1 pending criticismArchived

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

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

#3421·​Dennis HackethalOP, 11 months ago·​1 pending criticismArchived

Yes, people could just start bounties on criticisms.

#3420·​Dennis HackethalOP, 11 months ago·​Archived

Idea: voice spaces, like Twitter spaces, except an AI generates a transcript and automatically turns it into a discussion tree, with criticism chains and all.

#3419·​Dennis HackethalOP, 11 months ago·​1 pending criticismArchived

Fixed as of bd7c1b6.

#3416·​Dennis HackethalOP, 11 months ago·​CriticismArchived

There’s an encoding bug affecting title previews.

#3415·​Dennis HackethalOP, 11 months ago·​Criticism1 pending criticismArchived

Done, see #3413.

#3414·​Dennis HackethalOP, 11 months ago·​CriticismArchived

Benjamin suggests making it clearer that you can use Veritula by yourself.

#3409·​Dennis HackethalOP, 11 months ago·​Criticism1 pending criticismArchived

I have implemented 1-4. Give it a try. I think 5 is out of scope for now but I may revisit it at some point. If auto-closing asterisks are a problem at the start of a line (when making lists), use a hyphen instead.

#3399·​Dennis HackethalOP, 11 months ago·​CriticismArchived

On second thought, implementing a proper text editor would take more work than I initially realized, and is far beyond the scope of what Benjamin is requesting anyway. I can revisit this idea later.

#3398·​Dennis HackethalOP, 11 months ago·​CriticismArchived

I can take this opportunity to replace manual markdown with a proper text editor. Then there’s no need for autopaired brackets.

The editor will need to support:

  • Automatic links to ideas like #123
  • Links to @mentions like @dennis-hackethal*
  • Safe link formatting
  • Disabling of turbo links
  • Namespaced footnotes
  • Custom blockquote format
  • Protection against XSS
  • Retention of formatting when pasting
#3397·​Dennis HackethalOP revised 11 months ago·​Original #3396·​1 pending criticismArchived

I can take this opportunity to replace manual markdown with a proper text editor. Then there’s no need for autopaired brackets.

The editor will need to support:

  • Automatic links to ideas like #123
  • Links to @mentions like @dennis-hackethal*
  • Safe link formatting
  • Disabling of turbo links
  • Namespaced footnotes
  • Custom blockquote format
  • Protection against XSS
#3396·​Dennis HackethalOP, 11 months ago·​Archived

I’ve asked Gemini to explain it:

1. Auto-Closure (Insertion State)

When the user inputs an opening delimiter, the system immediately injects the corresponding closing delimiter and places the caret (cursor) between them.

Input: (

Buffer State: (|)

Logic: insert(opening_char) + insert(closing_char) + move_caret(-1)

2. Type-Through (Escape State)

If the caret is positioned immediately before a closing delimiter that was autopaired, and the user types that specific closing delimiter, the system suppresses the character insertion and instead advances the caret.

Context: [text|]

Input: ]

Buffer State: [text]| (Not [text]])

Logic: if (next_char == input_char) { move_caret(+1); prevent_default(); }

3. Atomic Deletion (Regression State)

If the caret is between an empty pair of delimiters, a backspace event deletes both the opening and closing characters simultaneously, returning the buffer to the pre-insertion state.

Context: (|)

Input: Backspace

Buffer State: |

Logic: if (prev_char == open && next_char == close) { delete_range(caret-1, caret+1); }

4. Selection Wrapping (Transformation State)

If a text range is selected (highlighted) and an opening delimiter is typed, the system wraps the selection rather than replacing it.

Context: |selected_text|

Input: [[

Buffer State: [[selected_text]]

Logic: surround_selection(input_pair)

5. Markdown-Specific Heuristics

Obsidian applies context-aware logic for Markdown syntax (e.g., * or _). It often checks word boundaries to determine if the user intends to bold/italicize or use a bullet point.

Context (Start of line): | + * + Space -> Bullet list (autopair disabled/consumed by formatting).

Context (Middle of line): word | + * -> word *|* (autopair enabled for italics).

#3372·​Dennis HackethalOP revised 11 months ago·​Original #3271·​Criticism1 pending criticismArchived