Good to hear.

I’ve not released it because I hacked it up very quickly.

Let’s go back to gopher?

Read the guardian over the gopher protocol at my gopher hole:

gopher://theunixzoo.co.uk/the-guardian

People like FreeNAS.

I just installed alpine Linux. I just wanted a compact Linux with good ZFS support.

For backup i use restic to backblaze.

I moved from my old nas to my new in a similar manner.

I have a two disk mirror. Call the disks d1 and d2.

• removed d1 from the old server, put it in the new nas
• creat fresh filesystem on d1
• copied the data, over the network, from d2 to d1.
• took d2 from the old server and added it to a mirror with d1 in the new server. Let it resilver.

It worked, but I was damn sure to have a backup.

Also note, the ugreen nas software is garbage. Install your own os.

Me too.

You made me question my sanity. Clocks change in 3 weeks in the uk!

I dont understand why people aren’t sandboxing these things.

Another question: is how many charge / discharge cycles are possible?

Usually the faster you charge a cell, the fewer times you can do so.

Could they please make cheap ram?

Yeah, and meanwhile visa are doing god knows how many million transactions per second.

I dont think its that big, but bitcoin is also very slow, which wont help.

I’ve been using Linux and Unix for about 25 years and I’ve never had a malware problem.

I’m not saying they dont exist (they do), but malware for those systems seems much rarer.

Can’t wait to hear how much a “lower cost” macbook costs. I bet it’s still pricey.

Headphone jack crew, unite!

I’d be surprised if you find cheaper, but if you do, please report back.

Fwiw, BB have been super reliable for me over that past few years I’ve used them.

There’s a plan where you pay some tiny amount per gb. Thats the one to use.

I use restic to backup immich (and everything else) to b3.

Be sure to stop the docker container while you backup to avoid skew.

Backblaze saved my ass at the end of last year when I had a hardware failure.

It’s not ideal.

Depending on the kind of warning, you may be able to re-write the code in question including a ‘todo!()’ to capture the “i need to think about this” case.

This way you get a crash at runtime. This is preferable to continuing execution with incorrect computation.

It’s best just to fix the warnings ASAP. They are usually trivial anyway.

You could do a dry run with rsync and see what it reports needs update.

I think you’d have to force it to use checksums instead of time stamps.