I just farted

lol

1705 here… I hate ST.

Because you’ve come to the conclusion that “retirement in the US is a scam” evidently based on a few years of data in just your portfolio. Retirement savings is built over decades.

I’d be curious about your specific positions contributing to this graph.

JFC. Just buy a target date fund. This post makes it clear that you don’t really know what your’re doing so please do yourself a favor and just pick a target date fund like this (or equivalent if Vanguard funds aren’t available to you) and don’t mess with it until retirement.

If you want to take the time to learn more about what you should probably be doing, here are some resources:

• JL Colins Stock Series
• Bogleheads investment principles

Edit: Extras, as I come across them. Candidly, most will probably come from Rob Berger’s newsletter.

• https://www.whitecoatinvestor.com/optimists-vs-pessimists-finance/

I personally don’t tinker much with the OS. I want it to stay out of the way and let me do things. In the case of Bazzite, everything I need for gaming is just there and works without me lifting a finger.

I like the safety and simplicity immutables bring.

If I’m doing something out of the ordinary, a temporary container usually suffices.

It’s really made the switch from Windows as a daily driver much easier.

Okay 2 things.

1. I haven’t heard about any security issues with Rustdesk. Can you link to what you’re referring to?
2. It’s strange to see someone concerned about security recommend RDP for remote access when it’s a terrible idea to expose it to the internet. But maybe you mean to expose a VPN and then connect to RDP via that?

Edit: I see you have some info on the Rustdesk point elsewhere in the thread. I’ll read up on that part so don’t feel like you have to repeat yourself here.

No rustdesk but recommend RDP for remoting?

I’m confused on both recommendations.

restic -> Wasabi, automated with shell script and cron. Uses an include list to tell it what paths to back up.

Script has Pushover credentials to send me backup alerts. Parses restic log to tell me how much was backed up, removed, success/failure of backup, and current repo size.

To be added: a periodic restore of a random file to have its hash compared to the current version of the file (will happen right after backup, unlikely to have changed in my workload), which will be subsequently deleted, and alert sent letting me know how the restore test went.

Ohh I see.

I could see this being a problem for me

Note: While JMP does provide phone numbers and voice/SMS features, it does not provide 911, 112, 999 or other emergency services over voice or SMS.

How do you deal with it?

First I’m hearing of it and I’m starting to question my security given I installed my OS using it.

What’s fake about the effect a FPTP voting system creates?

What was some of the difficulty you ran into?

I haven’t had to do anything weird but I don’t need anything outside of flatpaks usually.

For most other things a container with more traditional package management works well.

Bazzite worked well for me with dual monitors and a 1060. But I can’t speak for 3 monitors and a 4070.

Hm. Let’s see what I get.

And here’s another one for good measure:

It is, yes. But it’s also legal to make your own.

Bro keep up. They doin’ it again.

Wait till this crowd hears about smoke detectors.

Yeah that was fun times.

Luckily, thanks to using docker, it was easy enough to “pin” a working version in the compose file while I figured out what just broke.

For everyone’s reference, here’s my fstab to give you an idea of what works with linuxserver.io’s qbittorrent

## Media disks setup for mergerfs and snapraid

# Map cache to 1TB SSD
/dev/disk/by-id/ata-Samsung_SSD_860_EVO_1TB_S3Z8NB0K820469N-part1 /mnt/ssd1 xfs defaults 0 0

# Map storage and parity. All spinning disks.
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK39X4N-part1 /mnt/par1         xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK3TY5N-part1 /mnt/disk01       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK4806N-part1 /mnt/disk02       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD100EZAZ-11TDBA0_JEK4H0RN-part1 /mnt/disk03       xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT0TS-part1 /mnt/disk04 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT1YS-part1 /mnt/disk05 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N4XFT3EK-part1 /mnt/disk06 xfs defaults 0 0
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N6CKJJ6P-part1 /mnt/disk07 xfs defaults 0 0

# Setup mergerfs backing pool
/mnt/disk* /mnt/stor fuse.mergerfs defaults,nonempty,allow_other,use_ino,inodecalc=path-hash,cache.files=off,moveonenospc=true,dropcacheonclose=true,link_cow=true,minfreespace=1000G,category.create=pfrd,fsname=mergerfs 0 0

# Setup mgergerfs caching pool
/mnt/ssd1:/mnt/disk* /mnt/cstor fuse.mergerfs defaults,nonempty,allow_other,use_ino,inodecalc=path-hash,cache.files=partial,moveonenospc=ff,dropcacheonclose=true,minfreespace=10G,category.create=ff,fsname=cachemergerfs 0 0

I do this with mergerfs.

I then periodically use their prewritten scripts to move things off the cache and to the backing drives.

I should say it’s not really caching but effectively works to take care of this issue. Bonus since all that storage isn’t just used for cache but also long term storage. For me, that’s a better value proposition.