egui_node_graph VS tubearchivist

I want the DAG to be explainable so to handle type safety ( think that's what you're getting at?) in a user friendly way, I've been looking into using this library to draw the DAG interactively, save this to disk, and then I will then consume this in a macro to actually write the final executable.

Did you consider to use egui_node_graph ?

I was looking for something similar and found https://github.com/setzer22/egui_node_graph

Gankra's work on a useful rust memory model is both fascinating and useful: https://twitter.com/Gankra_/status/1509335163045650436

This tool to convert low-complexity rust tests to proofs is interesting and something I'm glad I know exists: https://model-checking.github.io/kani-verifier-blog/2022/05/...

I'm using this code I found out about via reddit in a side project, probably less interesting to you though: https://github.com/setzer22/egui_node_graph

(Warning, videos from here on out):

Cool product demo of a futuristic debugger: https://www.hytradboi.com/2022/debugging-by-querying-a-datab...

These people also have a cool demo of splitting a single program across two different computers (frontend and backend webserver in their case). Maybe a bit less convincing than the previous one, but something I intend to watch: https://www.hytradboi.com/2022/uis-are-streaming-dags

These people have some really cool work on automatically solving physics problems (just linking to one of their talks as an example): https://www.youtube.com/watch?v=WHhDgxkiR9c

holy hell I hadn't come across archivebox as of yet, I'll definitely be spinning this up this eve. Is the UI comfortable enough to use as a "bookmark manager"? just been setting up tubearchivist for essentially this purpose, wondering if ArchiveBox would essentially do the same

I'm using TubeArchivist to maintain this VERY large collection.

There appears to be a patch in Tubearchivest at https://github.com/tubearchivist/tubearchivist/issues/587

Personally, I use Tubearchivist.

There are others though.

https://github.com/tubearchivist/tubearchivist

I've been seeing TubeArchivist posted a lot recently.

It has been some time since the last release, but v0.4.0 is finally wrapped up. This brings a wide range of fixes and changes, particularly stability improvements, with our new file system naming convention, this should solve a bunch of previously unsolvable compatibility issues. I highly recommend reading the release notes carefully, as the filesystem migration could be a breaking change if you made changes manually there: https://github.com/tubearchivist/tubearchivist/releases/tag/v0.4.0

I saw this was a Django app so I dug around to look at their models. As far as I can tell this is all they have: https://github.com/tubearchivist/tubearchivist/blob/master/t... - just a `Account` model.

It looks like Django + SQLite is used for user accounts, but all other data storage happens in Elasticsearch.

It's an interesting design decision. I would have gone all-in on the database, and used SQLite FTS in place of Elasticsearch for simplicity, but that's my own personal favourite stack. Not saying their design is bad, just different.

Oh, so it is. I happen to run a TubeArchivist at home that grabs the videos and subtitles. Then I can search through the subtitle files for key phrases. I must have grabbed it while it was still public.

You probably want Tube Archivist. The only problem is that it’s naming convention doesn’t work with the Jellyfin YouTube Metadata Plugin.