• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle





  • What worked for me at my old school was using a ShadowSocks proxy. Basically what this does, is it takes all your traffic and just makes it look like random https traffic (AFAIK). ShadowSocks is just a proxy. The description fits the Cloak module, mentioned below.

    I believe multiple VPNs support this, for me with PIA VPN it’s in the settings under the name “Multi-Hop” (PIA only supports this on the Desktop App, not on mobile).

    This technique is pretty much impossible to block, unless you ban every single VPN ShadowSocks Proxy IP. If that is the case for you (chances are practically 0), you could also selfhost ShadowSocks in combination with the Cloak module, however this method is a lot more complicated.









  • TVHeadend is the way, I’ve been running it with a USB satellite tuner for 5+ years. Setting it up can be a little confusing, but once it’s running you pretty much never have to touch it again.

    As for clients, there’s a Jellyfin plugin, however it seems to not work for me right now.

    My client of choice is Kodi with the TVHeadend plugin, and that works great. If you still want Jellyfin integration, you could just add your recordings folder as a library in Jellyfin.


  • Could I purchase two different brand drives and use them with btrfs?

    I don’t quite remember the source for this, but I believe I read some time ago that it’s actually a good thing to have separate drives. The reasoning is, if you buy two identical drives (at the same time), the likelyhood of both drives failing around the same time is severely higher.

    This is then amplified by the fact that rebuilding a RAID puts a lot of strain on the non-dead drive, so if ie. drive 1 dies and drive 2 is about to die, the strain you put on drive 2 in order to rebuild your RAID onto drive 3 might kill drive 2 before you even finish rebuilding your RAID.

    Again, this is just from my memory, it might be worth doing some more research on.





  • As the article states, currently all processes are able to read the file which contains the key. Instead, you could store the key in the macOS Keychain (and Linux/Windows equivalents), which AFAIK is a list of all sorts of sensitive data (think WiFi passwords etc.), encrypted with your user password. I believe the Keychain also only let’s certain processes see certain entries, so the Signal Desktop App could see only its own encryption key, whereas for example iMessage would only see the iMessage encryption key.