Some quick wins: - make the workspace persistent so you can resume what you were doing the last time you visited - the Swagger UI does this, not sure how but I suspect browser side storage. This might be easy for you. - more user feedback when you add a new block to the workspace. For example I kept clicking items from the toolbar wondering why nothing was happening until I finally realized a buttload of new objects had appeared in the workspace but weren't highlighted enough to notice them.

Some kind of auto-arrange would help a lot, starting with a pile of rectangles that you have to manually drag around to have any chance of making sense of it isn't ideal.

Graph diagrams look great but they fill a screen VERY quickly. There has to be a lot of thought into how to make the boxes as small as possible so someone can get the overall layout of the land, but can quickly access any details.

And the harder stuff would be some kind of assist dialog when you add a new toolbar item (I'm NOT going to suggest AI here, maybe just a dialog box which lists mandatory items and them other items in the order from most to least common). I understand this is tricky because you intend to support all API versions.

I ran into errors when I tried to download the schema, but then it suddenly started working, not sure why.

My first impression is that even with a high resolution laptop screen you're going to end up doing a lot of zooming in and out even for trivial deployments.

I imported the directory where I created those 3 yaml files and now have 3 connected boxes for the ingress, two for the deployment, and three for the service, but no interconnections between those three groups. It would be nice if the labels were cross connected between those groups, even better if when you were creating those groups from scratch you could specify the labels on one side then draw the edge connecting them and the label would get filled in on the other side and even get updated when one side changes. For example if I created a deployment with app.kubernetes.io/name of kubeforge and then was able to create the service object and link the edge and have that label connect.

I looked at Walabag and Shiori before I decided on Karakeep. I just didn't like the UI of the first two. I already have an Ollama server and the AI tagging feature of Karakeep is far better than Walabag's, in fact the tag management feature in general is. And Meilisearch adds a really fast search engine to Karakeep that has allowed me to discover new value to the 16k bookmarks from Pocket after cleaning down from the 20k I exported, it's super impressive.

Now the less great news, Karakeep is much newer and less mature than the other options and currently only supports a SQLite backend and I really hope that changes. The only API for Karakeep goes through its web interface and so I don't think I even could export all my bookmarks. If the data was stored in a standalone real database like MySQL or PostgreSQL other options would be possible.

The AI tagging is AMAZING but it generates a LOT of tags and that makes the tag management screens in Karakeep difficult or impossible to use because they are overwhelmed. I am looking forward to the next and future releases which aim to help with this.

I use the Android app which works really well.

Karakeep does make your server into a web crawler and because of the little war on AI LLMs we're experiencing these days an unfortunate number of websites have started to fight all crawling. Karakeep uses a SingleFile browser extension which allows you to prove you are a human or log in to a website and then capture a page and submit it to Karakeep. This is a little awkward because you may end up bookmarking something once using the regular Karakeep extension and then see that you didn't get what you want and have to do it again via SingleFile. I'm hoping that at least a config list will be added so that the regular Karakaap browser extension will automatically invoke SingleFile for websites known to block bots.