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.

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.

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: ‘Return to Reason’, ‘RR’

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

‘Veritula’ is a difficult name, people don’t know how to pronounce it. They usually can’t remember it.

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.

After resetting my working directory and beginning to implement streams a second time, I can no longer reproduce this issue, despite reasonable attempts to reproduce it.

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

Fast UX is more important than fast developer experience.

Including that module significantly slows down hot reloads on all pages. I need a tight feedback loop in dev.

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

Ah, but I can reproduce when I manually make the selection by clicking and dragging to cover the entire quote.

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

Cannot reproduce, neither on iPad nor macOS.

I tried copying the entire quote…

Cannot reproduce. If I triple-click a word in a box quote, then copy/paste, I get the > sign.

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.

On initial page load, I could just load the first ten or so top-level ideas and their immediate children, just to reduce wait times and populate the page. Then load the rest asynchronously.

I could lazy load ideas: only load the parts of the page that would be visible on the current viewport. Then load more parts as the user scrolls.