silverwind

> Since there is a plan to move to self-hosting gitea (as far as I know), I think the bot should be compatible with gitea If there's nothing suitable, I...

It's probably not the best way to reward developers, but I see no problem in at least supporting it on a invisible api- or even database-only level.

I'd just kill the EventSource. As I see it, it's a graceful degradation if WebSocket doesn't work because the features that rely on it are not something I would consider...

As for reconnection behaviour, you can take a hint from [sockette](https://github.com/lukeed/sockette) or even use it as it's a tiny wrapper.

Actually I may have some SharedWorker WebSocket code with reconnects to share as I'm working on one currently. Still need to clean it up thought.

Here's my rather terse script of a SharedWorker that processes JSON on a WebSocket and does the reconnecting. It's based on sockette with all the cruft removed. I'm not sure...

Yes, sticky big TOC can get annoying because one has to scroll to the page end to scroll the TOC. For that reason, I'm undecided whether this change is a...

> We could give the TOC a max height with a scrollbar? No, nested scrollbars are generally confusing UX. One solution might be to sticky only if TOC height is...

No, I think a JS solution is probably not what we want right now. Let's see what others think about this change. I personally am undecided, pro's and con's are...

I think we want to keep them on the left and we should instead make more space in the box instead, e.g. make the wiki content box render with same/similar...