git.lirion.de

Of git, get, and gud

summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.md b/README.md
index e3b97c6..f16c691 100644
--- a/README.md
+++ b/README.md
@@ -10,11 +10,11 @@ updater.phar is useless.
delivered a 255MiB file in over 15 minutes to a machine with download speeds of 30+MiB/sec)
so the backup may already be dated when we proceed.
We are just using `curl`, and we are backupping afterwards.
-3. It then does stuff with nextcloud in an undocumented [^1] manner. Given that some utterly stupid
- morons decided that within Nextcloud (nice software by itself) everything needs to be writable
+3. It then does stuff with nextcloud in an undocumented [^1] manner. Given that some ...
+ people decided that within Nextcloud (nice software by itself) everything needs to be writable
by the web server user (utterly insane!), we don't want to rely on such a construct too much.
- (Nextcloud don't give a fuck about security principles that are aaaaages old? Fuck your meta
- layers, then, we don't trust you anymore. Security fucked once, security fucked always.)
+ (Nextcloud don't give a fuck about security principles that are aaaaages old? Security fucked
+ once, security fucked always - we'll ignore meta layers as far as possible, then.)
4. Also, it rolls back everything on any failure - including downloads which will be fully
re-executed, every. single. time. (our curl does not re-download complete downloads.)
5. Solution? Create own scripts which take over downloads, download verification, and then