git-annex/doc/tips/using_Backblaze_B2.mdwn

For using Backblaze B2 as a special remote, there are currently two
choices:

* Using [[special_remotes/rclone]]  
  (Actively maintained)
* A dedicated special remote, <https://github.com/encryptio/git-annex-remote-b2>  
  (Last updated 2016)

At this time it's not clear which is better, so if you find one works
better than the other, please comment below.
improve special remotes list In several cases, there's an old, maybe unmaintained special remote, and rclone also supports the service. I don't know which is better, so I added tips pages for these, listing both possibilies, so users can fill in the details. Added some things listed in special_remotes/rclone that were not in the cloud provider list, so users will see it supports those. But, omitted S3 and webdav, since it's probably better for users to use what's built into git-annex than going via rclone. The rclone list is out of date apparently, as rclone.org has more, so I added a note at the bottom for users to check. This commit was sponsored by Ethan Aubin. 2020-03-05 02:27:56 +00:00			`For using Backblaze B2 as a special remote, there are currently two`
			`choices:`

			`* Using [[special_remotes/rclone]]`
			`(Actively maintained)`
			`* A dedicated special remote, <https://github.com/encryptio/git-annex-remote-b2>`
			`(Last updated 2016)`

			`At this time it's not clear which is better, so if you find one works`
			`better than the other, please comment below.`