summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawkkPNpWiR4rn0u1-Mww0sGnGGfsu51NX2U <Luke@web>2013-07-15 14:48:05 +0000
committerGravatar admin <admin@branchable.com>2013-07-15 14:48:05 +0000
commitbf333a348925867480602a27a569136f2ac9fe62 (patch)
tree9f4cbb5a138d80521517ad221e317773a0166773 /doc/todo
parent8e1e23cb02f99f33bb692ea1f6bd3ace3d5fbeea (diff)
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/support_for_lossy_remotes.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/support_for_lossy_remotes.mdwn b/doc/todo/support_for_lossy_remotes.mdwn
new file mode 100644
index 000000000..e757343f4
--- /dev/null
+++ b/doc/todo/support_for_lossy_remotes.mdwn
@@ -0,0 +1,5 @@
+I'm curious if there's a possibility to support lossy remotes. It may be handy to support syncing to special remotes that do lossy compression on the files (e.g., videos and images). For example, one could imagine having a YouTube special remote that only syncs video files. The original files wouldn't be available for download due to the transcoding and compression that YouTube does, so they wouldn't count towards the number of copies. In this YouTube example, the user gains:
+
+1. an online place that their videos are available from
+2. a worst-case scenario "backup"
+3. a remote that they could download smaller video files