It doesn't have to be hard - you just need to think methodically through each of your services and assess the cost of creating/storing the backup strategy you want versus the cost (in time, effort, inconvenience, etc) if you had to rebuild it from scratch.
For me, that means my photo and video library (currently Immich) and my digital records (Paperless) are backed up using a 2N+C strategy: a copy on each of 2 NASes locally, and another copy stored in the cloud.
Ditto for backups of my important homelab data. I have some important services (like Home Assistant, Node-RED, etc) that push their configs into a personal Gitlab instance each time there's a change. So, I simply back that Gitlab instance up using the same strategy. It's mainly raw text in files and a small database of git metadata, so it all compresses really nicely.
For other services/data that I'm less attached to, I only backup the metadata.
Say, for example, I'm hosting a media library that might replace my personal use of services that rhyme with "GetDicks" and "Slime Video". I won't necessarily backup the media files themselves - that would take way more space than I'm prepared to pay for. But I do backup the databases for that service that tells me what media files I had, and even the exact name of the media files when I "found" them.
In a total loss of all local data, even though the inconvenience factor would be quite high, the cost of storing backups would far outweigh that. Using the metadata I do backup, I could theoretically just set about rebuilding the media library from there. If I were hosting something like that, that is...
The whole point of this particular comment thread here is that we’re already starting to see what’s happening: people are taking back control. You’re here on Lemmy, proving that exact point.
I never said we needed Cory to tell us what comes next. Just come up with another colourfully descriptive term like he did with enshittification.
You sound like that insufferable ponytail from Good Will Hunting.
We need Cory to coin a term for what comes after enshittification. Perhaps we can call it the Great Wipening, where we all stop paying to be treated like serfs and start taking back control of our content and data.
I needed four cables run from one room, up two storeys, across the roof, and back down into my garage, where my network cabinet is.
I reckon each cable was about 25m. I supplied half the cable (had some left on a drum), he supplied the other half, the conduit, and of course the labour. I terminated the cables myself later.
I reckon I was pretty much first in my suburb when we got it a couple of years back - I called my ISP the second it was available, and they hadn't even updated their records yet.
My experience was really good, but it probably helped that I'd already paid my sparky to run some Cat 6 to where I knew the nbn tech would want to put the NTD, so it was a straight-forward drill and connect job once the lead-in had been run.
lol - I'm the same, and frequently wonder if I'm allowing tech debt to creep in. My last update took me to 8.0.3, and that was only because I built a new node and couldn't get an older version for the architecture I wanted to run it on.
This is more about the car maker harvesting data, rather than just tracking the car. Car makers have been (quietly) building more tech into their cars to collect data for the purposes of selling it to third parties. It's effectively the enshittification of cars.
Unfortunately, any mobile data component likely to be integrated with something more integral to the car, like the entire entertainment/climate control interface, or something equally difficult/impossible to drive without.
I think OP is referring to the whole "connected cars" thing, which isn't the same as GPS. Many cars nowadays have mobile data capabilities on and are, unbeknownst to the owner, sending all sorts of information to the car makers.
This isn't just governments and government contractors collecting data for road use and tolling. It's for-profit companies harvesting consumer data for their own purpose. OP is right to be paranoid.
Nice one. This statement in particular sums it up nicely:
Jung did not see the type preferences (such as introversion and extraversion) as dualistic, but rather as tendencies: both are innate and have the potential to balance.
I remember reading elsewhere that it'd be like drawing a line down the middle of a table of people's heights, so that those who were 5 feet 10 inches and under would be the "shorts" and those 5 feet 11 inches and taller would be the "talls".
I remember buying some bits and pieces to setup my home theatre in a new house years ago, and the guy at the store tried to sell me a $100 TOSLINK cable. When I asked why a $12 cable was going for so much, he pointed out that it was the "premium" cable, to ensure the highest quality audio.
I couldn't stop laughing. Like their special cable scrubbed the photons before sending them or something.
My phone's data is encrypted. I use alphanumeric passwords. They can't compel me to give them shit, at least not anything that's only in my head. What's so hard to understand about that?
I'm not at all paranoid about your questioning. I'm just wondering why it's so important to you that I agree with your point of view.
As I said in the reply you originally replied to, I need it when I travel for work. Border Force aren't taking phones on the way out, but on the way in. And them taking my phone is not guaranteed to happen, whereas the inconvenience of me wiping my phone is.
The real question is why it matters to you so much what I do with my phone? Nice try Border Force...
It doesn't have to be hard - you just need to think methodically through each of your services and assess the cost of creating/storing the backup strategy you want versus the cost (in time, effort, inconvenience, etc) if you had to rebuild it from scratch.
For me, that means my photo and video library (currently Immich) and my digital records (Paperless) are backed up using a 2N+C strategy: a copy on each of 2 NASes locally, and another copy stored in the cloud.
Ditto for backups of my important homelab data. I have some important services (like Home Assistant, Node-RED, etc) that push their configs into a personal Gitlab instance each time there's a change. So, I simply back that Gitlab instance up using the same strategy. It's mainly raw text in files and a small database of git metadata, so it all compresses really nicely.
For other services/data that I'm less attached to, I only backup the metadata.
Say, for example, I'm hosting a media library that might replace my personal use of services that rhyme with "GetDicks" and "Slime Video". I won't necessarily backup the media files themselves - that would take way more space than I'm prepared to pay for. But I do backup the databases for that service that tells me what media files I had, and even the exact name of the media files when I "found" them.
In a total loss of all local data, even though the inconvenience factor would be quite high, the cost of storing backups would far outweigh that. Using the metadata I do backup, I could theoretically just set about rebuilding the media library from there. If I were hosting something like that, that is...