witten

borgmatic's "spot" check (probabilistically) protects against both of those failure modes: https://torsion.org/borgmatic/docs/how-to/deal-with-very-lar...

Sure thing! If you have any feedback on how it works (or doesn't) for you, please feel free to file a ticket.

You may also be interested in borgmatic's (beta) "spot" check, which compares your backup archive's files to your source files: https://torsion.org/borgmatic/docs/how-to/deal-with-very-lar...

I actually had the opposite reaction to it, but I do think it's nice there are tools for every use case and preference.

So is Podman, if you are to believe Red Hat's marketing on it.

With component-based solutions like Mailu, the junk/non-junk categorization you do in your mail client (via folders, not flags) indeed does inform the training of the spam filter used on incoming mail.

I can confirm that the online process for deleting an account still does not work! Gets into an endless loop sending repeated validation emails. (Firefox with all blockers disabled.)

Thanks for the shout out, Manu! I'll also plug an all-in one Borg + borgmatic Docker image (https://hub.docker.com/r/b3vis/borgmatic/) that I've used to backup to both BorgBase and rsync.net.

A bunch of this resonates with me, having spent many years in climate tech as well. I laughed at the part about selling a pilot to a utility in three months though. That's like super lightning speed in this industry.

That's the old way of doing things. And I've been there. Do I want Tomato Shibby.. or will this other weird ROM work better? Hmm, the home page isn't in English on this one. And this other fork was last released March 2011..

No more of that. Today, buy a router OpenWrt supports and just install the official images and get on with your life.

Yup, totally understood about the second subscription. The challenge is getting that first subscription though, when a particular user hasn't yet signed up for (or even heard of) the service. At that point, it's a fair amount of friction from where I'm sitting.

While this is pretty ingenious, and "solving" open source funding is a noble goal, there's a pretty practical impediment to GitRoyalty working in the real world: For new or existing projects, a big draw of open source is the on-boarding process.. You can download, install, and start playing with a library or application to see if it meets your needs with almost zero friction. And that's a big part of the selection process for any new project.

But with GitRoyalty, you can't even install the software to see if you want to use it or take a dependency on it.. without at minimum ponying up a credit card and signing up for a free trial.

My take is that this roadblock will turn away new users in sufficient numbers that it'll hurt projects with this paywall in place. Users will leave in droves for competing projects with less install friction. Not because they don't believe in paying, but because they don't know if they want to pay yet.

The projects that can afford to turn away users like this are the well-known ones with big-name maintainers, corporate sponsors, and thousands of GitHub stars. But these also happen to be the projects least in need of funding.

As difficult as it is to implement, a better place for a paywall would be after the user has installed the software, evaluated it, and decided to roll it out in production. That would bring the payment closer to the point of value, and also keep the on-boarding friction nice and low.

I can see how it seems that way (that self-publishing gets authors noticed by publishers), but it's actually pretty rare that it works out that way for any given writer. As I understand it, publishers generally don't look favorably upon a self-published author.. unless we're talking pre-published Andy Weir level numbers.

And xanthan gum, another example of this general process (perhaps without the "programming"), has been around since the 1960s: https://en.wikipedia.org/wiki/Xanthan_gum

Also check out borgmatic for configuring Borg. Works well with rsync.net: https://torsion.org/borgmatic/

Already exists for job descriptions! https://jobdescription.app

For all I know, it could exist for haircuts too.

What about the high level of oxalates in spinach, the over-consumption of which can result in kidney stones[1]?

[1] https://nutritionfacts.org/video/oxalates-in-spinach-and-kid...

That's true, although there are now a handful of BorgBackup remote storage vendors (rsync.net, BorgBase, etc.) that you can pay to run the server-side hosting for you. Probably not nearly as cheap as, say, S3.. but it does get closer to "just point your client here and hit go". And they offer additional sauce on top that you'd have to roll yourself with S3.. Backup activity monitoring, etc.

I don't know about "should", but one way to do it is to put both the backup script and the cron job to run it into a single, separate, backup-only container. Then tell that container (via volume mounts, etc.) what volumes to backup from other containers. Example container (non-Restic) that does this: https://hub.docker.com/r/b3vis/borgmatic/

You might be thinking of Borg Backup, which is written in Python: https://borgbackup.readthedocs.io/

Yeah, I haven't tried it with an existing importer, but I can't say I'm surprised. FWIW, it does work pretty well in combination with finance-dl (same author): https://github.com/jbms/finance-dl

It's a bit annoying that you have to configure it with Python code but once you set it up it's pleasant to use.

Not necessarily a good idea in every case, but if it's "just data" in the Python config file, you could make the Python config instead slurp in an actual data file of your desired format (YAML, TOML, whatever), and then transform it into Python data structures as needed.

It's also not too difficult to throw Fava and Beancount into a Docker container and host it on a web server, if that's your thing.

No. It doesn't support investment data at all.

I've actually found double-entry bookkeeping really useful for personal finances. Let's say I transfer money from one financial institution to another (say, a bank to an investment firm). With double-entry, I can track and reconcile both sides ("legs") of that transfer: one positive, and one negative. And they have to match up for things to balance.

Have you seen Beancount-import (https://github.com/jbms/beancount-import)? It provides a web interface just focusing on the import and transaction reconciling/categorization piece, and includes a decision-tree-based classifier that learns as you go.

You can disable string normalization with Black, and then continue using single quotes all day. But then, yeah, you give up enforced standardization on that.

Even if there's no way to blast all Firefox users, there are blue links to standard Mozilla-hosted "help" web pages within the Firefox add-ons config, links that a non-insignificant number of confused users will probably click. Those web pages could easily be updated with info about the cert expiry snafu.

I wonder how the boiling method (https://www.saveur.com/perfect-brown-rice-recipe) fares in regards to arsenic, given that: 1. You can use a higher water-to-rice ratio than with traditional methods, and 2. The remaining cooking water is discarded at the end.

You are correct. And yet I've found multiple cases in which they're used for code.