| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Yes, I'm stupid and I'm developing under a custom theme
|
| |
|
| |
|
|
|
|
| |
TODO: make requested scopes parametrized
|
|
|
|
|
|
|
| |
This helps unify HTTP-related settings in one place.
In Relm4 Matrix chatroom, it was said that deconstructing child
components makes little sense in terms of optimizations.
|
|
|
|
|
|
| |
The code is really janky and unpolished, the error handling is
TERRIBLE, and I think I can't publish it like this. This'll need a
refactor, but it'll come tomorrow.
|
| |
|
| |
|
|
|
|
|
| |
Now it's easy to use the same UI for sending a new post or editing an
existing one (by loading it with `?q=source` and then comparing).
|
|
|
|
|
|
|
| |
What this command should do is construct a summarization request and
return a future which would return chunks from the LLM.
Perhaps this component will be asyncified in the future.
|
|
|
|
|
| |
On receving `smart_summary::Output::Start`, one must reply with
`smart_summary::Input::Text(text)` to start the actual summarization.
|
|
This is a little bit janky in my opinion, because it takes a reference
to the buffer which contents its gonna be summarizing. In a perfect
world, it would ask the parent component for the text.
|