• 1 Post
  • 134 Comments
Joined 1 year ago
cake
Cake day: February 24th, 2025

help-circle






  • I have Paperless on home server and I am backing up offsite to StorJ (encrypted). I have it on TrueNAS that have native support for StorJ so its as easy as setting credentials and and filling a few form fields. I back up all of my non-media data there and it costs me less than 5 bucks per month. I realize you have different setup, this is just an example what I do. You can still spin up Paperless in LXC and make sure you back up to some offsite storage. You mention Proton Drive, that is another option if you really just need storage. They have data redundancy so the chance you will loose your data is virtually zero. Make sure you have recovery email though, if you forget your password no one can help you if you don’t have recovery email.








  • Lol nice coincidence 😀 Hope you will like it! There is still a date though, it’s not completely decoupled, but it’s more sliding window and I only mark the chores as overdue if missed, but it still sorts neatly which is what you might like 😊 I was thinking making it pwa, which i am not sure if it can send notification. I can check it out for sure because I think it would be useful. I don’t really know gotify, been using ntfy (selfhosted), so i gotta look into it and maybe what they have in common to do something more universal.


  • I am with you on the whole not wanting to use torrents. And also kinda have similar issue. I try to buy my stuff, but its becoming harder and harder avoid DRM.

    There is a benefit though in not having a huge library, I am not paralyzed with choice and I am more intentional with listening to my music. Almost like the good old days, taking a tape and sitting with my wired headphones next to a hi-fi system and “just” listening.






  • In case of NPM version pinning is a good practice. But also set it to ignore post install scripts. They are a bad practice and only about 2 % of all packages use it so it is unlikely it will bother you. They, the post install scripts, were used in recent supply chain attacks btw (the axios). You can either set it project wide in .npmrc file, add ignore-scripts=true, that is good for project where multiple people collaborate. And/Or system wide by running npm config set ignore-scripts true for your personal workspace. You can also achieve it by using --ignore-scripts flag during npm install, but that is way too impractical to always think about it. Also I would recommend checking npq, its a wrapper around npm cli that will give you some security summary before installing anything (and it is able to give you warning about post install scripts).