Search Ideas

The following commits should address this:

• 3af3966 Clarify in title that someone revised an idea (rather than originated idea)

  The HTML title now says ‘Idea x revised by…’

• 6c70cea Underneath idea, indicate that someone revised an idea (rather than submitted it)

  It says ‘Dennis Hackethal, 1 day ago’ for new ideas, ‘Dennis Hackethal revised 1 day ago’ for revisions

• d20d386 Explain that users can revise each others’ ideas

  As part of the alert on the revision page, when the user is about to revise someone else’s idea.

• c5748e3 Turn ‘revise’ link into ‘revise their idea’ when it’s someone else’s idea

  Underneath each idea.

• e0fbd41 List user under each revision in version history

  So that each version is clearly attributed to the corresponding user.

• 06d3241 List contributors at top of version history

  Comma-separated list to see all contributors at a glance. Eg see here

Changing the view logic so that the controller can stream each deeply nested idea separately sounds non-trivial. It’s not clear to me how to do that currently. It may be possible someday if I adjust Hiccdown to allow the use of enumerators or something like that.

I could use ActionController::Live to stream top-level ideas to the page one by one. Instant page load.

Complex, requires non-trivial scroll listeners correlated to deeply nested ideas.

Just saw this app that lets you play ambient sounds at home: https://x.com/mirdhaaakanksha/status/1983238682154021218

Idea: ‘The Second Renaissance’, ‘2nd Renaissance’, ‘2R’ for short.

Replacing a raw SQL query in Idea.tree with a standard ActiveRecord query solves this issue.

I’ve since been able to reproduce the issue after all. Running a raw SQL query in Idea.tree in combination with the inclusion of the Live module seems to mess with Rails’s reloader.

A slow developer experience will slow down all further development, including bug fixes and feature rollouts, which hurts UX as well.

… copying extra stuff above and below the box quote, and neither gave me the > sign.

Cannot reproduce, neither on iPad nor macOS.

A single new idea somewhere down the tree could invalidate the cache and slow things down again.

Initial page loads would still be slow for users.

To be clear, if you copy the entire box quote and paste it into a textarea, it will start with the > sign. I just double checked.

You’re saying you’d still want the > if you only copy/pasted part of the box quote, right?

Cache invalidation for user-based caching sounds like a nightmare.

Feature idea: page at /ideas/:id/guide which shows you an idea and helps you address all pending criticisms one by one, if any. At the end, it shows a message ‘You’re all set!’ or something like that.

Done as of f2531a2.

… all of our knowledge is tentatively true.

This is still false, see #2603. You moved it from one place to another but I don’t see how that helped.

But you didn’t write my suggestions in your own words. You ignored them and instead wrote something else.

Fallibilism is the idea that all of our knowledge is tentatively true…

That isn’t true either.

I had already suggested replacements for the first sentence in both #2374 and #2589. At the time of writing, those ideas have no pending criticisms. You could have safely gone with either one.

Instead, you wrote something different for no apparent reason and introduced a new error in the process.

What are you doing man, come on

As of 2d3d38f, system-generated ideas are excluded from search results. They can be included again by checking a new checkmark in the form.

Now you’re using the word ‘certain’ with two different meanings, which is confusing. You could replace the second instance, “a certain”, with ‘some’ or just ‘a’.

Still, I don’t see why you’d use quotation marks for that. They don’t seem to be scare quotes, and they’re not a literal quote either.

Building on #2588, I recommend changing the opening lines of #2539 to something like ‘Fallibilism is the view that there is no criterion to say with certainty what’s true and what’s false. As a result, we inevitably make mistakes.’ And then adjust the rest accordingly.

In that case, I would agree with the second part of #2544 – just because something solves a problem doesn’t mean it’s guaranteed to be true, yes – but the first part is still wrong, IMO: “So there is no way to tell the truth of our knowledge.” There is, just not infallibly.

It certainly (pun intended) does not follow that all our knowledge contains errors, as you originally wrote.

… us[ing] terms like ‘good’ and ‘hard to vary’ in the sense of ‘not bad’ and ‘not easy to vary’ … eliminates the problem of gradation and positive argument, while preserving a shared and otherwise useful set of terminology.

Remembering and using the new meaning would take practice and effort. Why not just go with ‘has pending criticisms’ and ‘has no pending criticisms’ (or ‘problematic’ and ‘unproblematic’ for short)?