Today is #WorldBackupDay - a good day to:
- start using borg backup
- upgrade to borg 1.4.4
- actually test a restore
- play with the latest borg2 beta
- contribute to borg development
- donate to the borg project
- give borgbackup a star on github
- update the borg packages, if you maintain some
- contribute to some project borg backup depends on
- contribute to some project that uses borg backup
Remote
BorgBackup
@borgbackup@fosstodon.org
mastodon 4.7.3Deduplicating archiver
with compression and encryption
0 Followers
0 Following
14 Posts
Joined July 04, 2023
Homepage:
GitHub:
Open post
Congrats to rolandrc on github - he just discovered and fixed an ancient memory leak in borgbackup's C code.
18
0
7
0
Open post
Replying to
@argv_minus_one@mastodon.sdf.org Somehow I get the feeling that you need to retry and maybe get more practice with it.
Maybe use a better model than in your last try. Maybe give it more context.
Claude >= Opus, maybe also a recent Gemini [Pro] (High). I have the paid plan (~20 EUR/m), not sure if the free plan is as good.
Maybe use Python and C code (I had quite a lot of success with that). It also worked great for html/css/js (Claude Fable + Opus).
That's just my experience, initially I was also skeptical.
2
2
0
0
Open post
Replying to
@argv_minus_one@mastodon.sdf.org To get a bit more practical / specific:
Did you notice the increased amount of bugs being fixed recently? Tons of CVEs and also lots of non-CVE fixes. Commercial SW as well as FOSS.
Quite a lot of these were discovered by AI.
A lot of these were in the code since many years and were NOT discovered by humans - neither in code review at commit time, nor in the years after that.
2
6
1
0
Open post
Replying to
April 1st is now globally over - relax!
AI won't decide about what's in your backups.
7
0
0
0
Open post
Replying to
@argv_minus_one@mastodon.sdf.org "this bad at programming" seems to be something you experienced.
My experience is quite different, so I disagree.
It's hard to see whether something was reviewed, but that is not an AI specific problem. You can also not see how much a human developer was thinking while they developed some piece of code.
A small bit of evidence (but no proof) sometimes can be seen if there is a big change (AI assisted) followed by some small changes (human corrections).
1
7
0
0
Open post
Replying to on mastodon.sdf.org
@argv_minus_one@mastodon.sdf.org https://fosstodon.org/@borgbackup/116767338328586303 that one plus some more after that.
1
10
0
0
Open post
Replying to
borg 1.4.4: if you package for big-endian architectures (most stuff is little-endian nowadays), you will need this patch:
https://github.com/borgbackup/borg/issues/9521
2
0
1
0
Open post
0
0
1
0
Open post
Replying to
@argv_minus_one@mastodon.sdf.org It's not the same task, but considering these amounts, I think some people should re-think their point of view that "human written code is good and AI written code is bad".
Obviously human written code isn't THAT good, otherwise AI would not find tons of bugs in it.
And if the developers had used AI while writing the code, maybe the bugs would not be found in production, but before release.
Years ago that was not possible, but nowadays it would be quite good for quality.
0
4
0
0