Author: sajolida Date: To: Tails user experience & user interface design Subject: Re: [Tails-ux] Ever-growing blueprint/ directory on the website
intrigeri: > sajolida wrote (26 Feb 2015 11:44:08 GMT) :
>>> * Assuming you still want to use blueprint/* as a wiki, what kind of
>>> linkage between blueprints and binary files stored elsewhere do you
>>> need? Would blueprint -> external attachments be good enough?
>
>> We need to be able to insert those binary images into the blueprints.
>> I'm not sure ikiwiki knows how to do that for remote URLs
>
> Apparently not with the img plugin.
>
>> but in the worse case we can do that through HTML.
>
> Cool.
>
> So, problem solved apparently. Yay!
>
> Do we need to enforce this server-side, to forbid pushing large files,
> possibly with a per-file-extension limit?
Given the fact that blueprints are world writable, if we want to be
serious about that it should be enforced somehow.
> I definitely trust that mistakes will be rare, but one can *not* undo
> such mistakes, as far as the `.git' directory size is concerned, which
> is what I'm interested in right now... and I'd like to avoid having to
> rewrite the Git history again in a few years, sort of. OTOH, I can
> definitely do more interesting things than setting up Git hooks :)
