[feat] Static HTML as a user setting #368
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#368
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea
Hey all.
I think it'd be great if Static HTML generation was a user setting, rather than a server one. Static HTML generation is a great tool for creating less overhead on the user-side, but having it enabled for every user on the server just seems like a bad idea, given that it breaks some things.
The reasoning
Have you searched for this feature request?
It would be helpful if you report said things that break due to static-fe.
that's just an argument in favor of static-fe, not of your feature request
could you please elaborate? this isn't really a reasoning
Remote following is the only one I can think of off the top of my head right now.
honestly, making static-fe interactive would be one heck of an undertaking
it's currently read-only and just there to provide a cacheable response for external people
making it interactive would require some huge auth changes, considering everything works on oauth
Isn't this really just a question for having multiple front-ends? So some people can use the static-fe while others can choose to use a more JS-based fe? If so, this is already possible. Some instances already do that with bloat-fe for example (which you can e.g. host on a subdomain). See also https://docs.akkoma.dev/stable/clients/.