traches

joined 1 year ago
[–] [email protected] 3 points 1 day ago* (last edited 1 day ago)

So there’s a storage protocol called “S3” (I wanna say it stands for simple scalable storage?), first created by Amazon for AWS. Many types of software, including backup programs, have been designed to use it as a storage backend. There are now many S3 compatible providers, last I looked the best value was backblaze B2.

You need a backup program with end-to-end encryption, S3 compatibility, and whatever other features you like. I use restic but it’s CLI only, there’s also borg backup and many others.

If you encrypt locally with a good key, you don’t have to trust the remote storage provider. They just see a bunch of meaningless noise. Just don’t lose the key or your backup is useless.

[–] [email protected] 2 points 5 days ago

i build websites

[–] [email protected] 18 points 1 week ago (1 children)

Go ask your gay friend if they can tell a difference

[–] [email protected] 37 points 2 weeks ago

I fuuuhuhuhucking hate this condescending, pestering dark pattern that apparently every single designer on the planet is required to use

[–] [email protected] 11 points 2 weeks ago (1 children)

At first glance I thought it said “extremist kinks”

[–] [email protected] 14 points 3 weeks ago (1 children)

I’ve always wanted to write a bot that replies to comments that say „I have no words” with a list of random words

[–] [email protected] 1 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

I haven’t had a chance to watch the video yet, but I will when I can, thanks for the recommendation!

From personal experience, my 2 year old Phone 14 only competes with my 6 year old a6400 in perfect light when it comes to noise and sharpness. Indoors it’s not even close.

[–] [email protected] 1 points 4 weeks ago* (last edited 4 weeks ago) (3 children)

Any decent camera with an m4/3 or better sensor and a half decent lens will blow the best smartphones out of the water. Computational photography can’t beat physics.

Edit: in good light they can get close, but the differences show up quickly in low light, if you crop, or if you look at it on anything bigger than a phone.

[–] [email protected] 1 points 4 weeks ago

Started learning web development.

[–] [email protected] 1 points 1 month ago

Totally fair, I agree it is definitely not a good first distro. I think everyone should follow the manual setup process the first time and not use archinstall, because it’s the tutorial which teaches you what’s on your system and how it works.

[–] [email protected] 1 points 1 month ago (2 children)

I’m also not new to the Linux scene, I also run a variety of distros on a variety of machines including servers and I also write software professionally. Arch is fucking great.

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago) (1 children)

I didn’t say it was stable, I specifically said it was unstable. Because it is. I said arch is reliable, which is a completely different thing.

Debian is stable because breaking changes are rare. Arch is unstable because breaking changes are common. In my personal experience, arch has been very reliable, because said breaking changes are manageable and unnecessary complexity is low.

 

I have a load-bearing raspberry pi on my network - it runs a DNS server, zigbee2mqtt, unifi controller, and a restic rest server. This raspberry pi, as is tradition, boots from a microSD card. As we all know, microSD cards suck a little bit and die pretty often; I've personally had this happen not all that long ago.

I'd like to keep a reasonably up-to-date hot spare ready, so when it does give up the ghost I can just swap them out and move on with my life. I can think of a few ways to accomplish this, but I'm not really sure what's the best:

  • The simplest is probably cron + dd, but I'm worried about filesystem corruption from imaging a running system and could this also wear out the spare card?
  • recreate partition structure, create an fstab with new UUIDs, rsync everything else. Backups are incremental and we won't get filesystem corruption, but we still aren't taking a point-in-time backup which means data files could be inconsistent with each other. (honestly unlikely with the services I'm running.)
  • Migrate to BTRFS or ZFS, send/receive snapshots. This would be annoying to set up because I'd need to switch the rpi's filesystem, but once done I think this might be the best option? We get incremental updates, point-in-time backups, and even rollback on the original card if I want it.

I'm thinking out loud a little bit here, but do y'all have any thoughts? I think I'm leaning towards ZFS or BTRFS.

view more: next ›