Change handling of relative paths in %include directives?
Right now, relative paths in %include directives are handled relative to Tor's working directory, which doesn't make a lot of sense. Handling them relative to the configuration file might make more sense?
We'd want to figure out a way to handle this that won't break existing users.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information