traches

joined 1 year ago
[–] traches 17 points 3 days ago (2 children)

Also your F-117s are rocket powered or some shit because those flames are coming from the one place that isn’t exhaust

[–] traches 4 points 4 days ago

dude I just live here

[–] traches 10 points 4 days ago (1 children)

Im so excited to finally get icc color calibration

[–] traches 2 points 4 days ago (1 children)

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

[–] traches 24 points 4 days ago (8 children)

Moved to Europe

[–] traches 8 points 1 week ago

I’m a web dev with a wife who is a researcher, and on the side I’ve built a few tools for her work. Web apps are great because cross-platform distribution and compatibility are non-issues. If you don’t need a database or server-side logic, a client-side only application is basically free to host given that it’s ultimately just a pile of static files. You can use localstorage for persistence, and because there’s no server logic you have a lot fewer security implications to worry about.

JavaScript gets a bad rap, but if you pair it with typescript and decent tooling it’s really not bad. HTML and CSS are an incredibly powerful engine for building UI, which is only getting better.

[–] traches 9 points 1 week ago (1 children)

Which is why we stopped using “gay” as a pejorative a long time ago?

[–] traches 3 points 2 weeks ago* (last edited 2 weeks 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.

[–] traches 13 points 2 weeks ago

Friend, you need therapy. There’s no shame in it, it’s just healthcare like any other. Happiness and peace aren’t as far away as you feel right now.

[–] traches 2 points 2 weeks ago

i build websites

[–] traches 18 points 3 weeks ago (1 children)

Go ask your gay friend if they can tell a difference

[–] traches 6 points 3 weeks ago (2 children)

Arrays start at 0

 

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.

 

Not sure about the artist, sorry

 
view more: next ›