Dennis Hackethal
@dennis-hackethal·Member since June 2024
Badges
Activity
#2701·Dennis HackethalOP revised about 19 hours agoOld ideas can pollute discussions. Like in this meta thread.
Proposed solution: allow people to archive ideas. Maybe only their own.
#2708·Dennis HackethalOP, about 18 hours agoThere could be periodic reminders and a review board to make it easier.
That could just annoy people and cause them to unsubscribe from emails.
#2706·Dennis HackethalOP, about 19 hours agoThis could inadvertently hide dormant but important ideas.
Could do it only for ideas with pending criticisms. If they have pending criticisms, how important can they be? This has the added benefit of creating an incentive for proponents of ideas to address criticisms.
There could be periodic reminders and a review board to make it easier.
#2703·Dennis HackethalOP, about 19 hours agoProposed solution: 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.
People might just forget to do this.
#2704·Dennis HackethalOP, about 19 hours agoProposed solution: ideas could be archived automatically if they haven’t been revised or criticized in 90 days, say.
This could inadvertently hide dormant but important ideas.
#2703·Dennis HackethalOP, about 19 hours agoProposed solution: 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.
This requires manual action. Could mean a lot of work depending on the discussion.
#2701·Dennis HackethalOP revised about 19 hours agoOld ideas can pollute discussions. Like in this meta thread.
Proposed solution: ideas could be archived automatically if they haven’t been revised or criticized in 90 days, say.
#2701·Dennis HackethalOP revised about 19 hours agoOld ideas can pollute discussions. Like in this meta thread.
Proposed solution: 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 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.
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 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.
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.
This problem will surface rarely – users would have to hit cmd + f immediately upon opening the page. For most users, by the time they start typing, the page is already fully loaded. So this seems like a small price to pay in exchange for discussion pages that always render faster.
Now that parts of the page are purposely and visually disabled (see #2694), users may not expect everything to be working 100% during a loading state.
#2671·Dennis HackethalOP, 2 days agoJS 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.
I now purposely prevent interactions with buttons and gutters, and gray them out, until the page is fully loaded. So instead of broken hover effects and interactions, the user gets intentionally disabled elements, and this intentionality is communicated to them.
Once the page is fully loaded, buttons and gutters are enabled and visually restored.
Since the browser’s loading indicator remains visible until then, this behavior shouldn’t violate user expectation.
#2692·Dennis HackethalOP, 2 days agoI could override
authenticate_user!in theDiscussionsController.
That means duplicate functionality; anytime I customize Devise in the future, I’ll have to remember to adjust this one method as well.
#2670·Dennis HackethalOP, 2 days agoIncompatible with Devise authentication: https://github.com/heartcombo/devise/issues/2332
I could override authenticate_user! in the DiscussionsController.
#2670·Dennis HackethalOP, 2 days agoIncompatible with Devise authentication: https://github.com/heartcombo/devise/issues/2332
I could extract discussions#show into a new, separate StreamController or something like it. That controller would not use Devise.
#2688·Dennis HackethalOP revised 2 days agoThe thread suggests a workaround: use
authenticated do …blocks inroutes.rbinstead ofbefore_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.)
Then again, I’d want to redirect users to the sign-in page (and then ideally back to where they were trying to go).
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.)
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 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 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.)
#2636·Dennis HackethalOP, 5 days agoOn 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.
#2677·Dennis HackethalOP, 2 days agoThe top level ideas could be rendered as turbo frames of
ideas#show.
While ideas load, cmd +f won’t work.
#2680·Dennis HackethalOP, 2 days agoI just tried this. Seemed promising at first but sometimes ideas load out of order. Looks horrible.
I could render the first ~10 top-level ideas immediately and only render the rest as turbo frames off screen. By the time the user scrolls down, they should all be loaded.