Search Ideas
710 ideas match your query.:
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.
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.
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.
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.
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.
Rather than set a fixed amount for each unproblematic criticism (#3421), the ceiling could be divided among all criticisms equally.
That could be a good thing in that people won’t completely overwhelm OP with criticisms.
But that means that additional criticisms don’t get any payout.
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.
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.
There’s an encoding bug affecting title previews.
Benjamin suggests making it clearer that you can use Veritula by yourself.
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.
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.
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
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
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).
As of 9087189, the footer automatically hides and shows based on scrolling behavior.
Try it out and let me know if this doesn’t help.
As of c08f508, the footer automatically hides and shows based on scrolling behavior.
Try it out and let me know if this doesn’t help.
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(openingchar) + insert(closingchar) + 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 (nextchar == inputchar) { movecaret(+1); preventdefault(); }
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 (prevchar == open && nextchar == 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: surroundselection(inputpair)
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).
I haven’t used Obsidian, so I don’t understand what you are requesting. Is it that, whenever you open a bracket, you want the closing bracket to appear automatically?