todos + ideas

[jmoiron]

• fix blog rss
• fix blog atom
• fix cache headers on static
  • there were still some weird issues here, serving static directly from nginx for now
  • etags? etags will force rtt so maybe not?
• new version of font-awesome with stripped glyphs
• add bsky link
• fix stream loading
  • rebuild twitter stream off of twitter data dump
  • get bsky stream loading working
  • fix github stream loading
  • rewrite stream loading in Go (libs are probably good enough now)
• show loading indicator while wasm is loading in the split live view
• add a wiki app maybe what I really want is "notes" as wiki suggests it is user editable and it won't be

[jmoiron]

• It'd be nice to be able to stretch the entire authoring content area vertically and maybe horizontally for when I'm on a large screen and have some extra space.
• I am finding things that I thought used to be searchable to not really be retrievable anymore, so it'd be good to have a bookmarks app where I can also have a little description, archive link, maybe even a screenshot (or use the meta oc image)
• It would also probably be good to have a mobile layout, even though the normal site style adapts very well to mobile.

[jmoiron]

• File uploads app
  • Upload any kind of file
  • Customizable destination
  • Can add metadata to that file (name, etc)
  • Can preview files in the admin and edit/replace them depending on type
  • Blog should be modified to take photo drops as uploads, and track what images are attached to what posts

I want to be able to track my research on topics and make it public sometimes, but not on the blog. To this end, I think I want an experience something like:

• A "research" app which is built off of the "notes" app described below

  • Something I can consult while writing a blog post; perhaps a post editing mode with a "research panel" available?
  • Can attach notes/documents and bookmarks and reference them all quickly
  • Archive functionality? (the bookmark content is already available for now..)
  • Auto-generate a bibliography

• I want a note taking app, mostly for annotating papers

  • Should be able to upload a PDF
  • Or HTML bundle (v2)
  • Saves that document to an external documents directory (maybe)
  • Notes are markdown and refer to highlighted text or regions (depends on PDF.js maybe?)
  • Searchable by both document and note content

[jmoiron]

The template registry system needs some work.

I'd like to be able to have the possibility of always rebuilding template files, so I could pass it a normal fs.FS during development and work on templates w/o restarting the dev server. This is tricky to do right now, because each app registers its templates in mtr up front and after you call Build() the registry is essentially frozen.

This could be fixed in two ways, and I'm not sure which one I like more.

• build a "debug" mode into mtr and use the fss to pass alternative template paths for debug mode on registry, then swap mtr to debug mode when Debug=true
• expose enough build/rebuild interface to the application where I can use hotswap to swap out the underlying fs without mtr needing to know about "debug" mode.

I feel like 2 allows mtr to stay simple and it more elegantly exploits the power of interfaces, and I already have the hotswap and fss library built.

However, it might be too clever and tricky to debug, and this is potentially such a fundamental function of a template registry that the simpler solution of building this into the registry might be better.

---

On some reflection, doing this properly is complex and a similar result can be achieved without any special effort with a filesystem watcher tool like reflex.

It's actually not obvious what templates will be required for a given URL, since the change of eg. a base template could impact all URLs. To rebuild everything constantly seems silly; it should only build on change, but this would require filesystem watching, which is notoriously a bit weird to get spot on in a cross platform way.

I'm starting to build the vfs registry type, which will manage various filesystem mount points and the way that they are intended to map to URLs. This is intended to provide the following features:

• a single vfs that can be passed to various apps for them to look up "filesystem" mount points by name, so eg. the bookmarks app can look up a "screenshot" FS and also map paths within that FS to an appropriate URL for display on the FE.
• a file serving app that makes sure all of the fs mount points with URL mappings are available in dev mode
• an upload API helper that can be used by admin-side apps as a way to accept file uploads to be stored on particular FS points, like images for blogs or pdfs for the notes/research app