“Healthy snacks” are an edge concern - I snack on whatever the fuck I want, because that’s not the prime driver.
Every meal is the prime mover. Balance that for you, and you’ll be closer to where you want to be, and less interested in bad snacks.
When I’m eating right I’m not interested in the bad-for-me stuff nearly as much.
Yep.
I run Tailscale on every device that can run it, and have a TS router in one device at home for devices that can’t run it.
Its my fallback if Syncthing ever has a Discovery server failure.
It’s a fantastic app, but doesn’t do sync like SyncThing or Resilio Sync.
It can do things similarly if you work at configuring it, but it can never monitor a remote and sync based on file changes there. That’s not a criticism, it’s a function of the file system approach it takes - it can sync with many different file systems, but it doesn’t have a client at the other end - it simply interfaces with that file system. Fantastic actually.
I’ve used it since about 2010, it was my solution for moving files back and forth for a long time. I still use it for specific things, but I’ve put more effort into ST and Resilio Sync config and management because they’re full-on sync suites.
Instant sync only works for local folders it can monitor. Since it doesnt have a client on the other end, there’s no way to make this happen (it would have to monitor the destination).
This would require keeping a connection open between devices, which is a high cost from a network (and especially battery) perspective.
Its a great app, I’ve used it for 10+ years, paid for it 2 or 3 times because it’s worth it.
I’ve been using Fork for years. Möbius on iOS has financial support from a 3rd party that uses Syncthing in their own processes, so I suspect it will stay around.
That said, Resilio Sync is the other most-viable option I know (and use).
It’s a little less kind to battery with larger folder pairs, and uses more memory since it stores the index in RAM. But it’s robust.
Doesn’t exist, sorry.
Has to do with how RCS works. It’s a crappy “protocol” that’s bound to hardware and software like Google Messages.
Best to move on from it - it’s was born dead on the vine.
Nothng official, sorry, wish I did!
Mostly personal experience. But that experience is also shared among a group of peers and friends in the SMB space where their clients think they can keep stuff on externals in an office safe only to find they’ve gone tits up nearly every time they pull them out a couple years later. And not the enclosures, the drives themselves - they all have external drive readers for just these kinds of circumstances.
In the enterprise you’d get laughed out of a datacenter for even suggesting cold drives for anything. Of course that’s based around simple bit rot concerns, and why file systems like ZFS use a methodology to test/verify bits on a regular basis.
If nothing else, that bit rot should be enough of a reason to not store data on cold drives. It’s not what drives were designed (or tested) to do.
Edit: Everything I’ve read over the years suggests failures happen as much from things like lubricants hardening from sitting as from bit rot. I’ve experienced both. I’ve seen drives that spin up after ten years but have numerous data errors, and drives that just won’t spin up, while their counterparts that have run nearly continuously are fine (well, their bit-rot was caught by the OS and mitigated). With a running drive you have monitoring, so you know the state.
Meh, you got a spare kidney…
Fine, I write an extensive bit of help with links to QNAP docs and a few other things, and you downvote.
Fine, how about I just delete it, and ya all go figure it out without my help.
I would definitely keep them warm, as in a running machine.
Drives on a shelf die more often than always-on drives.
I don’t even know what you’re saying at this point
Big time more expensive.
Who says college is better than no college?
What are your metrics?
Your questions are all binaries:simplistic, juvenile.
Like your question about dating and race: simplistic, bigoted and racist.
Careful, not all states have a castle doctrine, and really you don’t want the legal shitshow even in a Castle Doctrine state.
Better to deter than have to deal with that.
at an unrecoverable height
Ouch!
I’ve had way more USB C ports fail than micro, surprisingly, and that’s in perhaps a 5 year period vs 15 (and continuing) usage of micro.
I know C is supposed to be more robust, that just hasn’t been my experience.
My last phone was a 2017 model, I replaced it early 2025 with a Pixel 5. I have since bought 2 more Pixels (because they’re cheap) and keep one as a hot spare (boot it once a month to update) and one as a test bed.
I would involuntarily laugh at this.
“Clearly you don’t know my family, we’re like wolves. Yes, we’ll back you up, but we’ll also pounce on the weak so they either toughen up or die. Is that really what you want?”
I use a similar Dell Optiplex 7000 series.
It boots from the NVME, with an 8TB 3.5 disc for data, and a 500GB SD for my VMs. (Since spinning disks can idle much lower than SSD, getting my always-on VMs off the big drive lets it idle, with the SSD peak power being lower than the peak of spinning disk Adding the SSD increased net power slightly).
I use a splitter on the 12v power line for both of the drives. It’s fine.
This box only has an 80w power supply, and with both those drives hooked up it draws 20w at idle, and peaks at 70w when converting multiple videos simultaneously.
The manuall tells you what you can do without voiding the warranty.
Edit: Given it’s age, I’d pull the CPU cooler and replace the paste. It’s likely hardened by now. Mine was randomly rebooting because the cpu would overheat. Replaced the thermal paste and its been rock solid since.
So do I… Because it"is accurate when I’m not eating right! Haha 😮