- 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...)
IngwiePhoenix / Ingwie Phoenix
npub1tc…hjmky
2025-03-10 22:11:50
in reply to nevent1q…xh3u
Author Public Key
npub1tcekjparmkju6k83r5tzmzjvjwy0nnajlrwyk35us9g7x7wx80ys9hjmkyPublished at
2025-03-10 22:11:50Event JSON
{
"id": "c8e9481414bab6c3eb135552ab0c61f39025a599002fbca30489c12d8e39bad5",
"pubkey": "5e336907a3dda5cd58f11d162d8a4c9388f9cfb2f8dc4b469c8151e379c63bc9",
"created_at": 1741644710,
"kind": 1,
"tags": [
[
"e",
"0000daa8e795a5a089ac03556a167a206f8045a3bb7370837bd5eef9123b8866",
"wss://relay.nostr.band/",
"root",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"e",
"000003a5ca5048f680dfb7dcb6704d40c5a4130b69294ef3a500487823854a52",
"wss://nos.lol/",
"reply",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"5e336907a3dda5cd58f11d162d8a4c9388f9cfb2f8dc4b469c8151e379c63bc9"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "- file-based event retrival. Point Caddy with `file_server` at it, and you have a dumb njump.me.\n- 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.\n* If the FS also supports creating events, this might serve as a file-backend for a file-based CMS.\n- Mounting nostr events as a kubernetes volume (by mounting ontop of an emptyDir). Because lol.\n* ...and using that in a cronjob to use \"arbitrary\" tools like dagu to do things with nostr without teaching them how to nostr.\n- Backup. Speaking of cronjobs; just schedule a note dump with a cronjob.\n- 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\nAnd 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\" \u003e $HOME/.config/nostr.sh) \u0026\u0026 . $HOME/.config/nostr.sh` - truely have your dotfiles everywhere, literally platform independent :p (my solution is not the most elegant - but something like it...)",
"sig": "0635d133b9d9b3961f905a89012a12edd670b98fdab2cc8c3aa9511db959668371c0bfaf1af3f3ef0f12b5bcb045d8372c2df593a7d62cebc3c800e93657c060"
}