diff --git a/polls/2015/blocking_problems.mdwn b/polls/2015/blocking_problems.mdwn
index b8ff8596..e3ad5e98 100644
--- a/polls/2015/blocking_problems.mdwn
+++ b/polls/2015/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll expandable=yes open=yes 6 "too hard to install" 9 "too hard to use" 21 "not good enough documentation" 4 "because of a bug (that has been reported)" 0 "because of a bug (that's not been reported yet)" 1 "because I don't think it's ready" 30 "The only use for the assistant would be in combination with a good, native, fully automagic Android version which includes some sort of native UI" 24 "Performance with many files is somewhat meh" 13 "The lack of selective file sync (ie, git annex get and git annex drop) is what prevents me from using the Assistant" 15 "I use the command line, and find it difficult to show others how to use the git-annex assistant" 1 "new things are scary" 12 "have lost files in the past (very likely because of my own messing about) and although it's straightforward to restart from a healthy clone, i'm always a bit anxious about messing things up" 4 "preferred content settings are very wonky and make automation much harder" 2 "Tried it once for a few weeks... didn't work reliably back then (~2 years ago)" 3 "Too hard to use. But it *is* a tool for the more tech adept, so that is not a problem in my perception. Don't trade the powerfulness for average user compatibility. Fire-and-forget solutions exist like sand at the seeside." 3 "inconsistent handling of file metadata (mtime, mostly)" 2 "doesn't seem able to handle hundreds of offline archives (e.g., burnt CDs/DVDs) well" 1 "breaking with external plugins in the past (Glacier)" 1 "Handling of encrypted repositories can be difficult"]]
+[[!poll expandable=yes open=yes 6 "too hard to install" 9 "too hard to use" 22 "not good enough documentation" 4 "because of a bug (that has been reported)" 0 "because of a bug (that's not been reported yet)" 1 "because I don't think it's ready" 30 "The only use for the assistant would be in combination with a good, native, fully automagic Android version which includes some sort of native UI" 24 "Performance with many files is somewhat meh" 13 "The lack of selective file sync (ie, git annex get and git annex drop) is what prevents me from using the Assistant" 15 "I use the command line, and find it difficult to show others how to use the git-annex assistant" 1 "new things are scary" 12 "have lost files in the past (very likely because of my own messing about) and although it's straightforward to restart from a healthy clone, i'm always a bit anxious about messing things up" 4 "preferred content settings are very wonky and make automation much harder" 2 "Tried it once for a few weeks... didn't work reliably back then (~2 years ago)" 3 "Too hard to use. But it *is* a tool for the more tech adept, so that is not a problem in my perception. Don't trade the powerfulness for average user compatibility. Fire-and-forget solutions exist like sand at the seeside." 3 "inconsistent handling of file metadata (mtime, mostly)" 2 "doesn't seem able to handle hundreds of offline archives (e.g., burnt CDs/DVDs) well" 1 "breaking with external plugins in the past (Glacier)" 1 "Handling of encrypted repositories can be difficult"]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)

diff --git a/polls/2015/blocking_problems.mdwn b/polls/2015/blocking_problems.mdwn
index 61deb71b..b8ff8596 100644
--- a/polls/2015/blocking_problems.mdwn
+++ b/polls/2015/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll expandable=yes open=yes 6 "too hard to install" 9 "too hard to use" 21 "not good enough documentation" 4 "because of a bug (that has been reported)" 0 "because of a bug (that's not been reported yet)" 1 "because I don't think it's ready" 29 "The only use for the assistant would be in combination with a good, native, fully automagic Android version which includes some sort of native UI" 24 "Performance with many files is somewhat meh" 13 "The lack of selective file sync (ie, git annex get and git annex drop) is what prevents me from using the Assistant" 15 "I use the command line, and find it difficult to show others how to use the git-annex assistant" 1 "new things are scary" 12 "have lost files in the past (very likely because of my own messing about) and although it's straightforward to restart from a healthy clone, i'm always a bit anxious about messing things up" 4 "preferred content settings are very wonky and make automation much harder" 2 "Tried it once for a few weeks... didn't work reliably back then (~2 years ago)" 3 "Too hard to use. But it *is* a tool for the more tech adept, so that is not a problem in my perception. Don't trade the powerfulness for average user compatibility. Fire-and-forget solutions exist like sand at the seeside." 3 "inconsistent handling of file metadata (mtime, mostly)" 2 "doesn't seem able to handle hundreds of offline archives (e.g., burnt CDs/DVDs) well" 1 "breaking with external plugins in the past (Glacier)" 1 "Handling of encrypted repositories can be difficult"]]
+[[!poll expandable=yes open=yes 6 "too hard to install" 9 "too hard to use" 21 "not good enough documentation" 4 "because of a bug (that has been reported)" 0 "because of a bug (that's not been reported yet)" 1 "because I don't think it's ready" 30 "The only use for the assistant would be in combination with a good, native, fully automagic Android version which includes some sort of native UI" 24 "Performance with many files is somewhat meh" 13 "The lack of selective file sync (ie, git annex get and git annex drop) is what prevents me from using the Assistant" 15 "I use the command line, and find it difficult to show others how to use the git-annex assistant" 1 "new things are scary" 12 "have lost files in the past (very likely because of my own messing about) and although it's straightforward to restart from a healthy clone, i'm always a bit anxious about messing things up" 4 "preferred content settings are very wonky and make automation much harder" 2 "Tried it once for a few weeks... didn't work reliably back then (~2 years ago)" 3 "Too hard to use. But it *is* a tool for the more tech adept, so that is not a problem in my perception. Don't trade the powerfulness for average user compatibility. Fire-and-forget solutions exist like sand at the seeside." 3 "inconsistent handling of file metadata (mtime, mostly)" 2 "doesn't seem able to handle hundreds of offline archives (e.g., burnt CDs/DVDs) well" 1 "breaking with external plugins in the past (Glacier)" 1 "Handling of encrypted repositories can be difficult"]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)

diff --git a/polls/2018/graphs/happyness.png b/polls/2018/graphs/happyness.png
index fc8dcee3..f775e482 100644
Binary files a/polls/2018/graphs/happyness.png and b/polls/2018/graphs/happyness.png differ

diff --git a/polls/2018/graphs/command_line_vs_assistant.png b/polls/2018/graphs/command_line_vs_assistant.png
new file mode 100644
index 00000000..45dae80c
Binary files /dev/null and b/polls/2018/graphs/command_line_vs_assistant.png differ
diff --git a/polls/2018/graphs/field_of_science.png b/polls/2018/graphs/field_of_science.png
new file mode 100644
index 00000000..bd28918e
Binary files /dev/null and b/polls/2018/graphs/field_of_science.png differ
diff --git a/polls/2018/graphs/git_level.png b/polls/2018/graphs/git_level.png
new file mode 100644
index 00000000..a5b13c46
Binary files /dev/null and b/polls/2018/graphs/git_level.png differ
diff --git a/polls/2018/graphs/happyness.png b/polls/2018/graphs/happyness.png
new file mode 100644
index 00000000..fc8dcee3
Binary files /dev/null and b/polls/2018/graphs/happyness.png differ
diff --git a/polls/2018/graphs/how_installed.png b/polls/2018/graphs/how_installed.png
new file mode 100644
index 00000000..c29a61c4
Binary files /dev/null and b/polls/2018/graphs/how_installed.png differ
diff --git a/polls/2018/graphs/missing_ports.png b/polls/2018/graphs/missing_ports.png
new file mode 100644
index 00000000..3e0b5ad3
Binary files /dev/null and b/polls/2018/graphs/missing_ports.png differ
diff --git a/polls/2018/graphs/num_respondants.png b/polls/2018/graphs/num_respondants.png
new file mode 100644
index 00000000..d7131058
Binary files /dev/null and b/polls/2018/graphs/num_respondants.png differ
diff --git a/polls/2018/graphs/number_of_repositories.png b/polls/2018/graphs/number_of_repositories.png
new file mode 100644
index 00000000..7d70248a
Binary files /dev/null and b/polls/2018/graphs/number_of_repositories.png differ
diff --git a/polls/2018/graphs/operating_system.png b/polls/2018/graphs/operating_system.png
new file mode 100644
index 00000000..bb4a9753
Binary files /dev/null and b/polls/2018/graphs/operating_system.png differ
diff --git a/polls/2018/graphs/size_of_annex.png b/polls/2018/graphs/size_of_annex.png
new file mode 100644
index 00000000..6bec17c0
Binary files /dev/null and b/polls/2018/graphs/size_of_annex.png differ

diff --git a/polls/2018.mdwn b/polls/2018.mdwn
index 7d6ae067..09a6d2cb 100644
--- a/polls/2018.mdwn
+++ b/polls/2018.mdwn
@@ -1,6 +1,6 @@
 [[!meta title="2018 git-annex user survey"]]
 
-This survey is open now through January 31st 2019.
+This survey ran from December 1st 2018-January 31st 2019.
 
 [[!inline trail=yes show=0 pagenames="""
 polls/2018/v7_repositories
diff --git a/polls/2018/blocking_problems.mdwn b/polls/2018/blocking_problems.mdwn
index 4d02a28f..f2b440ce 100644
--- a/polls/2018/blocking_problems.mdwn
+++ b/polls/2018/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 47 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 28 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places" 1 "I use git annex mostly from linux, sometimes from mac os. On mac OS it is very slow. I'd blame mas os filesystem, and the size of my repo."]]
+[[!poll posttrail=2018 expandable=yes open=no 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 47 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 28 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places" 1 "I use git annex mostly from linux, sometimes from mac os. On mac OS it is very slow. I'd blame mas os filesystem, and the size of my repo."]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)
diff --git a/polls/2018/command_line_vs_assistant.mdwn b/polls/2018/command_line_vs_assistant.mdwn
index 6b2bf5f4..4d8b81fc 100644
--- a/polls/2018/command_line_vs_assistant.mdwn
+++ b/polls/2018/command_line_vs_assistant.mdwn
@@ -1,6 +1,6 @@
 Are you a command-line git-annex user, or do you
 use the [git-annex assistant](http://git-annex.branchable.com/assistant/)?
 
-[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 228 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
+[[!poll posttrail=2018 open=no 16 "I use mostly the git-annex assistant" 228 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/community.mdwn b/polls/2018/community.mdwn
index 1f29497b..49fd59ae 100644
--- a/polls/2018/community.mdwn
+++ b/polls/2018/community.mdwn
@@ -2,6 +2,6 @@ git-annex has a community of users, developers, and financial supporters,
 leading to a [rather long list of names on the thanks page](https://git-annex.branchable.com/thanks/).
 What's your involvement in this community?
 
-[[!poll posttrail=2018 expandable=yes open=yes 135 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
+[[!poll posttrail=2018 expandable=yes open=no 135 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/focus.mdwn b/polls/2018/focus.mdwn
index e82c1347..87b3fe72 100644
--- a/polls/2018/focus.mdwn
+++ b/polls/2018/focus.mdwn
@@ -1,6 +1,6 @@
 git-annex is now 8 years old, and has a good number of users. What general
 area do you think development should focus on now?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 47 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 37 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
+[[!poll posttrail=2018 expandable=yes open=no 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 47 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 37 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index c8c0d7f3..d8cc755f 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 17 "casual, needs advice" 52 "everyday use" 104 "can offer advice" 72 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=no 4 "novice" 17 "casual, needs advice" 52 "everyday use" 104 "can offer advice" 72 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index 1fc0f46d..8a5f5890 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 32 "not so happy" 109 "happy" 63 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=no 3 "unhappy" 32 "not so happy" 109 "happy" 63 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index 147a2fae..756b2aa8 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 17 "I build from source" 169 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=no 32 "From a prebuilt version on its website" 17 "I build from source" 169 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.
diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index 90e38e3c..51544c30 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 156 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 51 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=no 156 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 51 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index 1e70052f..2e79ecd0 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 53 "6-10" 52 "11-25" 22 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=no 8 "0" 19 "1" 87 "2-5" 53 "6-10" 52 "11-25" 22 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/operating_system.mdwn b/polls/2018/operating_system.mdwn
index 49140f40..d901b4ac 100644
--- a/polls/2018/operating_system.mdwn
+++ b/polls/2018/operating_system.mdwn
@@ -1,5 +1,5 @@
 Pick the operating system which you use git-annex on the most.
 
-[[!poll posttrail=2018 expandable=yes open=yes 223 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
+[[!poll posttrail=2018 expandable=yes open=no 223 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/roadmap.mdwn b/polls/2018/roadmap.mdwn
index 28fc0bd9..10b7a226 100644
--- a/polls/2018/roadmap.mdwn
+++ b/polls/2018/roadmap.mdwn
@@ -4,6 +4,6 @@ which item seems most important to you?
 Also feel free to write in an item from the
 [todo list](http://git-annex.branchable.com/todo/) instead.
 
-[[!poll posttrail=2018 expandable=yes open=yes 83 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 19 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 6 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
+[[!poll posttrail=2018 expandable=yes open=no 83 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 19 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 6 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index b9f5f0f0..22f68c69 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 38 "10+ GB" 78 "100+ GB" 34 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=no 20 "<1 GB" 15 "1+ GB" 38 "10+ GB" 78 "100+ GB" 34 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/using_for.mdwn b/polls/2018/using_for.mdwn
index dc6c42c5..1fedeffa 100644
--- a/polls/2018/using_for.mdwn
+++ b/polls/2018/using_for.mdwn
@@ -1,5 +1,5 @@
 What kind of data do you mostly use git-annex to store?
 
-[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 140 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 21 "Photos " 3 "music" 1 "All active work" 2 "Collected media"]]
+[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=no 140 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 21 "Photos " 3 "music" 1 "All active work" 2 "Collected media"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/using_with.mdwn b/polls/2018/using_with.mdwn
index 4ae64b2e..89fa735c 100644
--- a/polls/2018/using_with.mdwn
+++ b/polls/2018/using_with.mdwn
@@ -2,6 +2,6 @@ Do you use git-annex by yourself, or as part of a group of people
 who share a repository? (If you have multiple repositories, pick the one
 with the largest group.)
 
-[[!poll posttrail=2018 expandable=yes open=yes 147 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
+[[!poll posttrail=2018 expandable=yes open=no 147 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018/v7_repositories.mdwn b/polls/2018/v7_repositories.mdwn
index 9b6d616b..2915dab9 100644
--- a/polls/2018/v7_repositories.mdwn
+++ b/polls/2018/v7_repositories.mdwn
@@ -3,6 +3,6 @@ git-annex v7 was recently released, with improved support for
 which is planned to replace the old direct mode.
 Do you use any v7 repository features yet?
 
-[[!poll posttrail=2018 open=yes 199 "not yet" 21 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
+[[!poll posttrail=2018 open=no 199 "not yet" 21 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
 
 [[!sidebar content=""]]
diff --git a/polls/2018_science.mdwn b/polls/2018_science.mdwn
index c33657f5..1403852c 100644
--- a/polls/2018_science.mdwn
+++ b/polls/2018_science.mdwn
@@ -2,9 +2,8 @@
 
 This is an appendix to the main [[2018 git-annex user survey|/polls/2018]]
 to find out more about how people are using git-annex with scientific data.
-Please also fill out the main survey.
 

(Diff truncated)

diff --git a/polls/2018/v7_repositories.mdwn b/polls/2018/v7_repositories.mdwn
index 62cf971e..9b6d616b 100644
--- a/polls/2018/v7_repositories.mdwn
+++ b/polls/2018/v7_repositories.mdwn
@@ -3,6 +3,6 @@ git-annex v7 was recently released, with improved support for
 which is planned to replace the old direct mode.
 Do you use any v7 repository features yet?
 
-[[!poll posttrail=2018 open=yes 198 "not yet" 21 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
+[[!poll posttrail=2018 open=yes 199 "not yet" 21 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_for.mdwn b/polls/2018/using_for.mdwn
index ec579cf8..dc6c42c5 100644
--- a/polls/2018/using_for.mdwn
+++ b/polls/2018/using_for.mdwn
@@ -1,5 +1,5 @@
 What kind of data do you mostly use git-annex to store?
 
-[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 140 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 21 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
+[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 140 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 21 "Photos " 3 "music" 1 "All active work" 2 "Collected media"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_with.mdwn b/polls/2018/using_with.mdwn
index efc6a169..4ae64b2e 100644
--- a/polls/2018/using_with.mdwn
+++ b/polls/2018/using_with.mdwn
@@ -2,6 +2,6 @@ Do you use git-annex by yourself, or as part of a group of people
 who share a repository? (If you have multiple repositories, pick the one
 with the largest group.)
 
-[[!poll posttrail=2018 expandable=yes open=yes 146 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
+[[!poll posttrail=2018 expandable=yes open=yes 147 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/community.mdwn b/polls/2018/community.mdwn
index 0ea9cf42..1f29497b 100644
--- a/polls/2018/community.mdwn
+++ b/polls/2018/community.mdwn
@@ -2,6 +2,6 @@ git-annex has a community of users, developers, and financial supporters,
 leading to a [rather long list of names on the thanks page](https://git-annex.branchable.com/thanks/).
 What's your involvement in this community?
 
-[[!poll posttrail=2018 expandable=yes open=yes 134 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
+[[!poll posttrail=2018 expandable=yes open=yes 135 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/roadmap.mdwn b/polls/2018/roadmap.mdwn
index 2ab4e92e..28fc0bd9 100644
--- a/polls/2018/roadmap.mdwn
+++ b/polls/2018/roadmap.mdwn
@@ -4,6 +4,6 @@ which item seems most important to you?
 Also feel free to write in an item from the
 [todo list](http://git-annex.branchable.com/todo/) instead.
 
-[[!poll posttrail=2018 expandable=yes open=yes 83 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 19 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
+[[!poll posttrail=2018 expandable=yes open=yes 83 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 19 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 6 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/focus.mdwn b/polls/2018/focus.mdwn
index 4faa2da1..e82c1347 100644
--- a/polls/2018/focus.mdwn
+++ b/polls/2018/focus.mdwn
@@ -1,6 +1,6 @@
 git-annex is now 8 years old, and has a good number of users. What general
 area do you think development should focus on now?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 37 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
+[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 47 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 37 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index 1753de4a..1fc0f46d 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 32 "not so happy" 109 "happy" 62 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 32 "not so happy" 109 "happy" 63 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index b5165eae..c8c0d7f3 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 17 "casual, needs advice" 52 "everyday use" 104 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 17 "casual, needs advice" 52 "everyday use" 104 "can offer advice" 72 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index 957ebf41..b9f5f0f0 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 38 "10+ GB" 78 "100+ GB" 33 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 38 "10+ GB" 78 "100+ GB" 34 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index 82abc60a..1e70052f 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 52 "6-10" 52 "11-25" 22 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 53 "6-10" 52 "11-25" 22 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index 2301287e..90e38e3c 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 155 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 51 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=yes 156 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 51 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index c77b0524..147a2fae 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 16 "I build from source" 169 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 17 "I build from source" 169 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.

diff --git a/polls/2018/operating_system.mdwn b/polls/2018/operating_system.mdwn
index e9b74063..49140f40 100644
--- a/polls/2018/operating_system.mdwn
+++ b/polls/2018/operating_system.mdwn
@@ -1,5 +1,5 @@
 Pick the operating system which you use git-annex on the most.
 
-[[!poll posttrail=2018 expandable=yes open=yes 222 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
+[[!poll posttrail=2018 expandable=yes open=yes 223 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/command_line_vs_assistant.mdwn b/polls/2018/command_line_vs_assistant.mdwn
index 409545c3..6b2bf5f4 100644
--- a/polls/2018/command_line_vs_assistant.mdwn
+++ b/polls/2018/command_line_vs_assistant.mdwn
@@ -1,6 +1,6 @@
 Are you a command-line git-annex user, or do you
 use the [git-annex assistant](http://git-annex.branchable.com/assistant/)?
 
-[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 227 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
+[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 228 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/v7_repositories.mdwn b/polls/2018/v7_repositories.mdwn
index 537b0b3c..62cf971e 100644
--- a/polls/2018/v7_repositories.mdwn
+++ b/polls/2018/v7_repositories.mdwn
@@ -3,6 +3,6 @@ git-annex v7 was recently released, with improved support for
 which is planned to replace the old direct mode.
 Do you use any v7 repository features yet?
 
-[[!poll posttrail=2018 open=yes 197 "not yet" 21 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
+[[!poll posttrail=2018 open=yes 198 "not yet" 21 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_for.mdwn b/polls/2018/using_for.mdwn
index 98a0dd48..ec579cf8 100644
--- a/polls/2018/using_for.mdwn
+++ b/polls/2018/using_for.mdwn
@@ -1,5 +1,5 @@
 What kind of data do you mostly use git-annex to store?
 
-[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 141 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
+[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 140 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 21 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_for.mdwn b/polls/2018/using_for.mdwn
index c6ff1c17..98a0dd48 100644
--- a/polls/2018/using_for.mdwn
+++ b/polls/2018/using_for.mdwn
@@ -1,5 +1,5 @@
 What kind of data do you mostly use git-annex to store?
 
-[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 140 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
+[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 141 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_with.mdwn b/polls/2018/using_with.mdwn
index 1490eed7..efc6a169 100644
--- a/polls/2018/using_with.mdwn
+++ b/polls/2018/using_with.mdwn
@@ -2,6 +2,6 @@ Do you use git-annex by yourself, or as part of a group of people
 who share a repository? (If you have multiple repositories, pick the one
 with the largest group.)
 
-[[!poll posttrail=2018 expandable=yes open=yes 145 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
+[[!poll posttrail=2018 expandable=yes open=yes 146 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/community.mdwn b/polls/2018/community.mdwn
index a5eda7d3..0ea9cf42 100644
--- a/polls/2018/community.mdwn
+++ b/polls/2018/community.mdwn
@@ -2,6 +2,6 @@ git-annex has a community of users, developers, and financial supporters,
 leading to a [rather long list of names on the thanks page](https://git-annex.branchable.com/thanks/).
 What's your involvement in this community?
 
-[[!poll posttrail=2018 expandable=yes open=yes 133 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
+[[!poll posttrail=2018 expandable=yes open=yes 134 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/roadmap.mdwn b/polls/2018/roadmap.mdwn
index f8614b63..2ab4e92e 100644
--- a/polls/2018/roadmap.mdwn
+++ b/polls/2018/roadmap.mdwn
@@ -4,6 +4,6 @@ which item seems most important to you?
 Also feel free to write in an item from the
 [todo list](http://git-annex.branchable.com/todo/) instead.
 
-[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 19 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
+[[!poll posttrail=2018 expandable=yes open=yes 83 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 19 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/focus.mdwn b/polls/2018/focus.mdwn
index 148e396e..4faa2da1 100644
--- a/polls/2018/focus.mdwn
+++ b/polls/2018/focus.mdwn
@@ -1,6 +1,6 @@
 git-annex is now 8 years old, and has a good number of users. What general
 area do you think development should focus on now?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 36 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
+[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 37 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/blocking_problems.mdwn b/polls/2018/blocking_problems.mdwn
index 2e389438..4d02a28f 100644
--- a/polls/2018/blocking_problems.mdwn
+++ b/polls/2018/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 47 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places" 1 "I use git annex mostly from linux, sometimes from mac os. On mac OS it is very slow. I'd blame mas os filesystem, and the size of my repo."]]
+[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 47 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 28 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places" 1 "I use git annex mostly from linux, sometimes from mac os. On mac OS it is very slow. I'd blame mas os filesystem, and the size of my repo."]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)

diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index 72d2a1eb..1753de4a 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 32 "not so happy" 109 "happy" 61 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 32 "not so happy" 109 "happy" 62 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index 18527d3c..b5165eae 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 104 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 17 "casual, needs advice" 52 "everyday use" 104 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index 7c6e2139..957ebf41 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 38 "10+ GB" 78 "100+ GB" 32 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 38 "10+ GB" 78 "100+ GB" 33 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index 79a1016c..82abc60a 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 51 "6-10" 52 "11-25" 22 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 52 "6-10" 52 "11-25" 22 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index c1b215bb..2301287e 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 154 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 51 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=yes 155 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 51 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index 3f934a74..c77b0524 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 169 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 16 "I build from source" 169 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.

diff --git a/polls/2018/operating_system.mdwn b/polls/2018/operating_system.mdwn
index a90c85a4..e9b74063 100644
--- a/polls/2018/operating_system.mdwn
+++ b/polls/2018/operating_system.mdwn
@@ -1,5 +1,5 @@
 Pick the operating system which you use git-annex on the most.
 
-[[!poll posttrail=2018 expandable=yes open=yes 221 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
+[[!poll posttrail=2018 expandable=yes open=yes 222 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/command_line_vs_assistant.mdwn b/polls/2018/command_line_vs_assistant.mdwn
index 3fb783aa..409545c3 100644
--- a/polls/2018/command_line_vs_assistant.mdwn
+++ b/polls/2018/command_line_vs_assistant.mdwn
@@ -1,6 +1,6 @@
 Are you a command-line git-annex user, or do you
 use the [git-annex assistant](http://git-annex.branchable.com/assistant/)?
 
-[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 226 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
+[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 227 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/v7_repositories.mdwn b/polls/2018/v7_repositories.mdwn
index dc98b35e..537b0b3c 100644
--- a/polls/2018/v7_repositories.mdwn
+++ b/polls/2018/v7_repositories.mdwn
@@ -3,6 +3,6 @@ git-annex v7 was recently released, with improved support for
 which is planned to replace the old direct mode.
 Do you use any v7 repository features yet?
 
-[[!poll posttrail=2018 open=yes 197 "not yet" 20 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
+[[!poll posttrail=2018 open=yes 197 "not yet" 21 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index 12a89c6c..72d2a1eb 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 109 "happy" 61 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 32 "not so happy" 109 "happy" 61 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index 89b63952..18527d3c 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 103 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 104 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index e7d41665..7c6e2139 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 32 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 38 "10+ GB" 78 "100+ GB" 32 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index 5225803b..79a1016c 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 51 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 51 "6-10" 52 "11-25" 22 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index 6b539878..c1b215bb 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 154 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=yes 154 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 51 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index 2cf8e9f8..3f934a74 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 168 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 169 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.

diff --git a/polls/2018/operating_system.mdwn b/polls/2018/operating_system.mdwn
index 75ff5f09..a90c85a4 100644
--- a/polls/2018/operating_system.mdwn
+++ b/polls/2018/operating_system.mdwn
@@ -1,5 +1,5 @@
 Pick the operating system which you use git-annex on the most.
 
-[[!poll posttrail=2018 expandable=yes open=yes 220 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
+[[!poll posttrail=2018 expandable=yes open=yes 221 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/command_line_vs_assistant.mdwn b/polls/2018/command_line_vs_assistant.mdwn
index 69834b4d..3fb783aa 100644
--- a/polls/2018/command_line_vs_assistant.mdwn
+++ b/polls/2018/command_line_vs_assistant.mdwn
@@ -1,6 +1,6 @@
 Are you a command-line git-annex user, or do you
 use the [git-annex assistant](http://git-annex.branchable.com/assistant/)?
 
-[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 225 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
+[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 226 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_for.mdwn b/polls/2018/using_for.mdwn
index 2d3d3b3e..c6ff1c17 100644
--- a/polls/2018/using_for.mdwn
+++ b/polls/2018/using_for.mdwn
@@ -1,5 +1,5 @@
 What kind of data do you mostly use git-annex to store?
 
-[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 139 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
+[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 140 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_with.mdwn b/polls/2018/using_with.mdwn
index 09257f76..1490eed7 100644
--- a/polls/2018/using_with.mdwn
+++ b/polls/2018/using_with.mdwn
@@ -2,6 +2,6 @@ Do you use git-annex by yourself, or as part of a group of people
 who share a repository? (If you have multiple repositories, pick the one
 with the largest group.)
 
-[[!poll posttrail=2018 expandable=yes open=yes 144 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
+[[!poll posttrail=2018 expandable=yes open=yes 145 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/community.mdwn b/polls/2018/community.mdwn
index 03898464..a5eda7d3 100644
--- a/polls/2018/community.mdwn
+++ b/polls/2018/community.mdwn
@@ -2,6 +2,6 @@ git-annex has a community of users, developers, and financial supporters,
 leading to a [rather long list of names on the thanks page](https://git-annex.branchable.com/thanks/).
 What's your involvement in this community?
 
-[[!poll posttrail=2018 expandable=yes open=yes 132 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
+[[!poll posttrail=2018 expandable=yes open=yes 133 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/roadmap.mdwn b/polls/2018/roadmap.mdwn
index ed3a3fe6..f8614b63 100644
--- a/polls/2018/roadmap.mdwn
+++ b/polls/2018/roadmap.mdwn
@@ -4,6 +4,6 @@ which item seems most important to you?
 Also feel free to write in an item from the
 [todo list](http://git-annex.branchable.com/todo/) instead.
 
-[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 18 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
+[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 19 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/focus.mdwn b/polls/2018/focus.mdwn
index 2ee18918..148e396e 100644
--- a/polls/2018/focus.mdwn
+++ b/polls/2018/focus.mdwn
@@ -1,6 +1,6 @@
 git-annex is now 8 years old, and has a good number of users. What general
 area do you think development should focus on now?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 35 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
+[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 36 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/blocking_problems.mdwn b/polls/2018/blocking_problems.mdwn
index edd42864..2e389438 100644
--- a/polls/2018/blocking_problems.mdwn
+++ b/polls/2018/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 46 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places" 1 "I use git annex mostly from linux, sometimes from mac os. On mac OS it is very slow. I'd blame mas os filesystem, and the size of my repo."]]
+[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 47 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places" 1 "I use git annex mostly from linux, sometimes from mac os. On mac OS it is very slow. I'd blame mas os filesystem, and the size of my repo."]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)

diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index c94475cf..12a89c6c 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 109 "happy" 60 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 109 "happy" 61 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index ae931d36..89b63952 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 102 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 103 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index 44ad1289..e7d41665 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 31 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 32 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index 3e80d2f8..5225803b 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 50 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 51 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index 1a1d09fe..6b539878 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 153 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=yes 154 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index 20693def..2cf8e9f8 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 167 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 168 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.

diff --git a/polls/2018/operating_system.mdwn b/polls/2018/operating_system.mdwn
index 03358b64..75ff5f09 100644
--- a/polls/2018/operating_system.mdwn
+++ b/polls/2018/operating_system.mdwn
@@ -1,5 +1,5 @@
 Pick the operating system which you use git-annex on the most.
 
-[[!poll posttrail=2018 expandable=yes open=yes 219 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
+[[!poll posttrail=2018 expandable=yes open=yes 220 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/command_line_vs_assistant.mdwn b/polls/2018/command_line_vs_assistant.mdwn
index e1285b7a..69834b4d 100644
--- a/polls/2018/command_line_vs_assistant.mdwn
+++ b/polls/2018/command_line_vs_assistant.mdwn
@@ -1,6 +1,6 @@
 Are you a command-line git-annex user, or do you
 use the [git-annex assistant](http://git-annex.branchable.com/assistant/)?
 
-[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 224 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
+[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 225 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/v7_repositories.mdwn b/polls/2018/v7_repositories.mdwn
index ce111034..dc98b35e 100644
--- a/polls/2018/v7_repositories.mdwn
+++ b/polls/2018/v7_repositories.mdwn
@@ -3,6 +3,6 @@ git-annex v7 was recently released, with improved support for
 which is planned to replace the old direct mode.
 Do you use any v7 repository features yet?
 
-[[!poll posttrail=2018 open=yes 196 "not yet" 20 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
+[[!poll posttrail=2018 open=yes 197 "not yet" 20 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/blocking_problems.mdwn b/polls/2018/blocking_problems.mdwn
index 6fe8514d..edd42864 100644
--- a/polls/2018/blocking_problems.mdwn
+++ b/polls/2018/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 46 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places"]]
+[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 46 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places" 1 "I use git annex mostly from linux, sometimes from mac os. On mac OS it is very slow. I'd blame mas os filesystem, and the size of my repo."]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)

diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index af75ccb4..c94475cf 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 108 "happy" 60 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 109 "happy" 60 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index ae11b468..ae931d36 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 101 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 102 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index 11fb5528..44ad1289 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 31 "1+ TB" 20 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 31 "1+ TB" 21 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index f40cf916..3e80d2f8 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 49 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 50 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index c07d290e..1a1d09fe 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 152 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=yes 153 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index c1f51a77..20693def 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 166 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 167 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.

diff --git a/polls/2018/operating_system.mdwn b/polls/2018/operating_system.mdwn
index 6a3799b1..03358b64 100644
--- a/polls/2018/operating_system.mdwn
+++ b/polls/2018/operating_system.mdwn
@@ -1,5 +1,5 @@
 Pick the operating system which you use git-annex on the most.
 
-[[!poll posttrail=2018 expandable=yes open=yes 218 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
+[[!poll posttrail=2018 expandable=yes open=yes 219 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/command_line_vs_assistant.mdwn b/polls/2018/command_line_vs_assistant.mdwn
index 41bc9136..e1285b7a 100644
--- a/polls/2018/command_line_vs_assistant.mdwn
+++ b/polls/2018/command_line_vs_assistant.mdwn
@@ -1,6 +1,6 @@
 Are you a command-line git-annex user, or do you
 use the [git-annex assistant](http://git-annex.branchable.com/assistant/)?
 
-[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 223 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
+[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 224 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/v7_repositories.mdwn b/polls/2018/v7_repositories.mdwn
index e26db37e..ce111034 100644
--- a/polls/2018/v7_repositories.mdwn
+++ b/polls/2018/v7_repositories.mdwn
@@ -3,6 +3,6 @@ git-annex v7 was recently released, with improved support for
 which is planned to replace the old direct mode.
 Do you use any v7 repository features yet?
 
-[[!poll posttrail=2018 open=yes 195 "not yet" 20 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
+[[!poll posttrail=2018 open=yes 196 "not yet" 20 "v7 unlocked files" 4 "adjusted unlocked branches" 19 "I'm still using direct mode" 20 "I don't know"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/roadmap.mdwn b/polls/2018/roadmap.mdwn
index 2dc273fb..ed3a3fe6 100644
--- a/polls/2018/roadmap.mdwn
+++ b/polls/2018/roadmap.mdwn
@@ -4,6 +4,6 @@ which item seems most important to you?
 Also feel free to write in an item from the
 [todo list](http://git-annex.branchable.com/todo/) instead.
 
-[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 17 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
+[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 18 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_for.mdwn b/polls/2018/using_for.mdwn
index feede604..2d3d3b3e 100644
--- a/polls/2018/using_for.mdwn
+++ b/polls/2018/using_for.mdwn
@@ -1,5 +1,5 @@
 What kind of data do you mostly use git-annex to store?
 
-[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 138 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
+[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 139 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_with.mdwn b/polls/2018/using_with.mdwn
index 676c125d..09257f76 100644
--- a/polls/2018/using_with.mdwn
+++ b/polls/2018/using_with.mdwn
@@ -2,6 +2,6 @@ Do you use git-annex by yourself, or as part of a group of people
 who share a repository? (If you have multiple repositories, pick the one
 with the largest group.)
 
-[[!poll posttrail=2018 expandable=yes open=yes 143 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
+[[!poll posttrail=2018 expandable=yes open=yes 144 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/community.mdwn b/polls/2018/community.mdwn
index 0376151d..03898464 100644
--- a/polls/2018/community.mdwn
+++ b/polls/2018/community.mdwn
@@ -2,6 +2,6 @@ git-annex has a community of users, developers, and financial supporters,
 leading to a [rather long list of names on the thanks page](https://git-annex.branchable.com/thanks/).
 What's your involvement in this community?
 
-[[!poll posttrail=2018 expandable=yes open=yes 131 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
+[[!poll posttrail=2018 expandable=yes open=yes 132 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/roadmap.mdwn b/polls/2018/roadmap.mdwn
index 89012a03..2dc273fb 100644
--- a/polls/2018/roadmap.mdwn
+++ b/polls/2018/roadmap.mdwn
@@ -4,6 +4,6 @@ which item seems most important to you?
 Also feel free to write in an item from the
 [todo list](http://git-annex.branchable.com/todo/) instead.
 
-[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 17 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 1 "Speed up transfer of many small files."]]
+[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 17 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 2 "Speed up transfer of many small files."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/focus.mdwn b/polls/2018/focus.mdwn
index b178442b..2ee18918 100644
--- a/polls/2018/focus.mdwn
+++ b/polls/2018/focus.mdwn
@@ -1,6 +1,6 @@
 git-annex is now 8 years old, and has a good number of users. What general
 area do you think development should focus on now?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 34 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
+[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 35 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/blocking_problems.mdwn b/polls/2018/blocking_problems.mdwn
index e6bdb7aa..6fe8514d 100644
--- a/polls/2018/blocking_problems.mdwn
+++ b/polls/2018/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 46 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day."]]
+[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 46 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day." 1 "needs an easy way to visualize the locations and status of files, so at a glance I can know if all my files are healthy and in the right places"]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)

diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index 07a57da3..af75ccb4 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 108 "happy" 59 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 108 "happy" 60 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index ba5a0f5e..ae11b468 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 101 "can offer advice" 70 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 101 "can offer advice" 71 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index 903f7022..11fb5528 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 30 "1+ TB" 20 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 31 "1+ TB" 20 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index 7e8429fe..f40cf916 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 48 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 49 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index 57a8fd6f..c07d290e 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 151 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=yes 152 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index 7a123d01..c1f51a77 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "From a prebuilt version on its website" 15 "I build from source" 166 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=yes 32 "From a prebuilt version on its website" 15 "I build from source" 166 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.

diff --git a/polls/2018/operating_system.mdwn b/polls/2018/operating_system.mdwn
index 1361c1de..6a3799b1 100644
--- a/polls/2018/operating_system.mdwn
+++ b/polls/2018/operating_system.mdwn
@@ -1,5 +1,5 @@
 Pick the operating system which you use git-annex on the most.
 
-[[!poll posttrail=2018 expandable=yes open=yes 217 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
+[[!poll posttrail=2018 expandable=yes open=yes 218 "Linux" 26 "OSX" 0 "Android (app)" 1 "Android (termux)" 1 "other Unix" 9 "Windows (native)" 3 "Widows Subsystem for Linux (WSL)" 1 "OpenBSD"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/command_line_vs_assistant.mdwn b/polls/2018/command_line_vs_assistant.mdwn
index 0e18a8d9..41bc9136 100644
--- a/polls/2018/command_line_vs_assistant.mdwn
+++ b/polls/2018/command_line_vs_assistant.mdwn
@@ -1,6 +1,6 @@
 Are you a command-line git-annex user, or do you
 use the [git-annex assistant](http://git-annex.branchable.com/assistant/)?
 
-[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 222 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
+[[!poll posttrail=2018 open=yes 16 "I use mostly the git-annex assistant" 223 "I use mostly git-annex at the command line" 12 "I use both equally often" 10 "I do not yet use git-annex"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018_science/datalad_rerun.mdwn b/polls/2018_science/datalad_rerun.mdwn
index 150ab2fc..fb0d47ff 100644
--- a/polls/2018_science/datalad_rerun.mdwn
+++ b/polls/2018_science/datalad_rerun.mdwn
@@ -1,5 +1,5 @@
 If you use Datalad, is `datalad run/rerun` part of your workflow?
 
-[[!poll posttrail=2018_science expandable=yes open=yes 7 "yes, I use datalad run/rerun" 10 "no, but I have heard about it" 10 "no" 65 "I don't use datalad"]]
+[[!poll posttrail=2018_science expandable=yes open=yes 7 "yes, I use datalad run/rerun" 10 "no, but I have heard about it" 10 "no" 66 "I don't use datalad"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018_science/related_software.mdwn b/polls/2018_science/related_software.mdwn
index 462432ea..b84cd2bb 100644
--- a/polls/2018_science/related_software.mdwn
+++ b/polls/2018_science/related_software.mdwn
@@ -1,6 +1,6 @@
 Do you use software layered on top of git-annex for generating,
 discovering, managing, publishing data sets etc?
 
-[[!poll posttrail=2018_science expandable=yes open=yes 75 "just git-annex" 12 "Datalad (http://datalad.org)" 1 "DataLad-HIRNI (https://pypi.org/project/datalad-hirni)" 0 "GIN (https://web.gin.g-node.org)" 1 "ReproIn/HeuDiConv (http://reproin.repronim.org)" 8 "our own custom software"]]
+[[!poll posttrail=2018_science expandable=yes open=yes 76 "just git-annex" 12 "Datalad (http://datalad.org)" 1 "DataLad-HIRNI (https://pypi.org/project/datalad-hirni)" 0 "GIN (https://web.gin.g-node.org)" 1 "ReproIn/HeuDiConv (http://reproin.repronim.org)" 8 "our own custom software"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018_science/consumer_or_producer.mdwn b/polls/2018_science/consumer_or_producer.mdwn
index b3709cd0..742e59f1 100644
--- a/polls/2018_science/consumer_or_producer.mdwn
+++ b/polls/2018_science/consumer_or_producer.mdwn
@@ -1,7 +1,7 @@
 Do you use git-annex more for getting access to data from others,
 or for producing/publishing your own data?
 
-[[!poll posttrail=2018_science expandable=yes open=yes 13 "consuming data from others" 57 "producing/publishing data" 14 "both equally" 6 "moving data around"]]
+[[!poll posttrail=2018_science expandable=yes open=yes 13 "consuming data from others" 58 "producing/publishing data" 14 "both equally" 6 "moving data around"]]
 
 [[!sidebar content="Thanks for voting! Remember to continue to the rest of
 the questions in this poll, using the link at the top right of the page!"]]

diff --git a/polls/2018_science/field_of_science.mdwn b/polls/2018_science/field_of_science.mdwn
index 8bd1a658..17aee526 100644
--- a/polls/2018_science/field_of_science.mdwn
+++ b/polls/2018_science/field_of_science.mdwn
@@ -5,6 +5,6 @@ participating in the poll.
 
 What field of science do you use git-annex for?
 
-[[!poll posttrail=2018_science expandable=yes open=yes  8 "astronomy" 4 "bioinformatics" 0 "biology" 2 "chemistry" 32 "computer science" 0 "geography" 4 "machine learning/AI" 0 "meteorology" 19 "neuroscience" 5 "physics" 1 "statistics" 1 "social sciences" 2 "mathematics" 2 "education" 2 "linguistics" 2 "biomedical engineering" 2 "EE" 1 "physiology" 12 "None of the above"]]
+[[!poll posttrail=2018_science expandable=yes open=yes  8 "astronomy" 4 "bioinformatics" 0 "biology" 2 "chemistry" 32 "computer science" 0 "geography" 4 "machine learning/AI" 0 "meteorology" 19 "neuroscience" 5 "physics" 1 "statistics" 1 "social sciences" 2 "mathematics" 2 "education" 2 "linguistics" 2 "biomedical engineering" 2 "EE" 1 "physiology" 13 "None of the above"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_for.mdwn b/polls/2018/using_for.mdwn
index 60259a05..feede604 100644
--- a/polls/2018/using_for.mdwn
+++ b/polls/2018/using_for.mdwn
@@ -1,5 +1,5 @@
 What kind of data do you mostly use git-annex to store?
 
-[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 138 "personal data" 5 "business data" 25 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
+[[!poll postlink=/polls/2018_science/field_of_science expandable=yes open=yes 138 "personal data" 5 "business data" 26 "scientific data" 1 "game development assets" 0 "rather not say" 5 "cultural archive data" 2 "backups" 6 "podcasts" 18 "video" 20 "Photos " 3 "music" 1 "All active work" 1 "Collected media"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/using_with.mdwn b/polls/2018/using_with.mdwn
index 06437462..676c125d 100644
--- a/polls/2018/using_with.mdwn
+++ b/polls/2018/using_with.mdwn
@@ -2,6 +2,6 @@ Do you use git-annex by yourself, or as part of a group of people
 who share a repository? (If you have multiple repositories, pick the one
 with the largest group.)
 
-[[!poll posttrail=2018 expandable=yes open=yes 143 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 8 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
+[[!poll posttrail=2018 expandable=yes open=yes 143 "by myself" 43 "by myself so far but I hope to get others using my repository" 20 "1 other person" 3 "2 others" 9 "3-5 others" 4 "6-10 others" 1 "11-25 others" 0 "26-50 others" 1 "50+ others"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/community.mdwn b/polls/2018/community.mdwn
index 711c3639..0376151d 100644
--- a/polls/2018/community.mdwn
+++ b/polls/2018/community.mdwn
@@ -2,6 +2,6 @@ git-annex has a community of users, developers, and financial supporters,
 leading to a [rather long list of names on the thanks page](https://git-annex.branchable.com/thanks/).
 What's your involvement in this community?
 
-[[!poll posttrail=2018 expandable=yes open=yes 130 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
+[[!poll posttrail=2018 expandable=yes open=yes 131 "none, I just use git-annex" 63 "my name is on the thanks page!" 9 "I rely on the community for tech support and/or file bugs" 16 "Helping other users, filing bugs, pushing git-annex to breaking point" 5 "I try to give feedback where possible" 2 "If I've worked out how to do something with git-annex I sometimes do a write-up in a blog post or similar" 1 "patreon supporter"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/roadmap.mdwn b/polls/2018/roadmap.mdwn
index bb64b350..89012a03 100644
--- a/polls/2018/roadmap.mdwn
+++ b/polls/2018/roadmap.mdwn
@@ -4,6 +4,6 @@ which item seems most important to you?
 Also feel free to write in an item from the
 [todo list](http://git-annex.branchable.com/todo/) instead.
 
-[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 17 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 4 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 1 "Speed up transfer of many small files."]]
+[[!poll posttrail=2018 expandable=yes open=yes 82 "speed improvements" 4 "improve tree export" 10 "importing trees from special remotes" 6 "improve adjust --hide-missing interface" 31 "improve Windows support" 2 "more/collection of special remotes" 17 "deltas" 5 "Improve assistant on macos" 26 "I'm good without any of those" 29 "sharing files outside of git-annex easily" 3 "sync over tor" 5 " LFS API support" 1 "git-annex-assistant improvements" 2 "Improve installation. What about static linked compiled binaries for a few archs like I get with Go binaries?" 1 "git repo tracking (not storage)" 2 "Lower-case extension for SHA256E and similar. Also, simple way to make sure no big file is ever committed in regular git storage. This is simply too costly to recover from when each copy of a repo is a multi terabyte hard disks with a million+ of files, some in the 10-100kB range, some in the 10-40MB range." 1 "Speed up transfer of many small files."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/focus.mdwn b/polls/2018/focus.mdwn
index 65c48979..b178442b 100644
--- a/polls/2018/focus.mdwn
+++ b/polls/2018/focus.mdwn
@@ -1,6 +1,6 @@
 git-annex is now 8 years old, and has a good number of users. What general
 area do you think development should focus on now?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 45 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 34 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
+[[!poll posttrail=2018 expandable=yes open=yes 31 "just general maintenance, keep it working and fix bugs" 75 "make it easier for nontechnical users" 46 "make it more suitable for collaboration inside larger groups/organizations (ie, game developers, scientists, archivists)" 1 "port it to more platforms" 34 "performance" 10 "reliability" 9 "improve the existing ports" 12 "improve documentation" 3 "get more of the functionality merged into vanilla git, to have at least rudimentary interactions with git-only users" 6 "reliability features (e.g. being able to query when a file was last fsck'd on any device, consistent hashing to shard across devices)" 4 "features that widen applicability to data storage problems that are not currently well-served (think outside the box, eg. system backups, media galleries, large file sharing via email)" 2 "The documentation on configuration was not easy for me to use.  I had to jump around lots of man pages to figure out how to specify  a config option and where to place it." 1 "metadata fast cache to make it usable on mid-large repos"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/blocking_problems.mdwn b/polls/2018/blocking_problems.mdwn
index fc9cb7f7..e6bdb7aa 100644
--- a/polls/2018/blocking_problems.mdwn
+++ b/polls/2018/blocking_problems.mdwn
@@ -5,7 +5,7 @@ If you're currently using git-annex, you can instead answer on behalf of
 less technically adept friends or family, and identify a problem blocking
 them from using the git-annex assistant.
 
-[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 34 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 46 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day."]]
+[[!poll posttrail=2018 expandable=yes open=yes 6 "too hard to install" 35 "too hard to use" 8 "not good enough documentation" 3 "because of a bug (that has been reported)" 3 "because of a bug (that's not been reported yet)" 3 "because I don't think it's ready" 24 "don't trust the assistant" 21 "either git-annex gets  confused often, or I do, so my use of it has started to stagnate" 46 "not issues personally, but people don't see (or realize they need) the immense benefits it provides :)" 27 "git-annex has many power features and good documentation of these features, but lacks many tutorials (like the walkthrough) showing new users how to tie the features together" 10 "without v7 there is a bit too much friction for non-technical user's file syncing needs.  once v7 hits Debian stable etc. that will change.  exciting times are ahead." 15 "git alone is hard to grasp for a novice, with git-annex symlinks, locked/unlocked states, now adjusted branches -- it goes way too far to even grasp concepts. So hard to advice to naive users who did not yet get fascinated by git itself" 1 "do not work well over smb" 4 "git is not quite right as a data model, so there's lots of minor to serious friction when using git-annex to share data between different users or even just different contexts that want different views of the same data" 1 "problem with filenames across OSes (e.g., colons work with Linux but not under Windows)" 1 "difficult to use with Files/Nautilus (copy or drag&drop actually copies the symlink)" 1 "Integration with operating system not convenient enough." 1 "My opinion could maybe be covered by Integration with operating system not convenient enough. (0%), not sure, but I'd thought that I would explain.  First, I am a daily user of git, but the interactions and relationship between git and git-annex are not always clear to me, like for example renaming files (ther's no git-annex mv).  Not sure if there's another way to do it, but I end up doing git mv; and similar for git-annex add and not having data commited until git-annex sync or manual commit.  So I always feel as if it's not a complete tool and has to rely on git for some functionality, or that the user has to be aware of underlying concepts including git, which is much a bigger deal than software for storage and archives.  The other big issue for me, perhaps unavoidable, is that symlinks are not exactly files, so this is covered by the Files/Nautilus answer, but also that one has to add -L for operations like du -shc *, or that the files don't get colored as media files with ls because again they are symlinks, not proper files.  So it's tantalisingly close to be a normal directory with extra features like checksumming, archival and sharing between devices, but not in all aspects.  As I said not sure if avoidable, so overall I prefer very much to use this software and have these features even with the glitches compared to usual files, thanks a lot!" 1 "Was unable to install it on OpenBSD" 1 "Lack of Github support (not your fault, of course)" 1 "Not apt for subsetting a big repo into a small storage device with crippled filesystem, which is what a dumb devices (say, MP3 player) would require and what I would consider a pretty common use scenario. For such a device, files would need to be unlocked, but that doubles the size of the repo, since annex.thin is not supported on such filesystems." 2 "v7 is just way too slow sometimes. updating a (unchanged, or maybe one file changed) repo takes hours for a repo containing tens of thousands of files :/" 1 "I love the idea of git annex, but finding it hard to get confidence that I can get myself out of trouble.  git makes it easy to get back to an earlier state, but I don't yet feel confident about that with git annex, despite it being just git -- the complexity and quirkiness make this harder.  e.g. the issue with not being able to undo git add before first committing.  More get out of trouble docs covering various situations might help.  For example, for me right now, knowing some maybe hacky but performant v7-supported way to remove all the git data and just leave file content and structure behind (seems uninit and unannex don't yet tick the performant box) would help give me confidence to start using it seriously.  Then I'd know I can just create a new annex when I get myself in serious trouble, until I understand things better." 1 "loss of files' mtime info (for some reason year and month fields are preserved in metadata, but the rest is thrown away)" 0 "The major change from v5 to v7 adds a lot of confusion. Even though the issues are discussed fairly well in docs, novice users simply cannot navigate the docs effectively because of the persistence of relics of indirect/direct, locked/unlocked. It'" 1 "Terribly confusing for novice/beginning git users who rely on docs to  figure things out, but cannot escape the presence of historical relics from v5 (direct, indirect, locked, unlocked). One is likely to pore over these difficult concepts for some time, then realize they're deprecated, then begin using in earnest, and only THEN realize that all repos default to v5 and that upgrading is not such a straightforward thing. I am still fighting this battle. Persisting because the product is just what i need at the end of the day."]]
 
 (Note that [[missing_ports]] covers ports to IOS etc, so don't add them
 here.)

diff --git a/polls/2018/happyness.mdwn b/polls/2018/happyness.mdwn
index b911b295..07a57da3 100644
--- a/polls/2018/happyness.mdwn
+++ b/polls/2018/happyness.mdwn
@@ -1,5 +1,5 @@
 Overall, how happy are you with git annex?
 
-[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 30 "not so happy" 108 "happy" 59 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
+[[!poll posttrail=2018 expandable=yes open=yes 3 "unhappy" 31 "not so happy" 108 "happy" 59 "very happy" 5 "completely ecstatic" 41 "one of my favorite applications of all time" 1 "Don't know, I just use NeuroDebian and PyMPVA"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/git_level.mdwn b/polls/2018/git_level.mdwn
index 02331bbf..ba5a0f5e 100644
--- a/polls/2018/git_level.mdwn
+++ b/polls/2018/git_level.mdwn
@@ -1,6 +1,6 @@
 How would you characterize your general git knowledge?
 (Not your git-annex knowledge!)
 
-[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 101 "can offer advice" 69 "know it very well" 7 "wrote some of it"]]
+[[!poll posttrail=2018 expandable=yes open=yes 4 "novice" 16 "casual, needs advice" 52 "everyday use" 101 "can offer advice" 70 "know it very well" 7 "wrote some of it"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/size_of_annex.mdwn b/polls/2018/size_of_annex.mdwn
index 63e8f646..903f7022 100644
--- a/polls/2018/size_of_annex.mdwn
+++ b/polls/2018/size_of_annex.mdwn
@@ -7,6 +7,6 @@ and look for the line that says
 If you've got multiple repositories that each contain different files
 (not git clones), you can run it in each and add them up.
 
-[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 77 "100+ GB" 30 "1+ TB" 20 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
+[[!poll posttrail=2018 expandable=yes open=yes 20 "<1 GB" 15 "1+ GB" 37 "10+ GB" 78 "100+ GB" 30 "1+ TB" 20 "2+ TB" 17 "4+ TB" 14 "8+ TB" 8 "16+ TB" 4 "32+ TB" 2 "64+ TB" 0 "128+ TB" 0 "256+ TB" 1 "rather not say" 1 "I have too much data for git-annex to handle :)" 1 "Maggie here, I don't know this answer."]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/number_of_repositories.mdwn b/polls/2018/number_of_repositories.mdwn
index a7dfdc65..7e8429fe 100644
--- a/polls/2018/number_of_repositories.mdwn
+++ b/polls/2018/number_of_repositories.mdwn
@@ -1,6 +1,6 @@
 How many git-annex repositories do you have? If you have a bunch of clones
 of the same repository on different devices, count them all up or estimate.
 
-[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 47 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
+[[!poll posttrail=2018 expandable=yes open=yes 8 "0" 19 "1" 87 "2-5" 48 "6-10" 52 "11-25" 21 "26-50" 5 "51-100" 5 "101-200" 0 "201-300" 3 "more!"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/missing_ports.mdwn b/polls/2018/missing_ports.mdwn
index 53e8f6c7..57a8fd6f 100644
--- a/polls/2018/missing_ports.mdwn
+++ b/polls/2018/missing_ports.mdwn
@@ -6,6 +6,6 @@ If there's a device on which you cannot use git-annex today, because the
 port to an OS is missing or incomplete, please pick it. Please don't vote
 for an OS where you already successfully use git-annex.
 
-[[!poll posttrail=2018 expandable=yes open=yes 150 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
+[[!poll posttrail=2018 expandable=yes open=yes 151 "I'm good -- git-annex runs on my OSes of choice!" 22 "Windows" 50 "Android" 10 "Apple iOS" 3 "an ARM board not powerful enough to compile stuff on it. cross compiling haskell is a pain. So i rewrote the parts that i needed in another language (and i won't mention which one, i should be ashamed of this)." 2 "SmartOS" 6 "Synology NAS (app store package)" 4 "OpenBSD" 1 "MacOS - assistant is still flakey" 1 "MacOS - no tor integration"]]
 
 [[!sidebar content=""]]

diff --git a/polls/2018/how_installed.mdwn b/polls/2018/how_installed.mdwn
index 2ab5a6f8..7a123d01 100644
--- a/polls/2018/how_installed.mdwn
+++ b/polls/2018/how_installed.mdwn
@@ -1,6 +1,6 @@
 How do you get git-annex installed?
 
-[[!poll posttrail=2018 expandable=yes open=yes 31 "From a prebuilt version on its website" 15 "I build from source" 166 "I install the version provided by my OS distributor" 28 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
+[[!poll posttrail=2018 expandable=yes open=yes 31 "From a prebuilt version on its website" 15 "I build from source" 166 "I install the version provided by my OS distributor" 29 "From a package manager not part of my OS (eg Nix, Homebrew)" 2 "I don't know; it was installed for me" 9 "Sometimes OS package manager, sometimes source" 3 "neurodebian repo"]]
 
 If you install it using different methods at different times, pick the
 method you use most frequently.