capital

I brought up emanations in my first reply…

I even couched it with a “might be” because I’m aware there’s lots I don’t know.

It wasn’t that you may be wrong. It was your overconfidence and hyper-fixation on one type of security.

My brother in christ, you are still missing the point.

So you pick up a message that reads “867-5309” and the receiver picks up their landline and calls.

So you have a phone number now. One that you probably already had given the organization we’re talking about. If the call is staying landline and within the boundaries of their country, you aren’t picking up shit with your SDR. You need to have a physical tap somewhere.

They swapped cell phones which send and receive for pagers that receive only. Think for 2 seconds what that means for tracking. To say nothing of also losing the fucking microphone, camera, GPS…

There’s a reason pagers are allowed into SCIFs where phones and other devices which send are not.

There’s more to security than your experience picking up unencrypted shit with an SDR.

They might be in regards to emanation.

It’s funny how confident comments like these are without really thinking it though.

Already saving lives.

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.

No, it’s an AI company now bro. Trust me.

Same. Upper middle class and work for a large hyperacaler.

Tesla was the only one excluded from my recent EV search. Loving the Polestar 2 so far.

Fuck your research.

Does each person willingly consent to being in the relationship? Yes or no. That’s the only fucking thing we need to know.

Does consent mean something different depending on skin color? The fuck?

Go far enough left or right and y’all MFs care way too much about skin color…