• 0 Posts
  • 8 Comments
Joined 4 days ago
Cake day: May 2nd, 2026
  • BartyDeCanter@piefed.socialtoSelfhosted@lemmy.world•How to not loose important documents?English
    4·
    1 day ago

    I recently did a big expansion on my home networking infrastructure, and backups were one of bigger triggers.

    My setup is based on a local NAS + Hetzner storage box. The NAS runs Immich, Paperless, and the arr stack. Immich and Paperless back up to the storage box via borg, along with the configuration and docker files, but not the media. I either have physical copies of that or don’t really care because I can just download it again.

    My computers also back up to the storage box via borg, except for the Photos, Music and Video directories, for the same reasons. My partners Mac is currently backing up to an external USB drive, but the plan is to move them to Backblaze for the easy SAF and/or the NAS as a Timemachine target.

  • BartyDeCanter@piefed.socialtoRust@programming.dev•A note-taking app backend using RustEnglish
    1·
    1 day ago

    Plausible? Absolutely. The questions are what and why?

    For notes, it seems like most people have settled on one of three things: org-mode, markdown, or free form plain text. There are some closed source tools that use a proprietary format, but fuck them.

    So then the question becomes what does the backend do? Provide a way to query notes for links, topics, and todos? Keep a versioning system? Synchonization? Something else? Answer those questions and you have a project.

    For references, take a look at nb, Joplin, Logseq, org-mode, anytype.

  • BartyDeCanter@piefed.socialtoLearn Programming@programming.dev•How do you make terminal interfaces all fancy looking?English
    5·
    2 days ago

    Generally, yes, adapting to the size of the window is pretty easy. Most of those libraries have a layout engine, so you define the size of things relative to the size of the window and each other, then the layout engine takes care of the rest.

    As for discoverability, well, it’s a hard issue in all UI schemes, and tends to be particularly difficult in CLI/TUI applications due to layout and input constraints. In a GUI application users can click on buttons, scroll, and generally figure things out. For a tui, there are probably going to be a large number of (possibly reconfigurable) keyboard shortcuts and maybe some sort of command system. How you let the user know about all of them without having to memorize a giant table can be difficult. The common options I’ve seen are a “?” popup (lazygit), a context-aware small popup during multi-key commands (helix), a command palette with search (lots), a top menu bar with accelerator keys (old school WordPerfect), or a bottom bar with context available options (lots). They all have their respective tradeoffs, and can make something go from “useable after hours of practice and reading” to “oh, this is intuitive!”.