Discord is not very privacy-oriented. We‘re in a privacy-oriented community here, so Discord should raise an eyebrow, not Signal, which is famously privacy-oriented.
Deswegen habe ich die Hoffnung, dass sich Typst mittelfristig zu einer echten Alternative entwickelt. TeX merkt man seiner Alter leider an. Vieles würde man heute anders machen. Da Typst ein komplett neu entwickeltes Textsatzsystem ist, können sie alte Zöpfe abschneiden und müssen nicht den Ballast eines halben Jahrhunderts mitschleppen. Es ist beeindruckend, was das Projekt schon erreicht hat.
Ich habe Freunde, die im Einzelhandel arbeiten. Ich gönne denen sehr, dass sie wenigstens einen festen Tag in der Woche auf jeden Fall planbar und regelmäßig frei haben.
Wer es nicht schafft seine Einkäufe von Montag bis Samstag zu erledigen, hat die Kontrolle über sein Leben verloren.
If in fact being listed in credits is that important, why wasn’t it in their contract?
Maybe because of the usual power imbalance between employer and employee? If there are enough other applicants, employers can dictate the terms. It‘s a bit like saying to a coal miner: “Oh, if not dying from black lung disease is sooo important to you, why wasn‘t that in your contract?”
“I see a lot of white knighting”
I hate this term. If you call people who care about injustices “white knights”, what do you call the people who go out of their way to defend injustices and take the side of the more powerful parties?
tl;dr Duplicity does full or incremental backups, BorgBackup only does full backups but with deduplication.
After the first backup with Duplicity, you can choose to do an incremental backup which will only store the data that has changed since the last backup. This saves time and disk space but you have to do slow full backups regularly. See question 3 of the FAQ.
BorgBackup alway does a full backup. But it divides all data into chunks or blocks (don’t know what they call it exactly at the moment). It then hashes those chunks and stores them in a content-addressed storage layer. So it basically works like Git under the hood (plus encryption). If a chunk doesn’t change between backups it‘s already there and does not have to be stored again. A backup is always a full index of the data.
With today‘s fast processors and hashing algorithms, a backup with Borg should be just as fast as an incremental backup with Duplicity. If you ask me deduplicated backups are just plain superior.
Another tool that works like BorgBackup is Restic, which I prefer. Both are good choices that I would trust with my data.
Great, I accidentally deleted my original comment because the Lemmy web interface doesn’t ask for confirmation when you click the delete button. And the buttons are so small on mobile that it‘s really easy to click the wrong button.
If you want to use these features for security, access them manually. But, OP said they are kind of a noob. Telling them to just use containers is dangerous and leads to false assumptions.
You are absolutely correct. I should have stated explicitly that I didn’t mean docker and/or using pre-built container images. I was talking about something like systemd-nspawn. And you are right that I should not have brought this up in this context. I will edit my original comment.