Actually, TFA isn't about svn repositories but about using working copies for your production site, and leaving .svn world-readable. svn repositories tend to at least use some kind of HTTP auth (if not https or ssh), but a world-readable .svn means your whole project is available.
Comments
tl;dr Don't accidentally leave an svn working copy available to the internet, it could be a security vulnerability.
Actually, TFA isn't about svn repositories but about using working copies for your production site, and leaving .svn world-readable. svn repositories tend to at least use some kind of HTTP auth (if not https or ssh), but a world-readable .svn means your whole project is available.
Yup, exactly. s/repositories/working copies/. I've been using git/hg too much lately.
tl;dr
http://yoursite.com/index.php
then
http://yoursite.com/.svn/text-base/index.php.svn-base
for source code!
Yes that was my thought too - at first I figured the translation was garbling what they were saying; I guess not.