This week's donation went to a software developer named Colin Percival who also goes by "cperciva". He contributes to GhostBSD, FreeBSD, and Tarsnap among others.
github.com/cperciva
www.daemonology.net
#ghostbsd #freebsd #github #foss #tarsnap
cperciva - Overview
new blog post: Reduce The Size Of Your Tarsnap Backups With This One Weird Trick (the trick is “pay attention to the size of your backups”) https://lucaswerkmeister.de/posts/2024/12/10/tarsnap-backup-size/
Here’s a small but useful shell function to analyze the size of tarsnap backups according to your current --exclude config without the overhead of creating and extracting the backups: https://github.com/lucaswerkmeister/home/blob/master/.bashrc.d/ncdu-tarsnap
@xerxespersrex nodds in agreement...
At least most source available products like #Tarsnap are honest that they are not #OpenSource!
@shoppingtonz @indigo I mean, #FakeFLOSS is a problem...
After creating an account, almost a decade ago and depositing $5 of credit, I've finally started making use of Tarsnap - "Online backups for the truly paranoid".
Most of my stuff is either ephemeral, or simple enough to rebuild, but a few new things recently made me realise they would be a right pain in the backside to have to recreate so it's time I started getting things backed up properly.
Setup one machine this morning and got my first backup in place. I'll wait until tomorrow to make sure the overnight cron job also works and of course make sure I can recover the backups before I start celebrating.
Now, where did I put that @mwl book?
@kasiandra ja, das ist allenfalls "#SourceAvailable", kein #OpenSourxe (vgl. #Tarsnap)...
@alterelefant @HauntedOwlbear nodds in agreement
That being said I do acknowledge the convenience that solutions like #Tarsnap deliver and I think @cperciva deserves the revenue he makes with this convenient, fully encrypted #backup solution that makes #AmazonGlacier easy to use...
Needless to say it did inspire me to consider trying my hand on building something similar but without being locked to Amazon:
@carlwgeorge @vermaden @samurro @tara Well, that confirms you went #ReplyGuy on me in the most disingenious way possible, wasting everyones' time and patience in the process.
If you (or #RedHat / #IBM) don't want to support #OpenSource or anyone using anything they made for #RHEL without paying, then shure you can do that but then don't expect people to like you.
#CentOS was in fact a "gateway distro" and had Red Hat not axed it I would've convinced my (fmr.) boss to consider paying for an RHCSA, but alas I've invested time and effort migrating from CentOS to #UbuntuLTS and even negotiated commercial support from #Canonical instead, because they were more friendly and welcoming.
Even "Source Available" like #Tarsnap is better - espechally in #finance - because having actual #SourceCode available is a matter of #trust.
But I'm not getting paid to prevent Red Hat from continuing to shoot itself in the foot...
@GrapheneOS It doesn't change the fact that #security requires #transparency and thus full access & reproduceability from source.
To give you a good example, source-available #Tarsnap demonstrates that stuff is truly securely encrypted by enabling #SelfCustody of keys and thus show they can't decrypt anything!
"Just use A, B, C & D, E, F" is the real threat as it sugfests people a false sense if security.
Collecting any #PII IS the illicit activity NO MATTER the excuse...
Sooner or later the #Enshittification of #Signal will reach a point where you'd rethink and consider apologizing...
@GrapheneOS I think both apps are shit as *both #Telegram and @signalapp demand #PII in the form of #PhoneNumbers.
OFC Telegram is (by my personal observation) almost exclusively being used by #Scammers and other #TechIlliterate criminals.
@jo I usually recommend multiple backup strategies; one fast and convenient one, that works for the usual >99% of cases, and one that may be slow but provides additional robustness and resilience against malicious data destruction and site-wide emergencies like fire or floods. Take a look at combining your existing #tarsnap with #sanoid and #syncoid
https://github.com/jimsalterjrs/sanoid
I like Tarsnap for the simplicity, but it is _so slow_ to restore backups. I should really have a faster, alternate method. I'm kicking around zfs send/receive...
@Yuki @BrodieOnLinux As shit as RMS his, he's sadly right.
Needless to say, @cperciva will pretty much remind people that "#SourceAvailable" is NOT #OpenSource and that #Tarsnap's #SourceCode is merely made available for #security and #auditability reasons as well as enabling people to build it for their (potentially weird) machine...
http://tarsnap.com/open-source.html
@trini and anyone else interested in the discussion (it appears @mwl wrote a book about it) - do you still use #tarsnap on a regular basis? What do you have backing up there, if you don't mind me asking?
Backstory: I had an email few weeks ago notifying me of my funds running low. I had some documents backed up there and I had about $50 prepaid - that was like 8+ years ago and I totally forgot about that...
I sent additional $20 their way, but was wondering - is it sill worth it?
@nazgul I mean, "credit where credit is due"...
Remembers the video where @cperciva got interrupted at a presentation on #Tarsnap and publicly honored the $2 #BugBounty for a #typo
