I pay about £2.50 for 700+ GB storage, with about 2-10 GB of ingress every month. Storage alone is only £1.40. That’s using OVH’s “Cloud Archive” product; they also have a product called Cold Storage which is a smidge cheaper but doesn’t offer updating of existing data, so according to my projections based on the class of data I am archiving it wouldn’t be cheaper in the long term.

I know - it’s unreal how much people confuse Swiss banking privacy with Swiss privacy laws in general. FADP is weaker than GDPR IMHO.

I just have a smaller dataset using the same settings, which I try to recover a couple of times/year.

It’s not perfect as recovery exercises go … but it feels safe enough for me.

I’ve used backblaze for years and regularly run recovery exercises. Never had a problem.

However, to avoid any fears, I store remote backups in two locations (the other one being OVH, a large French cloud provider).

My data retention regime:

• Mirrored disks in local NAS.
• Continually (every night) copy to Backblaze(US) and OVH (DE).
• Once/year, copy all local NAS data to offline disks (ie disks that are plugged into a tray only during the copy) to avoid a file locking/encryption infection that could spread to the online files.

No: https://www.sqlite.org/fileformat.html

Yeah, I agree that might work if the marketing team isn’t that connected to the product. I’ve not worked with a marketing team where that would work, but maybe it will for some. It doesn’t change the “massive customer will only renew if” scenario, though.

The challenge is, in a real org of some size, you’ll suddenly get marketing or customer success asking you for commitments that are very far out, because ad slots have to be booked or a very large customer renewal is coming up.

And some of the normal coping mechanism (beta-branch that spins off stable feature to the general release branch) don’t work for all those requests.

Try as you might, you are going to get far off deadlines that you have to work towards. Not for everything but for more than you’d like.

Yes completely agree. The cool thing about opencollective is the transparency - that should mean the core devs should be happy to pay themselves some money for their time. This is how projects sustain themselves IMHO.

Dunno about affordable but you can usually find some decently priced 1L Dell Optiplex micro systems. I’ve got one running under my desk 24/7. Great Linux support.

Harmonies is pretty and very very inviting for non-gamers.

Small World always stood out to me as a game with lots of style and identity.

Glory to Rome, in the crazy, all-in reprint they did still to me is an absolute highlight of art and theme. So pretty.

Are there people who can’t smell a coffee wee? You’re blowing my mind.

Same as asparagus wee. Man, when anyone has eaten asparagus I can smell it before I enter the door to the bathroom. When I have eaten it myself, I’m partly horrified and partly morbidly fascinated. What the fuck is up with only some people being able to smell it.

Wikipedia says the death cap tastes quite pleasing, reportedly.

Well, different floats for different boats I suppose.

I do think Zig is better for this kind of thing.

const ret = try do_thing();

if( ret ) | result | {
   do_something_with_result(result);
}

The try keyword returns any error up; the if-unwrap works with what came out of a successful call. Normally you wouldn’t have both, of course.

do_thing would be defined as a union of an error (a distinct kind of type, so it can be reasoned about with try, catch and unwrapping) and the wrapped return value.

I’ve already paid for a lifetime license of Plex. Is it worth considering a switch?

If you fund, you influence.

Scale. Look at a programming language like Zig … tiny, but managing to have three people full time.

• My self-hosted docker server is called Ark.
• My NAS is called NAS.
• The two remote servers are simply called the name of the country they reside in.
• The OPNsense router is called, wait for it, Router.
• The TV client is called TV.

It’s not very colourful :)

Yes I’m aware, of course. But then you take on another set of trade-offs. It’s not like shallow cloning SOLVES your problem.