Search Ideas

Old ideas can pollute discussions. Like in this meta thread.

I can still reproduce the issue by clicking on the button to collapse/expand an idea.

Feature idea: edit a discussion to hide top-level ideas. That way, discussion owners can hide ideas they no longer deem relevant.

For example, completed tasks in discussions used as issue trackers, like this Meta thread, could be hidden so they don’t pollute the thread.

There could be a button for users to reveal hidden ideas so nothing is lost or hidden dishonestly. And direct links to hidden ideas would continue to work.

Feature idea: edit a discussion to hide ideas. That way, discussion owners can hide ideas they no longer deem relevant. (For example, completed tasks in discussions used as issue trackers, like this Meta thread.) There could be a button for users to reveal hidden ideas so nothing is lost of hidden dishonestly.

I could override authenticate_user! in the DiscussionsController.

The thread suggests a workaround: use authenticated do … blocks in routes.rb instead of before_action :authenticate_user! in controllers.

It’s probably a good idea to do this anyway to avoid divulging the existence of routes that unauthenticated users don’t need to know exist. (They will get a 404 instead of a 401.)

The thread suggests solution: use authenticated do … blocks in routes.rb instead of before_action :authenticate_user! in controllers.

It’s probably a good idea to do this anyway to avoid divulging the existence of routes that unauthenticated users don’t need to know exist. (They will get a 404 instead of a 401.)

I just tried this. Seemed promising at first but sometimes ideas load out of order. Looks horrible.

cmd + f won’t work reliably.

The top level ideas could be rendered as turbo frames of ideas#show.

I could have a separate route at /ideas/:id/isolated which renders only the idea without any parents or children. And then a discussion could render a bunch of deeply nested turbo frames loading that route.

The thread contains a suggested solution: use authenticated do … blocks in routes.rb instead of before_action :authenticate_user! in controllers.

It’s probably a good idea to do this anyway to avoid divulging the existence of routes that unauthenticated users don’t need to know exist. (They will get a 404 instead of a 401.)

The thread contains a suggested solution: use authenticated do … blocks in routes.rb instead of before_action :authenticate_user! in controllers.

JS modules are always deferred and unusable until the page is fully loaded. As a result, comment buttons and gutters won’t work while ideas are still streaming onto the page.

Incompatible with Devise authentication: https://github.com/heartcombo/devise/issues/2332

Feature idea: pay people to address criticisms (either revise an idea and check off criticisms or counter-criticize).

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

‘Renaissance’ isn’t exactly easy to spell either.

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.

Idea: ‘Return to Reason’, ‘RR’

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

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.

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.