Looks great. Will definitely try out.

Day to day I just use LunaSea. Added convenience of being able to add a film from a phone.

Would HAVE. Could HAVE.

The original author tried to turn it into a business. Turns out that was next to impossible up against YNAB. Gave it to the community who’s keeping it current.

I’ve literally just switched to Actual (3 days in) after living out of a homemade Excel YNAB clone for years and years. Overall it’s great and the bank syncing really works (except with a weird issue around starting date and starting balance).

I love that it’s open source, E2E encrypted, self-hostable and the data lives in a SQLite database.

If I haven’t found any major snags, I’ll of course become a supporter in a couple of weeks.

Yes, it works a treat in the EU (due to PSD2, which mandates open banking) and U.K. (which is copy/pasting PSD2 to ensure their banks aren’t left behind).

I’m syncing with Handelsbanken UK, American Express, Lloyds, Monzo and Starling, all in the UK. Works a treat except most of the banks actually rate limit you to a couple of syncs per day.

I doubt it’s ever peaked at more than 3 GB usage, even with 18 containers running.

If it ran an Electron app it would need an upgrade.

Kinda similar to my self-hosted server; 24 core, 32GB - peak number of concurrent users ever hosted is 3.

You can milk anything with nipples!

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.

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.

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.