

Why wouldn’t I just read using the phone I already have?


Why wouldn’t I just read using the phone I already have?
Well, TrueNAS is a RAID system, and pretty much any Linux distro can run ZFS.


I sync hundreds of gigs, (if not terabytes at this point) using Syncthing with errors on only one machine (it’s running on 6 devices, including a VM). And those errors are of my own doing, not random Syncthing errors.
It’s surprisingly robust these days, especially for a single-user notes.
I have an indexing job that runs on my server every 30 minutes, saving into a text file (it indexes my media folder, which is about 3TB of movies and TV shows).
Those text files sync to my phone when they’ve changed (so every 30 minutes). They’re always up to date when I open them.
My phone also has jobs to continually sync my photos to home, an ad-hoc folder to my laptop, and about 25 other folder pairs (including NeoBackup) that sync under different conditions, without fail.
I’m currently testing Cherrytree using Sourcherry on Android and it seems to work fine as a single-user solution with Syncthing.


I’m with you.
Granted, many people have been using it to mean “shocked”, I find that use to be problematic.


so… Don’t be a dick
That should be your first rule! 😁


Others have clarified, but I’d like to add that security isn’t one thing - it’s done in layers so each layer protects from potential failures in another layer.
This is called The Swiss Cheese Model. of risk mitigation.
If you take a bunch of random slices of Swiss cheese and stack them up, how likely is there to be a single hole that goes though every layer?
Using more layers reduces the risk of “hole alignment”.
Here’s an example model:
So a router that has no open ports, then a mesh VPN (wireguard/Tailscale) to access different services.
That VPN should have rules that only specific ports may be connected to specific hosts.
Hosts are on an isolated network (could be VLANS), with only specific ports permitted into the VLAN via the VPN (service dependent).
Each service and host should use unique names for admin/root, with complex passwords, and preferably 2FA (or in the case of SSH, certs).
Admin/root access should be limited to local devices, and if you want to get really restrictive, specific devices.
In the Enterprise it’s not unusual to have an admin password management system that you have to request an admin password for a specific system, for a specific period of time (which is delivered via a secure mechanism, sometimes in person). This is logged, and when the requested time frame expires the password is changed.
Everyone’s risk model and Swiss cheese layering will fall somewhere on this scale.


About 5 years ago I opened a port to run a test.
Within hours it was getting hammered (probably by scripts) trying to figure out what that port was forwarded to, and trying to connect.
I closed the port about a week later, but not before that poor consumer router was overwhelmed with the hits.
I closed the port after a week. For the next 2 years I’d get hammered with scans occasionally.
There are tools out there continually looking for open ports, they probably get added to a database and hackers/script kiddies, whoever, will try to get in.
Whats interesting is I did the same thing around 2000 with a DSL connection (which was very much a static address) and it wasn’t an issue even though there were fewer always-on consume connections.


Downloads! Hurray!


I like the sign, like Mother Nature is out to kill your ass, but only beyond this point. Haha


This.
Time and space are major impacts to the cost when aging.
And cheese needs to be moved when aging. Like flipped over. This is done all day, every day, at the larger places because they have so many blocks of cheese. And it loses some weight as it ages. Not as much as alcohol, but some.
It’s similar to things like alcohol. Champagne bottles must be turned every day. Whiskey in barrels loses upwards of 2% per year as it ages, so a 40 year old cask has lost eighty percent of it’s volume, while sitting in a cellar and taking up space.


I’ve never once had a government service call me. I can’t imagine a use case. And I’m carrying the upper end of the age bracket on Lemmy.
Government sends mail. Certified if it’s court.


Groan.
Fine, take your upvote


I don’t.
If you’re stupid enough to carry out my stuff, good luck getting anything for it.
My setup is a small-form-factor desktop, a NAS, and 2 other modest systems. Easy enough to carry away, but all worthless from a pawn standpoint, because it’s all old, as in long past support dates from the vendor.
I guess you’d need to understand what a burglar in your area steals, and what homes they target.
I doubt they steal systems.


Others have mentioned Syncthing as a sync solution. I’d like to add a couple points:
Syncthing can work fine even for solutions that are intended to use their own sync, provided it’s a single-user setup. You’re not likely to make simultaneous changes on 2 devices, so collisions are unlikely.
Also for using Syncthing, I recommend Syncthing-Fork for Android - it moves sync conditions into the folder/job rather than global. Very useful when you have jobs you want always syncing, and jobs you want to only sync on wifi and power.
If using iOS there’s an ST client called Möbius Sync ($5), developed by a company the financially supports Syncthing.
For Windows, get SyncTrayzor - it makes running and managing ST easier.


I carry a phone, I’m not carrying a notebook and pen.
I did that 40 years ago.
Plus that list doesn’t show up on my laptop or my desktop, other places I’m working.
It’s not sortable by date/time, priority or project.
That’s terrible advice, and doesn’t even meet the basic requirements of the question.


Lol, angry pixie hate


Americans are about 20th on a list of countries of gun deaths per year, yet have approximately 3 guns per resident.
What do the labels say?


Ooh, MFM… That tickles my little gray cells!
What am I looking at here?