reddit refugee

  • 1 Post
  • 85 Comments
Joined 1 year ago
Cake day: June 11th, 2023
  • capital@lemmy.worldtoSelfhosted@lemmy.world•Data HDD with SSD catch driveEnglish
    2·
    2 months ago

    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
  • capital@lemmy.worldtoPrivacy@lemmy.ml•Use a password manager
    1·
    3 months ago

    Forgot to add this bit in my first reply:

    This is especially bad since I’m more confident that GV is less susceptible to a SIM swap type of attack since I can disable it on my account which is of course protected by real 2FA (not SMS).

    Meanwhile T-Mobile has shown a few times that they’re vulnerable to SIM swap attacks.

  • capital@lemmy.worldtoPrivacy@lemmy.ml•Lastpass Family - Privacy alternative
    1·
    3 months ago

    To add to this point,

    I was using ProtonMail when I finally got serious about generating new email aliases for everything. I went as far as upgrading my plan and started setting up SimpleLogin when I ran into the fact that I couldn’t just send from arbitrary addresses using a domain THAT I OWN. I couldn’t even reply to emails to a particular alias, FROM that alias. It looks mighty sketchy to the other party when you reply from some address they didn’t know about with the contents of someone else’s email (for all they know). Trying to explain this to others was a terrible experience.

    I came across Fastmail, saw they integrated with Bitwarden via API so Bitwarden could create aliases (Fastmail calls them “masked emails”), and verified that I could both send from arbitrary addresses using my own domain and easily reply from masked addresses properly. I moved over and I’ve loved it ever since.

    As I understand it, Proton is still working on the sending feature I wanted but it’s obviously not a priority for them.

    IMO, Fastmail + Bitwarden is a much stronger feature set than Proton + SimpleLogin. Which is nuts considering Proton/SimpleLogin’s close relationship.

    If I ever want to migrate from Fastmail, it’s a DNS change…