Traditionally, retiring entails leaving the workforce permanently. However, experts found that the very definition of retirement is also changing between generations.

About 41% of Gen Z and 44% of millennials — those who are currently between 27 and 42 years old — are significantly more likely to want to do some form of paid work during retirement.

...

This increasing preference for a lifelong income, could perhaps make the act of “retiring” obsolete.

Although younger workers don’t intend to stop working, there is still an effort to beef up their retirement savings.

It's ok! Don't ever retire! Just work until you die, preferably not at work, where we'd have to deal with the removal of your corpse.

About a year and a half ago I posted a script I made for deleting movie content in your library not being watched. Folks really seemed to like it, and I still get comments on that thread every so often. So I've updated it!

Far and away, the two biggest requests I got were:

• Make it do TV, too
• Make a dry-run mode
• Edit: Added just now: a protected mode when you volume mount a protected file!

The code is now available on github here:

https://github.com/ASK-ME-ABOUT-LOOM/purgeomatic

Even better, no installation is required. You can run it as a docker container like so:

docker run --rm -it --env-file .env --network=host ghcr.io/ask-me-about-loom/purgeomatic:latest python delete.movies.unwatched.py

It now supports TV series as well. Thanks to a suggestion from /u/JimLahey-, I was able to get my head around the idea - I had always thought of managing TV shows as "collections of seasons" of media, but the reality is, if nobody has watched anything related to a TV show in a while, the whole thing can go! And that's what this does:

docker run --rm -it --env-file .env --network=host ghcr.io/ask-me-about-loom/purgeomatic:latest python delete.tv.unwatched.py

No more editing python, either. Create yourself a .env file, set up all of your config, and even enable dry run mode, so you can test to your heart's content:

$ docker run --rm -it --env-file .env --network=host ghcr.io/ask-me-about-loom/purgeomatic:latest python delete.movies.unwatched.py
DRY_RUN enabled!
--------------------------------------
2023-08-25T12:40:57.288608
DRY RUN: Chaos Walking | Radarr ID: 1445 | TMDB ID: 412656
DRY RUN: Captain Marvel | Radarr ID: 885 | TMDB ID: 299537
DRY RUN: Captain America: Civil War | Radarr ID: 1768 | TMDB ID: 271110
DRY RUN: Black Widow | Radarr ID: 1517 | TMDB ID: 497698
DRY RUN: Birds of Prey (and the Fantabulous Emancipation of One Harley Quinn) | Radarr ID: 1092 | TMDB ID: 495764
DRY RUN: Bill & Ted's Excellent Adventure | Radarr ID: 1777 | TMDB ID: 1648
DRY RUN: Bill & Ted's Bogus Journey | Radarr ID: 1778 | TMDB ID: 1649
DRY RUN: Big Hero 6 | Radarr ID: 71 | TMDB ID: 177572
DRY RUN: Big | Radarr ID: 71 | TMDB ID: 177572
DRY RUN: Batman Begins | Radarr ID: 1745 | TMDB ID: 272
DRY RUN: Assault on Precinct 13 | Radarr ID: 1212 | TMDB ID: 17814
DRY RUN: 21 Jump Street | Radarr ID: 1096 | TMDB ID: 64688
Total space reclaimed: 164.88GB

To use protected mode, just create a text file with one TMDB/TVDB ID per line and volume mount it as /app/protected like so:

docker run --rm -it --env-file .env --network=host -v /home/user/protected:/app/protected ghcr.io/ask-me-about-loom/purgeomatic:latest python delete.movies.unwatched.py

Good luck! Please let me know if you have questions or problems and I'll do my best to help out!

I recently stood up a new file server using ZFS on linux. I'd like to automate the disk checking in such a way that I can essentially ignore and have a service notify me when SMART or other indications are hitting failure or pre-fail levels.

I'm not looking for a fancy GUI or web UI - a plain old config file would suit me just fine. In my ideal world, it would be a container I could simply spin up with minimal configuration, but I'm willing to give anything a try.

I comment more frequently than I post. Is there any way to set it to view comments by default? Even better, can we display a merged view of comments/posts in a single listing?

The fact that BW is open-source allowing the ability to self-host is a very awesome and unique feature. The fact that Dani Garcia ported the code and allowed you to host vaultwarden on a low-power device like a Pi or a small VPS is even more awesome. The fact that they both made it easy to install and run the service with Docker etc., and that there are a lot of guides on how to set the whole thing up is super awesome. You can play around, learn some things, and get control of your own data. It's all awesome. But none of that is a security feature.

BW started as a tool for enthusiasts, people who probably can review and compile source code, set up a server, and run services securely -- seasoned c/selfhost@lemmy.ml folks. Maybe in their hands, a self-hosted instance of BW can come close to the security provided by the official service. If they are experts in the field, maybe they can make it even more secure. Maybe.

For most people visiting this sub today that is patently untrue!

Most self-hosting posts today are chock-full of comments asking how to register a domain or set up dynamic DNS, or asking what is Docker. Do you honestly think that these people are knowledgeable enough to set up their own BW service securely? Are they knowledgeable enough to evaluate the original team, their product, its source, and its security; to evaluate a completely different team, with a different source; to set up a secure server and host a service without succumbing to all the pitfalls of novice self-hosting; and to do it better than the guys at Azure?

Hell No!

The fact remains that for the greatest majority of people coming here, using the official BW service hosted by Microsoft remains the most secure way to use Bitwarden. That should be the default advice on this sub. To state or imply otherwise is misleading at best and a patent lie at worst. Please stop recommending self-hosting as a security feature. Please stop leading the lemmings off the cliff.

https://nvd.nist.gov/vuln/detail/CVE-2023-27706

Bitwarden Desktop v1.20.0 and above stores the biometric key in plaintext which allows a local attacker to decrypt the entire local vault if you are using Windows Hello and are not on the latest version. The Bitwarden Windows client before version 2023.4.0 is affected.

Details here: https://hackerone.com/reports/1874155

(shamelessly stolen from reddit)