Dennis Hackethal
@dennis.hackethal·Joined Jun 2024·Ideas
Founder Veritula.
Author. Software engineer. Ex Apple. Translator of The Beginning of Infinity.
dennishackethal.com
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, 6 months 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, 6 months agoThe top level ideas could be rendered as turbo frames of
ideas#show.
While ideas load, cmd +f won’t work.
#2680·Dennis HackethalOP, 6 months 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.
#2676·Dennis HackethalOP, 6 months agoFor large discussions, wouldn’t that flood the server with requests?
#2677·Dennis HackethalOP, 6 months agoThe top level ideas could be rendered as turbo frames of
ideas#show.
Too many requests when there are enough top-level ideas.
#2677·Dennis HackethalOP, 6 months agoThe top level ideas could be rendered as turbo frames of
ideas#show.
I just tried this. Seemed promising at first but sometimes ideas load out of order. Looks horrible.
#2659·Dennis HackethalOP revised 6 months agoI could use
ActionController::Liveto stream top-level ideas to the page one by one. Instant page load.
cmd + f won’t work reliably.
#2635·Dennis HackethalOP, 6 months agoI 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.
That means cmd + f won’t always work.
#2630·Dennis HackethalOP revised 6 months agoDiscussions are getting slower to render as they grow. It’s a rendering issue (not a db issue).
The top level ideas could be rendered as turbo frames of ideas#show.
#2675·Dennis HackethalOP, 6 months agoI could have a separate route at
/ideas/:id/isolatedwhich 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.
For large discussions, wouldn’t that flood the server with requests?
#2630·Dennis HackethalOP revised 6 months agoDiscussions are getting slower to render as they grow. It’s a rendering issue (not a db issue).
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.
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.)
#2670·Dennis HackethalOP, 6 months agoIncompatible with Devise authentication: https://github.com/heartcombo/devise/issues/2332
The thread contains a suggested solution: use authenticated do … blocks in routes.rb instead of before_action :authenticate_user! in controllers.
#2659·Dennis HackethalOP revised 6 months agoI could use
ActionController::Liveto stream top-level ideas to the page one by one. Instant page load.
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.
#2659·Dennis HackethalOP revised 6 months agoI could use
ActionController::Liveto stream top-level ideas to the page one by one. Instant page load.
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).
#2659·Dennis HackethalOP revised 6 months agoI could use
ActionController::Liveto stream top-level ideas to the page one by one. Instant page load.
This page used to take ~3.5 seconds to load. Now it renders within 600ms :)
‘Veritula’ is a difficult name, people don’t know how to pronounce it. They usually can’t remember it.
‘Veritula’ is a difficult name, people don’t know how to spell or pronounce it. They can’t easily remember it.
#2654·Dennis HackethalOP, 6 months agoIdea: ‘The Second Renaissance’, ‘2nd Renaissance’, ‘2R’ for short.
‘Renaissance’ isn’t exactly easy to spell either.
The following commits should address this:
3af3966Clarify in title that someone revised an idea (rathen than originated idea)The HTML title now says ‘Idea x revised by…’
6c70ceaUnderneath 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
d20d386Explain that users can revise each others’ ideasAs part of the alert on the revision page, when the user is about to revise someone else’s idea.
c5748e3Turn ‘revise’ link into ‘revise their idea’ when it’s someone else’s ideaUnderneath each idea.
e0fbd41List user under each revision in version historySo that each version is clearly attributed to the corresponding user.
06d3241List contributors at top of version historyComma-separated list to see all contributors at a glance. Eg see here
The following commits should address this:
3af3966Clarify in title that someone revised an idea (rather than originated idea)The HTML title now says ‘Idea x revised by…’
6c70ceaUnderneath 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
d20d386Explain that users can revise each others’ ideasAs part of the alert on the revision page, when the user is about to revise someone else’s idea.
c5748e3Turn ‘revise’ link into ‘revise their idea’ when it’s someone else’s ideaUnderneath each idea.
e0fbd41List user under each revision in version historySo that each version is clearly attributed to the corresponding user.
06d3241List contributors at top of version historyComma-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.
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 ideas to the page one by one. Instant page load.
I could use ActionController::Live to stream top-level ideas to the page one by one. Instant page load.
#2646·Dennis HackethalOP, 6 months agoI could use
ActionController::Liveto stream 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.