• 0 Posts
  • 96 Comments
Joined 3 年前
cake
Cake day: 2023年7月5日

help-circle

  • As a CCTV enthusiast, I do not generally recommend ubiquiti cameras unless the person wants to wholly live in the unifi ecosystem.

    They’re very pricey for what you get, even though they are pretty good. They’re most often not even near the best in class despite their price, though (looking at you, doorbell camera)

    They also don’t play nice with open/self hosted NVRs. It’s getting better due to consistent demand, but the reality is that they’re at their best when you use unifi protect, on unifi devices. So IMO it’s all or nothing, and since there’s a lot better value in other brands, I choose not to use them anymore.

    They’re pretty user friendly, though











  • He didn’t sanitize names, addresses, or active locations of the individuals involved in the work he was exposing. He made each of them a direct target.

    Most people who are critical of him from an educated place instead of one based on feels do so because of that. That wasn’t necessary to get his point across, it was sloppy and reckless, and completely unnecessary. People who call him a terrorist usually are the ones who believe there’s no way you could be so reckless and instead attribute it to malicious ulterior motives of trying to get people killed.


  • It’s super easy to configure over a LAN.

    You set up a folder path to sync, authorize it between two machines, and set up your configuration (mirrored sync, one way, etc).

    For photos taken by my phone for example, I have two syncs set up (maybe not the best way to do it it’s just how I did it in 5 min when I started and never changed it)

    Phone has a 2 way sync set up with my photo folder with my desktop. Meaning, when I delete/modify a photo either at my phone or the desktop it deletes/modifies the photo on the other device.

    Additionally, I have a 1-way sync of my photo folder between my desktop and my server archive, so the server only pulls in new files and never deletes or modifies existing files in the archive. So if something happens to my sync folder or if I delete something on accident then I have an archive copy, important for precious memories. Every now and then I just delete the contents of the archive folder and it immediately re-syncs the existing folder of all the stuff I actually wanted to keep. Could set up a cron job but I’m too lazy.

    For Joplin I just have a folder on each device that’s JUST my Joplin notes that syncs between my devices that use Joplin. Easy as pie - as soon as I turn on my laptop or desktop it syncs up with whatever changes have happened on the other two.

    For syncthing I like to make a top level sync folder on each device and then nest many folders under that top level, each to sync distinct things depending on what device it is. You can just sync a main folder if you want but I like the granular control, and as you figure out more stuff to sync it scales much better if you start that way, and name folders consistently.

    Just be careful in the beginning and always back stuff up. It’s not TOO easy to mess up but if you did it would be unforgiving. Test it with some random stuff before you start sending anything important.






  • I had about 150 dives under my belt before I ever did my first night dive (I was not an advanced diver by any means but definitely quite comfortable in the water).

    It was a shore dive where you kicked out about 30m and then just dropped down at a buoy line, couldn’t be easier. I’d done that dive plenty of times in the day, you just follow the rope down to a concrete filled bucket, easy peasy.

    Holy shit. As I started to drop and the darkness pooled around me my breathing got REAL quick. Got down to the bottom and I recognized that I was freaking out some so I just chilled for a minute looking around and getting used to my light beam being my entire vision space.

    After about two minutes I got thrilled/excited/amazed instead of panicky, and after that it’s never been an issue, but it took a deliberate, conscious effort to stow away my lizard brain and force myself to realize that I was not in existential danger.

    I LOVE night diving, I’m a night owl anyways so it’s all the things I love about the peace and quiet of the night, AND the peace and quiet of diving. It’s bliss.

    But yeah, that first drop into the blackness… Woo. I’ll always remember it just as vividly as my first open water boat dive.


  • You mentioned immich somewhere, I think that’s a good one to set up. Don’t throw your entire life’s photo album at it at first, but it’s really good to test a variety of functions and transfer speeds.

    Oh yeah… And TAKE NOTES about your setup. Like, for each container, make notes of how you set it up and why. Trust me this is REALLY important for maintaining your stuff. If you go down a rabbit hole for two days and find a couple forum threads that lead you to how you need to modify the configs for your use case, a year from now you will have forgotten everything.

    Document, document, document.


  • If tailscale is your preferred method to access your network from outside your home it’s one of the most important parts of your setup, in terms of both security and functionality.

    Luckily, overlay VPNs like tailscale are pretty easy to set up without glaring security problems, but you definitely want to triple-check you aren’t messing things up. The thing is, you don’t know what you don’t know, so you might not realize if you make a mistake. But like I said, it’s pretty hard with those types of setups.

    To actually answer your question though, I recommend you get one or two containers working locally and then figure out how to access them from your tailnet before you dive in and set up your entire stack. Docker adds another layer of complexity when it comes to accessing things so I recommend you get it right and then deploy and test each container individually.

    Don’t set up 10 containers and then try to see if they all work, go steadily and deliberately, checking to make sure each works, and then snapshot your functional setup before you start using it heavily.

    Don’t forget to plan for backups and updates.