Rather than having the client constantly creating requests to refresh the board, have the server push updates to clients every 10 seconds or so. Only send updates if there's new content. This is much more efficient as it removes unnecessary requests from the client and sends just the data that's been changed.

Typing ">" in a document unit sometimes doesn't autofill the "<" but it does pull up the search box. No search query in input after typing.

How should we deal with this? Might be able to automatically unfocus the unit from any attached discussions... Alternatively could prevent deleting while discussions are attached.

Maybe have logging in prod to see what is going on.

This is probably just a dev problem, but is worth investigating to see if it occurs with a stable database as well.

We are potentially loading a lot of data on the board. Need to think of a better prefetching/caching startegy. Detangle routes from loading perhaps to avoid issue of leaving discussion, going to board, and loading it back to a "beginning state"?

Backend allows for you to add already pinned units to the pinned section, this should be prohibited and fail silently.

Backend: only send past 25 messages. Add a pagination route so we can request page 0, 1, 2 and so on infinitely.

Frontend: better loading indicator for chat. Detect when top of element is hit and make next page request. Keep track of current page in discussionDisplayStore.

• Must always filter on current board.
• Use keywords.
• Can also search within current discussion. Search within just chat or block units.
• For discussion units, can filter on author/time.

Currently anything that was sent > 25 messages ago is not loaded in until you scroll up. This means that stuff on the summary is not loaded initially.

Add a dragging handle so units from the chat can be moved to the document.

Use the same layout as the chat, except units should flow from the top

Allow people to show an "indicator" in real-time, somewhat similar to Zoom.
Have to consider where this indicator appears (i.e. next to user icon?)

Consider later.

When new posts are added the date given is based on when the server started, not when the post was made.

Happens when you reload, the connection to the server is not reestablished.

Make it clearer you can click on any unit on the board in order to form a link. Also allow for canceling creating a link once started.

Remove references to react, include svelte

Use double brackets, allow spaces inside but not inside brackets.

Valid:

[[ feugswd53yb5 ]]

[[feugswd53yb5]]

[[feugswd53yb5 ]]

Invalid:

[ [ feugswd53yb5 ]]

[ [feugswd53yb5 ] ]

[[feugswd53yb5] ]

Standardize all valid to:

[[feugswd53yb5]]

In board mode, the whole space can be dedicated to the 2D board.

In discussion mode, first divide the screen in half so the left is for discussion and the right is for board. On the left side, the half-section is further halved into a chat section and a summary section. It is important each feels equal in weight, that the summary feels as important as the ongoing discussion. On the right side, put the focus on the top, such that the board feels like a square. The square shape will give the psychological feeling that we see "more at once".

Currently just have text undefined. Need it to be more distinguishable.

Existing solutions, like in React, are too big, or others are too specific.
May need to cook-up something ourselves.

Need:

• seemingly infinite space, with origin (in center of div), and maybe bounding box
• panning => library?
• zoom in/out => library?
• rendering of basic shapes, like rectangles and arrows (arrows could get messy!)
• drag and drop, but on a grid => will have to worry a bit about arrow rendering

How do existing methods do it, like mind-mappers or design spaces? Excalidraw, kinopio.club, Figma.
Excalidraw and others use a more heavy solution, which feels rather slow.

For now, maybe use kinopio solution. Origin is at top-left, uses native scrollbars and zooming. For "arrows", there is a line that draws from one point to another. This is a pretty smart idea. The nodes are always rendered above the lines. The lines don't have directionality. Maybe instead of having an arrow point at the end, the line itself has chevrons on it indicating direction. Also, requires dragging to make line. Would be nicer to do a click-click.

Gotta have it

Get rid of the dialog. Maybe do the banner thing, like the one for errors but in a different color (i.e. green), to say they copied it successfully.

Write some load testing cases with something like artillery.

This is most important for entities like units that will probably be great in number in the theoretical case.

Should we let people create new boards someplace other than the command line? Could be nice to have to get people to create boards themselves rather than just joining existing ones...

When reloading the page in a discussion.

Clicking "Your discussions" to return to the root doesn't re-render the page. Something like this....

if subscribing pinned/focus, makes it easier to avoid dups on frontend

I wrote this already, just need to use it.

Not sure why this is happening... seems to happen pretty rarely.

Right now we're naively appending to the end of the unit ID array in state. Make sure that's a safe solution.

{each} iterates only over array like objects

Is a type of unit.
Add two new fields: beam (boolean), purpose (str).

Beams are treated the same as unit in the store. However, they are rendered specially, maybe with a special color, and the purpose should be displayed.

When creating a unit, can choose whether it is a beam. Thus, modify add_unit from add_unit(board_id, text) to add_unit(board_id, text, beam=False, beam_purpose=None).

Linking a unit in a discussion chat or document results in a very long ID. It would be better if these IDs were short and unique to just the discussion. For example, a chat unit would be "c003" or "c023" and a document unit might be "d532". It helps tell the unit type apart and promotes readability in the unit editor.

Currently, the backend sends a map of transcluded IDs for every post that has transclusions. This should be changed to an array so the order transclusions appear is preserved.

Currently:

{
    "k5rxb5t2owyu": "hello, this is a post",
    "ocy83cof8964": "some idea"
}

Ideally:

[
    { "id": "k5rxb5t2owyu", "pith": "hello, this is a post" },
    { "id": "ocy83cof8964", "pith": "some idea" }
]

It would be nice to be able to support markdown formatting in the editor. Right now the only way to format text is with meta + i/u/b, which uses document.exec to insert the proper html tag around the selected text. In ContentEditable.jsx we should add "" or "*" chars automatically around bold or em tags, and do the opposite when someone adds "" chars around a selection of text.

• Rename to "summary"
• Increase width, reducing chat and board width to accommodate
• Increase height so it takes 2/3 rather than 1/2 of vertical space

We need something. Probably not "jim is typing...", but perhaps just some little animated ellipses when typing is happening.

This will require creating some client logic to determine if someone is typing and sending start and stop events to the backend. The backend can then send updates to all clients to indicate typing is or is not taking place.

Don't propagate click events on the input down to the unit itself.