mazziechai / kose-kata Goto Github PK

I noticed that it took a very long time in ma pona when selecting a random note from a pool. This might be because of how the notes are retrieved and then chosen.

it's easier to learn note names when the content is displayed alongside the note's name.

i personally think a good spot for this is at the bottom, like #6770a0 tptpt

This could be solved with lazy pagination and retrieving of notes.
I'm not sure how to make this better with searching notes since the fuzzy search is in code rather than in MongoDB, which means that all notes have to be retrieved before a search.

A complaint is that there's too much information in the embed that isn't necessary.
A /info (ID) command should provide verbose information about a note as an embed. The message should not have the content of the note in it, and instead it should have a button to see the content in an ephemeral message.

Names can have multiple notes associated with them. When invoked through a regular viewing command, it chooses a random one from the notes associated with that name. However, this isn't always wanted behavior, and the option to reserve note names is necessary to prevent collision.

MongoDB has served us well, but I feel as if it's time we moved over to Postgres for performance reasons.

Logs for actions on notes should contain information for creation, deletion, editing, editing aliases, and editing its reserved name status. The view/usage count of a note will also be tracked.

Most interactions with kose kata are ephemeral. This makes it harder to moderate as there's no logs of it. Simply changing the type of the command should do, with minor adjustments.

The ability to reference a note by its ID should be there too, preferably with some syntax like [[id]].