{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2023-03-05T13:32:03.863Z",
  "attributedTo":"https://social.jayvii.de/actors/jayvii",
  "inReplyTo":"https://social.jayvii.de/objects/b4r2Ghn1YUw",
  "to":["https://social.jayvii.de/actors/jayvii","https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://social.jayvii.de/actors/jayvii/followers"],
  "content":"<p>Currently dabbling with an overlay <a href=\"https://social.jayvii.de/tags/encrypted\" class=\"hashtag\" rel=\"tag\">#encrypted</a> FS + <a href=\"https://social.jayvii.de/tags/rsync\" class=\"hashtag\" rel=\"tag\">#rsync</a>, which is similar to what is described here: <a href=\"https://www.baeldung.com/linux/rsync-encrypted-remote-backups\">https://www.baeldung.com/linux/rsync-encrypted-remote-backups</a></p><p>i.e. files are encrypted in real-time through a virtual filesystem and the encrypted content is stored externally via rsync. Makes it super fast, incremental and reasonably secure. When restoring, you can sync back to the encrypted FS and it magically appears in your real FS.</p><p>The only downside (but also advantage...) is that the remotely stored content can not be viewed by itself (file- and directory names are gibberish) , i.e. you restore everything or nothing. <a href=\"https://social.jayvii.de/tags/backups\" class=\"hashtag\" rel=\"tag\">#backups</a></p><p>Edit: Another downside: Since directory names and filenames are not identifiable, rsync can also not exclude certain patterns like cachefiles, trashbin, .git-dirs, etc.</p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Hashtag","name":"#encrypted","href":"https://social.jayvii.de/tags/encrypted"},
      {"type":"Hashtag","name":"#rsync","href":"https://social.jayvii.de/tags/rsync"},
      {"type":"Hashtag","name":"#backups","href":"https://social.jayvii.de/tags/backups"}
  ],
  "type":"Note",
  "id":"https://social.jayvii.de/objects/u4Axqbuus1k"
}