Dennis Hackethal
@dennis-hackethal·Joined Jun 2024·Ideas
Founder Veritula. Author. Software engineer. I study the mind and build tools for thinkers. Ex Apple. Translator of The Beginning of Infinity.
#2962·Dennis HackethalOP revised 4 months agoThe red ‘Criticized’ label shows how many pending criticisms an idea has. For example ‘Criticized (5)’ means the idea has five pending criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify pending criticisms.
There should be an easy way to filter comments of a given idea down to only pending criticisms.
As of 8e0a6e1, comments on each idea are shown in the following order: criticisms first, regular comments last. Within each category, uncontroversial comments are shown first. Lastly, comments are sorted by creation date (ascending).
#1869·Dennis HackethalOP, 5 months agoThe red ‘Criticized’ label could be clickable and filter the displayed comments ‘in place’.
Not as simple as #4349.
#1867·Dennis HackethalOP revised 5 months agoThe red ‘Criticized’ label could be a link leading to a filtered version of
ideas#show.
Not as simple as #4349.
#4274·Dennis HackethalOP, 19 days agoShould comments be sorted by controversial/uncontroversial first, date second?
More or less a duplicate of #4349.
#2962·Dennis HackethalOP revised 4 months agoThe red ‘Criticized’ label shows how many pending criticisms an idea has. For example ‘Criticized (5)’ means the idea has five pending criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify pending criticisms.
There should be an easy way to filter comments of a given idea down to only pending criticisms.
Could simply sort comments by pending criticism first, creation date second. (Variation of #4274.)
#4126·Dennis HackethalOP revised about 1 month agoFeature idea: pay people to criticize an idea.
You start a ‘bounty’ of an arbitrary amount (min. USD 5), which is prorated among eligible critics after some deadline.
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 writes terms for the kinds of criticism they want. This way, they avoid having to pay people pointing out typos or other unwanted criticisms.
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 has been implemented, sans page at /:username/bounties, which seems unnecessary.
Done.
Done, mostly as of 346fb25, then polished in 6dbf721, 5381525, 9f0f936, and 91e6f27.
#4128·Dennis HackethalOP, about 1 month agoNeed ‘standing’ bounties: they don’t expire. I keep finding myself wanting a standing bounty for #3069 so I don’t have to re-run expiring bounties.
Done.
When an empty block is passed to render, it results in an empty tag '<>'
Some Reagent-like way to make things reactive using proc as first element? And then the server keeps track of which procs have been rendered, which items have changed, and re-renders that part of the template in a turbo stream?
Use frame layout for turbo frame requests? https://discuss.rubyonrails.org/t/the-right-way-to-override-render-method/84765/2
Redirects result in two additional requests, the first of which is a turbo-stream request that renders nothing, thus (presumably) prompting the browser to make another request for the same resource.
Is there a way to teach user-built helpers how to process Hiccdown? Or maybe intercepting capture already took care of this?