How can I practically verify 2TB of a life's worth of files while guaranteeing I won't have data loss due to some edge cases and race conditions that delete my data.
Every time I've created my own backup script I realized knowing what to delete and when is not easy. IMO the practical solution to this is to just pay for more storage (within reason).
How can you guarantee you'll have access to your 2TB Google Drive when they ban your Google account for breaching terms or accidentally tripping a circuit breaker across one of their offerings?
A backup is not something I fear of losing access to because by definition it’s a copy.
However I am more afraid of my data being exfiltrated and imo there is a more risk of that with a “vibe coded 1 person 1 week old” app rather than any of the major providers.
This is unironically why I do not depending on google for products this important. I do have premium google drive as I needed barely over 15gb, but my main cloud storage is dropbox. A YT comment I made 10 years ago can't break Dropbox's TOS, and since premium storage is their whole business, they will take the product more seriously.
I also have a 14TB RAID 5 NAS at home. And my Desktop PC has 6TB of RAID 5 (had that first, mostly used for video games these days).
> How can I practically verify 2TB of a life's worth of files while guaranteeing I won't have data loss due to some edge cases and race conditions that delete my data.
Same with literally every other backup software. Have two, and test restorations regularly. It's not easy, but nothing worth it when you need it ever is.
I will never use one drive even if they paid me. I use Dropbox + Homelab NAS with RAID 5 + old desktop PC with a RAID 5 drive. I have a lot of RAW photos to keep.
I'll never forget when my Grandpa died 20 years ago, the first thing my dad did - even before telling us - was look for photos. His siblings did the same and they came up with a collage of around 30 photos I had never seen before that gave me a small glimpse of the highlights of his life.
My other grandpa, controversially used a big chunk of their wedding money on a good camera. They traveled the world and lived abroad for several years right before and after my mom and aunt were born. Because of this, we are all able to see such a fascinating and meticulous glimpse into their lives. Each photo tells a story even if the story is boring, but I really appreciated the small details. Even random pictures of cars that my Grandpa thought were cool. Or the mean guard dog they had in Taiwan while it was still a puppy. Or my mom on the Trans Siberian Railroad in the middle of the Cold War.
These stories and my own appreciation of photography have made me realize how valuable every photo I have is, and I'm willing to put in effort to save them. When I'm old and dying of dementia, I'll be able to look back at my life in incredible detail one last time. Even the dumb meme's I decided to save will tell a story.
I still have a deep appreciation for living in the moment and knowing not everything should be captured, but we live in an era where I have a really good camera in my pocket at all times, and the ability to store all those photos forever cheaply.
- It's "just" JSON and WebSockets. From a developer's perspective, it's incredibly easy to get started and build interesting things with it. (Like the early days of Twitter.) Which leads to...
- Nostr culture is tolerant of bots and other automated workflows. (Unlike current management of Twitter)
- Nostr culture is tolerant of search engines. (Unlike fediverse, or at least the Mastodon part, though I appreciate the reasons for that distinction.)
- Built-in micropayment infrastructure with "zaps" and Lightning Network integration enables a ton of interesting new startup idea possibilities.
One thing I don't like about Nostr, the social network. (Not Nostr, the protocol. Those two things are very easily conflated right now):
- Too many Bitcoin bros. (Although personally I don't mind Bitcoin, a thriving platform should have more than one thing to talk about.)
looks quite interesting, I wasn't aware of that. it seems like a nice hybrid solution to pull/push problem (relays can push if they choose to, clients just publish and pull).
I should say though, that upon first look, I wish it was built on top of some already existing standard (like rss), as it could get a great headstart in terms of content already circulating in the network that way.
Nostr can get complex, but at its core, it's deceptively simple. It's built on JSON, WebSockets, digital signatures, and sending a simple Event data structure over the wire. It can get complex, but its core is very small. Feels similar to how HTTP itself started.
Also, it wouldn't be too hard too build bridges or bots that bring in other stuff (like RSS feeds or ActivityPub content) to Nostr. One already exists: https://mostr.pub
In this case 34235 client refers to `kind 34235` events. In nostr, different event types are distinguished by kind numbers, so clients can be built and filter for events of a certain type. For example, the content shown on a twitter/microblogging client, should not be the same as the content shown on a YouTube like client.
Yeah, you're probably better off getting setup with a nostr account on https://primal.net/home or Damus. You'd need a nostr extension for the extension button to work
reply