traches

joined 1 year ago
[–] [email protected] 40 points 5 days ago (3 children)

the fuck is a chegg?

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

Yeah, I tried it but that experience isn’t as good as a native app. No swipe gestures, and an extremely basic UI

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

Miniflux has served me very well for years, combined with a few different apps. Reeder on iOS, I can’t remember what I used on android but there were plenty of options

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

Tractor pulls

[–] [email protected] 5 points 3 weeks ago

H model C-130s, the ones with the 4 square blade props? The engines and props are mechanically governed. There are electronic corrections applied, but the core of the systems are purely mechanical. Still flying.

Source: former flight engineer on them.

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

iPhone 3G. I’ll never forget the day I put the internet in my pocket

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

Raised conservative christian, took a disgustingly long time to lose some of my shittier takes

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

Delete the middle.

“I pledge allegiance to liberty and justice for all”

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

dude I just live here

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

Poland. It’s pretty nice but the language is real hard to learn

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

Moved to Europe

[–] [email protected] 3 points 1 month ago* (last edited 1 month 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.

 

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 ›