- file-based event retrival. Point Caddy with `file_server` at it, and you have a dumb njump.me. - Script access. Instead of `EVENT=$(nak ... $NAK_FLAGS)` (and subsequently hammering pid space and cpu with repeated tasks), mounting events as a filesystem allows "any" application to use nostr. * If the FS also supports creating events, this might serve as a file-backend for a file-based CMS. - Mounting nostr events as a kubernetes volume (by mounting ontop of an emptyDir). Because lol. * ...and using that in a cronjob to use "arbitrary" tools like dagu to do things with nostr without teaching them how to nostr. - Backup. Speaking of cronjobs; just schedule a note dump with a cronjob. - Shell-fu. `find /mnt/nostr/$npub -type f -exec ...`. You know the random oneliners that save a day? Yeah, that. sed, grep, awk... even ripgrep and fdfind And put this all together? Load your dotfiles from nostr. Publish a dotfile-setup script to nostr and just source it: `(cat /mnt/nostr/note1... | jq -r ".content" > $HOME/.config/nostr.sh) && . $HOME/.config/nostr.sh` - truely have your dotfiles everywhere, literally platform independent :p (my solution is not the most elegant - but something like it...)

You want to run a boring old blog, on top of your nostr long form... Mount it on your blog server, have your static site generator or whatever read and build HTML from new notes. Then you can update your blog with any nostr client automatically.