https://bugzilla.wikimedia.org/show_bug.cgi?id=23133
--- Comment #6 from MZMcBride <b...@mzmcbride.com> 2010-04-17 19:16:07 UTC --- (In reply to comment #4) > * Issue One: We already have file protection, you just need to ask someone at > the project to do it, what would you prefer a solution where you can protect > files remotely from another wiki? Dynamic content, like a Main Page's "In the news" section, makes this process very error-prone. The people updating the content need to always remember to ask someone on Commons to protect the image there, or they implement bad hacks like uploading the image locally and protecting it with a bot. There should be a way to have this seamless protection of the images. The original idea here is to prevent re-uploading of Commons images if they're used on designated pages (by checking the global image links table). Though, it seems others might be suggesting variations on this idea or completely different implementations altogether. That's not as important, the end result just needs to be some form of automated protection of this content. Something that doesn't rely on bots or people, something integrated into the software. > * Issue Two: When there is a local file and remote file, the local one already > takes precedent and is displayed, so what is the issue there? Using content from Commons directly (without uploading locally) leaves a breach in the security of the content. Requiring people to constantly upload locally is a broken hackish workaround. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
