User talk:Jimbo Wales: Difference between revisions
Orangemike (talk | contribs) →Wikipedia's red links...hot or not?: the person creating the redlink sis systematically setting up rosters of articles that indisputably will pass our standards of notability |
→A kitten for you!: new WikiLove message |
||
Line 326: | Line 326: | ||
http://en.wikipedia.org/wiki/Wikipedia_talk:RefToolbar_1.0 |
http://en.wikipedia.org/wiki/Wikipedia_talk:RefToolbar_1.0 |
||
== A kitten for you! == |
|||
[[File:Kitten in a helmet.jpg|left|150px]] |
|||
Hello:) |
|||
[[User:D vsquez|D vsquez]] ([[User talk:D vsquez|talk]]) 19:12, 9 July 2012 (UTC) |
|||
<br style="clear: both"/> |
Revision as of 19:12, 9 July 2012
Welcome to my talk page. Please sign and date your entries by inserting ~~~~ at the end. Start a new talk topic. |
![]() |
(Manual archive list) |
Username penalty: IP users see articles 5x-50x faster
We need to remind users to logout to view mainstream articles 20x 30x faster. Avoid the username penalty which reformats major articles so much slower than for IP users. In running tests of template speed, I noticed that registered users (logged-in) now view articles which are formatted 5x to 50x times slower than what the IP-address users see (due to IPs seeing the common, quick, cached copies of formatted articles). Some of us were recently trying to optimize template speed, and were able to make a core template run about twice as fast, rather than having hundreds of "sub-optimized" one-line templates. In running those tests, then I noticed that hundreds of major articles can be displayed for IP users in about 1/8 second, whereas the username-specific reformatting of those articles runs several times slower, typically 20x 30x slower for mainstream articles, such as classic encyclopedia topics with formatted references. As you probably know, the complex citation templates use vast amounts of time to slow a large text article from a half-second formatting into several seconds during an edit-preview or view by a logged-in user. Of course that's fine, when people expect to hit "Show-preview" and wait several seconds for citations and navboxes to be formatted into a half-second text article. However, more users should know to log out and view the major articles 30x times faster, and edit them when needed, but after edit-preview log-in before saving the changes with an unwanted IP-address user ID. I would hate for most registered users to think that big Wikipedia articles are really displayed as excrutiatingly slow as when users are logged in. Logout and view the major articles 30x faster. Stubs display at the same quick speed either way, due to few {cite..} or navbox templates piled on those stub pages. Long term, I am wondering how to change major articles into simple large text pages that still format within one second, perhaps using dozens of quick templates. Reduce the current username penalty. -Wikid77 (talk) 17:49, 1 July, revised 00:14, 3 July 2012 (UTC)
- Assuming one is not a computer, then I don't see why this matters. I very rarely have to wait more than a second or two for an article to appear. I don't know what my reading rate is but I would say 30 words a second is a decent upper bound. So at the very worst this costs me the time to read a couple of sentences.
- This will matter for bots of course. But then they shouldn't be running off cached pages most of the time... Egg Centric 21:40, 1 July 2012 (UTC)
- Only major articles slow, not stubs or small articles: Thanks for noting the difference. The problem is typically a speed factor for only major articles, such as the top 500 articles on any mainstream topic, where the {cite} templates have been used extensively (or navboxes are large). I think a typical infobox formats within 1 second, so a large half-second text formats within 1.5 seconds with an infobox. However, the various {cite} templates use the gargantuan Template:Citation/core with over 620 parameters in the markup, so using {cite...} often adds several seconds to the formatting time, at the rate of nearly 1 second per 13 {cite} transclusions. The result is that a major article formats in over 11-12 seconds, rather than 2-3 seconds, for registered users, or for anyone during edit-preview. Because the Internet is typically very slow (with exceptions such as Google Search), then many registered users do not realize that IP users see major articles several seconds faster than they do. It is an issue that I have been trying to improve for years (working on {cite-fast} templates which run 85 per second, 6x times faster), but Jimbo has advised to avoid "all templates" which would also solve the problem, but many templates (such as infoboxes) are valuable, so we just need to optimize (and reduce) the larger templates. -Wikid77 (talk) 11:46, 2 July 2012 (UTC)
- Making major articles 3x faster for editing: Okay, the reality, obviously, is that cached copies of articles will always be, typically, over 10x faster than any optimization of reformatting. A major article that IP users view in "0.249 seconds" is likely to reformat in over 11 seconds (44x slower), and my efforts at optimization are showing reformat times no faster than 5 seconds (20x slower than the cached copy), even though twice as fast as major articles display now. I think we could get major articles to reformat 3x times faster, to allow faster edit-preview of the whole page, by having special versions of templates which are specifically fast for the basic parameters (so for rare customized parameters, use the larger massive templates). Extensive functionality seems to be the enemy of speed, because checking for use of extra features, or giving users helpful advice during use, causes extra overhead and slows the whole template, or leads to n-variety sets of similar templates which are difficult to update in similar, synchronized functionality. A possible strategy would be to have 3 types of related templates:
- Template:Hogger - the typical massive template with many features
- Template:Hog_fast - a smaller version with only the basic features
- Template:Hog_helper - a training-mode version which warns of errors.
- From the tests I have run, I am seeing that any template with many parameters will be something of a resource hog. This confirms Jimbo's advice to avoid large templates. Hence, we have the infobox templates, but they tend to slow reformatting by 1 second each, so limit their use (having 20 infoboxes in an article could slow the article by nearly 20 seconds). We can live with 1 or 2 large infoboxes per article, no problem. However, {citation} templates for 200 footnotes per article are going to eat major time, currently 1 second for every 13 footnotes, or almost 15 seconds for 200 footnotes. Instead, many people are hard-coding several footnotes, in areas, so not all "200 footnotes" use {cite} templates. The tests for the experimental {cite_fast} run faster as 70x per second, or almost 6x faster, but 200 footnote templates would still consume 3 seconds of reformat time, so again, hard-coding many footnotes (where the detailed parameters are not needed) can keep 200 footnotes below 3 seconds of formatting with a {cite_fast} template. -Wikid77 00:14, 3 July 2012 (UTC)
- I've run a couple tests myself using citation templates. I did 3 tests: one with just the urls, one with full citation templates, and one with short Harv citation templates in the "Notes" section that called the longer templates in the "References" section. The no-template was obviously the fastest. The one with 200 full citation templates was the slowest, and the one using Harvard templates was in between. It's a good option for articles that have a lot of citations to the same source. ~Adjwilley (talk) 02:16, 3 July 2012 (UTC)
- The discussion at Wikipedia talk:Featured article candidates/Citation templates (technical) is useful background reading. A fuller debate exists at Wikipedia:Centralized discussion/Citation discussion. It's demoralising to see how the actual solution (extend cite.php and move away from templates) is opposed at Demo of specific proposal for all the wrong reasons. Any technical solution that requires changing something is likely to fail because of the culture of inherent Ludditeism that exists in Wikipedia. --RexxS (talk) 07:33, 3 July 2012 (UTC)
- The vcite solution is great for now: Most users would be stunned to realize the articles will reformat or edit-preview 3x (thrice) as fast now, using Template:Vcite_book (etc.). Awesome! As for internal changes to Cite.php, I try to also consider the "worst possible scenario" of how the proposed internal PHP functions might include some hideous bugs, stuck for years, because template coders could not help to fix them. Instead, by using fast-cite templates, we can gain 80% more speed now, while also fixing any format bugs, within days, rather than months or years. Reducing a 23-second edit-preview to only a 8-second wait is a wikimiracle at this point. Beyond the cite templates, we can also optimize other issues, to gain even more speed than from citations alone. -Wikid77 15:48, revised 23:59, 3 July 2012 (UTC)
- I've run a couple tests myself using citation templates. I did 3 tests: one with just the urls, one with full citation templates, and one with short Harv citation templates in the "Notes" section that called the longer templates in the "References" section. The no-template was obviously the fastest. The one with 200 full citation templates was the slowest, and the one using Harvard templates was in between. It's a good option for articles that have a lot of citations to the same source. ~Adjwilley (talk) 02:16, 3 July 2012 (UTC)
- Possibility of caching subst'd template results: Another tactic, which could be used in rare circumstances, would be to create "segmented articles" composed with cached segments appended to the current markup text. We could take very slow portions of articles and run the templates as wp:subst'ed, then save those segments and transclude them into the final article. For example, with an article named "Mars colony":
- Mars_colony/dynamic_map - a segment with a complex (slow) map template
- Mars_colony/dynamic_map_cache - a segment with the subst'ed template(s)
- Mars_colony - then transcludes {{Mars_colony/dynamic_map_cache}}
- The rule would be that changes should be made to the template-based segments (not the cache versions), which are subst'ed into the cache-based segments, and then the cache files are appended into the article, allowing massive slow templates to be used in a huge article which reformats (around the cached segments) within seconds. -Wikid77 (talk) 17:29, 4 July 2012 (UTC)
- You know that Tim is working on Lua ("scheduled for 2013")? The aim is to replace frequently-used templates with a new and much faster system. Johnuniq (talk) 00:35, 5 July 2012 (UTC)
- Conversion to fast Lua language: Thanks for noting that option for 2013. It would be great to have the ultra-efficient Lua scripting language, with loops and recursion, even if more complicated for many users. Beware that a massive change in technology is a typical tech solution for "deus ex machina" and typically needs almost a year longer than hoped (=2014?) to "quickly save the day". There is also a danger of interface overhead, such as a "faster" system needing a "10-second" connection link (hopefully not with Lua). Often, a rewrite can duplicate unneeded complexity, and there might be a feeling to handle all "620" parameters now in Template:Citation/core. Meanwhile, I am still focusing on actions to take within a few weeks, which already show 3x speed improvements. Long term, the use of Lua might allow extremely smart, and yet fast templates, so that is another benefit beyond today's cumbersome templates. -Wikid77 06:27, 5 July 2012 (UTC)
- Working on essays about performance: I think we will need several essays about various performance issues, depending on people's level of perspective, such as explain how an article can process over 900 templates per second, but they must be (very) small templates. There are too many topics to cover in a single essay. One essay already introduces the readers to technical performance issues:
- WP:Analyzing performance issues - gives intro & links other essays.
- We need a new essay about making templates run much faster. For example, passing only a dozen parameters to a template, rather than 100, can make a template run almost twice (2x) as fast. Another option is to have gated-if structures running 3x faster, which test for perhaps 16 rare parameters to exist, before checking the value of each of those 16 parameters separately. A gated-if structure with 1 parameter can run 5 times faster. -Wikid77 (talk) 11:15, 6 July, revised 7 July 2012, 13:01, 8 July 2012 (UTC)
Forking large major articles to: (full)
I am re-thinking your advice to have smaller, more-focused articles on major topics, perhaps named as article "xx" with the current large version renamed as "xx (full)". I initially thought the Simple English Wikipedia would handle the issue enough, but now, I think we really need to have 2 versions of major articles, here, as you suggested long ago. I was looking at article "YouTube" and thought "way too big" for general readers. So perhaps:
- new "YouTube" - a smaller article, limited in size (perhaps 700 words?)
- new "YouTube (full)" - the original large article moved to a new name.
Otherwise, I really would fear wholesale deletion of extra information, such as the interesting list of other nations having YouTube versions, but all of that extensive description overwhelms the basic details of the 6 W's ("who, what, when, where, why, and how"). In many cases, the full article is almost "YouTube (rant)" because of the tedious detail, but obviously, we cannot label articles as "rant" simply because they contain 5x-9x times as much detail as most readers seek. There could be numerous cases, such as a notorious crime article, where the "(full)" version could include lists of forensic evidence to explain "whodunit" or why other suspects were freed, while allowing a smaller article to generalize the issues (but knowing the "(full)" version explains things oversimplified in the top, condensed version). Since you have already thought about this issue, and content forks are entirely valid, what other concerns should we address before making such article forks?
From a practical standpoint, I would focus on the 100 (or 1,000) most-viewed articles, and count what percentage of them need a simplified overview article. In terms of Wikipedia performance, everyone would benefit from the numerous advantages: most readers would see the nutshell version they expect; the smaller article would appear within 2 seconds; large articles could be protected from excessive trimming of details; limiting size (700 words?) would discourage POV-pushing (where currently, tangent comments are allowed in large articles because wp:NOTPAPER protects long sections); and ideally any POV-pushing in "(full)" versions would have less impact (because few people would read the massive full versions). Currently, WP is a major "advert-magnet" because people know any boosterism wedged into major articles has a good chance of being info-spammed into the "captive audience" who view the major article by name, whatever that name happens to display. Any other thoughts or advice? -Wikid77 (talk) 06:42, 7 July 2012 (UTC)
- Ideally, I think the lead sections of all articles should combine to something like the Micropædia. —Kusma (t·c) 08:56, 7 July 2012 (UTC)
- I set up an RfC at WT:Article size#RfC: Should the rule of thumb for article size refer to readable prose size or markup size? which I believe is relevant. I should be neutral about notifying about that but I think the featured article candidate editors have completely forgotton and don't care about WP:NOTPAPER and just want to produce the equivalent of printed papers on the topics. Dmcq (talk) 10:57, 7 July 2012 (UTC)
- I just had a look at the Youtube article and personally I would consider it a large article where bits should be turned into sub-articles if they grow to any size but not one where that should be a major consideration of the editors yet. Perhaps what is wanted is an easy way of just viewing the lead of an article? That perhaps could be an option which is automatically invoked in mobile profiles so they have to click on a button to get the whole article downloaded. Dmcq (talk) 11:10, 7 July 2012 (UTC)
- I've just put a proposal at WP:VPT#Section viewing about how one could deal much better with download time. I still think the FAC editors tend to push articles so they are about twice the readable size even with a good computer. Dmcq (talk) 13:24, 7 July 2012 (UTC)
- I am thinking to allow users to see the smaller overview article, first, and then choose to see the larger article, whether a featured article, or not. -Wikid77 12:53, 8 July 2012 (UTC)
Alert !
Hello Mr. Jimbo.
I want to point out to you a problem, which I have identified in the current interpretation by other editors of WP:NOR:
If someone would mix a poison "X" and some fruit juice, and call it a "D" drink, and sell it to people, there is no way that fellow editors here would allow to mention the side effects of the poison ingredient "X", in an article about "D".
Why? Because the sources about "D" will not list the side effects of "X", as they would probably be PR for "D", and the sources for "X" will not mention "D", because what do scientists, who study the side effects of a poison "X", care about the drink "D" or "Z" that "X" will be put into.
Due to that there are two problems:
- First according to the WP:NOR it is not allowed to use the scientist's source because it don't mention "D". Although, I think, that "X" is directly related to "D", as "D" contain "X", other editors' practice is to mandate explicit mentioning of "D" in the scientist article about the side effects of "X", and that is not going to happen, that is not how scientists work. They find a rule ("X" cause a side effect), they don't retest and make papers about every conceivable application of the rule, like when "X" is mixed in a "D" drink.
- The second problem, is that according to the WP:SYNTH, if one say "D" contain "X" and "X" has a side effect thus "D" has a side effect1, then it is synthesis. (From [(drinking "D") -> (drinking "X")] and [(drinking "X") ->(suffering a side effect)] it follows that [(drinking "D") ->(suffering a side effect)])1. Again, I don't think that such a simple application of logic A->B, and B->C therefor A->C should be considered a synthesis, but other editors seem to be sure that it is.
And there you go, the drink "D" is on the street, and if a kid would open Wikipedia to learn about that drink, he will not learn of the side effects of "D" at Wikipedia, and drink the drink in ignorance.
I think that this is awful, and that something should be changed, so that editors will understand that a source can be related to the topic of the article, even if it doesn't mention the topic, but does mention some relevant ingredient of the topic, and that simple logic, that any educated person can verify, is allowed.
[1] labeled comments were added at --Nenpog (talk) 06:26, 9 July 2012 (UTC)
--Nenpog (talk) 20:04, 7 July 2012 (UTC)
- Your argument is completely unpersuasive. I happen to be sitting in a restaurant where they are serving a drink that pretty well matches your description. The
dangerous chemical in question is, as measured by LD50, 36 times more deadly than pure grain alcohol. The beverage? Tea. The chemical? Caffeine. Nowhere does Wikipedia mention the lethal dose of caffeine in the article Tea.
- But as I expected, in the discussion it emerges that actually you are about to be banned for similarly illogical ranting on a completely unrelated topic.--Jimbo Wales (talk) 17:49, 9 July 2012 (UTC)
Very good and detailed explanation of the issue hidden for talk page clarity - but read if if you want to understand more |
---|
The following discussion has been closed. Please do not modify it. |
. <-- -- Avanu (talk) 20:25, 7 July 2012 (UTC)
Nenpog appears unwilling to drop the WP:STICK with this issue. IRWolfie- (talk) 15:53, 8 July 2012 (UTC)
|
Great Job Opportunity for Jimbo at Elance!
Hi Jimbo,
Apologies if you've seen this before, but this Elance ad is looking for a Wikipedia Admin or 'Crat who can publish the Wikipedia articles their clients have written "without having them deleted a few weeks later." I figure why settle for a 'Crat, when you can hire Jimbo himself?! After all, he runs this place, doesn't he?
But seriously, if "Swift11" got a quick note (or a visit - he appears to be in London) from you explaining how things work around here, it might (or might not) convince him to change his ways. Cheers, Ebikeguy (talk) 23:57, 7 July 2012 (UTC)
- The discussion on this is herePharaoh of the Wizards (talk) 01:49, 8 July 2012 (UTC)
- They've got a whole list of Wikipedia-related ads, mostly PE/PEW. benzband (talk) 08:55, 8 July 2012 (UTC)
- These pages link to Elance.
- —Wavelength (talk) 12:34, 8 July 2012 (UTC)
- Related discussion at WP:AN/I, see Wikipedia:Administrators'_noticeboard/Incidents#Paid_advocacy. Albacore (talk) 21:51, 8 July 2012 (UTC)
- If their clients don't want their articles deleted a few weeks later then JW is hardly their man. Just consider his article Mzoli's Meat. It got deleted after just 22 minutes. --Aspro (talk) 22:06, 8 July 2012 (UTC)
- And yet, Mzoli's it lives. Please don't mislead people. --Jimbo Wales (talk) 17:52, 9 July 2012 (UTC)
Wikipedia's red links...hot or not?
If you saw an editor adding hundreds of new red links (links to nowhere) in existing articles, would that be cause for concern? Would it depend on circumstances? Do you like red links or hate them? How many people see a red link and think "I must go immediately and research that topic and create a new article" versus simply saying "Eh, the good samaritan behind me on this road will take care of it" and pass it by? -- Avanu (talk) 04:23, 8 July 2012 (UTC)
- See Wikipedia:Red link.—Wavelength (talk) 04:45, 8 July 2012 (UTC)
- I have. I want to see other opinions. -- Avanu (talk) 06:16, 8 July 2012 (UTC)
Wavelength - the attitude of "See this policy document" is of no use at all. doktorb wordsdeeds 06:42, 8 July 2012 (UTC)
- Personally, I have never been a fan of redlinks unless there is a realistic chance of creating the corresponding article in the near future. Speculative redlinks are of little use.--♦IanMacM♦ (talk to me) 07:23, 8 July 2012 (UTC)
- The redlink needs to be notable - it could have an article but is just not written yet. Interestingly we have means of finding redlinks on a most-wanted-list where the number of incoming links to any non-existant article shows its relative importance and article creators pick their chores from that. Anyway suitable redlinks are great, turning them blue is the icing on the cake. Agathoclea (talk) 07:39, 8 July 2012 (UTC)
- The "is the red link notable" question goes to the core of my issue (and Avanu shares this too, hence their question!). A policy is being used as a "free pass" for notability, something I'm disputing. doktorb wordsdeeds 07:54, 8 July 2012 (UTC)
- Yes, the notability of the issue is key: redlinks should only be added of there is a chance of the article eventually being created. In this specific situation, redlinks are being added to either sitting or past MP's. MP's have been held by WP:POLITICIAN to be suitably notable for articles, and thus there is a reasonable chance that an article could be created that is suitable for Wikipedia. Doktorbuk has stated that they disagree with that notability and has therefore been removing redlinks. Wikipedia is not finished, but this discussion and the related disruption caused by continually removing said redlinks should be. (✉→BWilkins←✎) 10:34, 8 July 2012 (UTC)
- And if the name of the politician happens to be the same as that of a rapist, and the article on the rapist gets created first, what happens to the redlink in a political article, where does it suddenly link to? John lilburne (talk) 13:16, 8 July 2012 (UTC)
- There was an analogous but opposite situation in lists of gay porn performers, with no care was being taken to ensure that the name of the performer was not the same as an existing article, leading to a situation where "red links" in the lists actually ended up being blue links to existing articles. Not everyone shared my opinion that labelling someone as a porn performer was a clear violation of our policies on biographies of living persons. Delicious carbuncle (talk) 14:09, 8 July 2012 (UTC)
- And if the name of the politician happens to be the same as that of a rapist, and the article on the rapist gets created first, what happens to the redlink in a political article, where does it suddenly link to? John lilburne (talk) 13:16, 8 July 2012 (UTC)
- Yes, the notability of the issue is key: redlinks should only be added of there is a chance of the article eventually being created. In this specific situation, redlinks are being added to either sitting or past MP's. MP's have been held by WP:POLITICIAN to be suitably notable for articles, and thus there is a reasonable chance that an article could be created that is suitable for Wikipedia. Doktorbuk has stated that they disagree with that notability and has therefore been removing redlinks. Wikipedia is not finished, but this discussion and the related disruption caused by continually removing said redlinks should be. (✉→BWilkins←✎) 10:34, 8 July 2012 (UTC)
While I agree that speculative red links should not be used, I disagree with this bit of advice from Wikipedia:Red link: "However, rather than using red links in lists, disambiguation pages or templates as an article creation guide, editors are encouraged to write the article first, and instead use WikiProjects or user spaces to keep track of unwritten articles." I don't know of any good reason for that. I think using red links in lists, disambiguation pages, etc. are a good way to organize work and motivate other contributors.
The BLP issue outlined above is really a separate issue which will not apply in most cases of red links. But it is of course a valid issue. If a red link seems likely to cause a BLP violation if the corresponding article is created ambiguously, then I can see a strong case for avoiding it. But that's a small percentage of overall links.--Jimbo Wales (talk) 13:49, 8 July 2012 (UTC)
- You'd be surprised how often it does occur. Whilst those two are historic figures I have no doubt that it will occur with living figures too. John lilburne (talk) 14:33, 8 July 2012 (UTC)
- It's not necessarily a BLP issue, of course. One answer to John lilburne's question is, after all, "The same as happened at User:Skysmith/Missing topics about Mechanics when it was discovered that one of the few bluelinks in that list is an article on sexual bondage.". ☺
The question at hand, that you may not have seen the whole of, isn't a BLP issue. It's actually a biographies of very dead people issue; a biographies of very dead politicians issue, more specifically. See the Village Pump discussion for what the question that you've been asked here actually relates to.
- The redlinks that the Doktor is complaining about are about members of the English Parliament from the 1300s, where the person creating the redlinks is systematically setting up rosters of articles that indisputably will pass our standards of notability. Doktorb just seems to find the presence of lots of redlinks aesthetically offensive. --Orange Mike | Talk 19:07, 9 July 2012 (UTC)
Commons flouting copyright law?
I've just been told that my sweat-of-the-brow copyright under UK law is, by policy, ignored, and the restoration work is to be recategorised into the public domain. (Wikipedia:Featured_picture_candidates/First_colored_senator_and_reps.jpg#First_colored_senator_and_representatives and http://lists.wikimedia.org/pipermail/commons-l/2012-July/thread.html#start )
As I was only asking for a CC-by license - the absolute minimum - and only then because I was tired of seeing unscrupulous print sellers selling things for £100 when people could download it and print it themselves, I'm horrified by this behaviour.
I mean, seriously, Wikimedia has a policy of forcibly removing a requirement that their content creators be credited, and all because it's possible that the European court might rule the UK sweat-of-the-brow doctrine invalid at some point in the future. Wikipedia is not a crystal ball.
A restoration takes between about 8 and 50 hours to do right, and I have generally offered this up freely. However, at the moment, I've restricted access to my full-size restorations until and if this is sorted out to some sort of reasonably satisfactory conclusion.
Honestly, I wouldn't even have minded so much if this wasn't basically a violation of meta:Don't be a dick. I was offering my works to everyone to use freely, but people decided to attack me for doing so? Seriously?
Thank you,
Adam Cuerden. — Preceding unsigned comment added by 86.139.213.143 (talk) 15:52, 8 July 2012 (UTC)
- See Sweat of the brow. This is accepted in the UK but rejected in the US and really I don't think you can expect much by it on an American based encyclopaedia when doing American senators! Personally I support sweat of the brow as a limited copyright. However I think copyright should have a much shorter term the same as patents and only trademarks should have long term protection whilst in use. I'd include Mickey Mouse or a writers characters as trademarks so others couldn't write new stories using them. Dmcq (talk) 16:07, 8 July 2012 (UTC)
- The work should have an additional notice about copyright outside the US in particular the EU. No way the public domain in the US bit can be taken out though. Dmcq (talk) 16:18, 8 July 2012 (UTC)
- Think you misunderstand the 1988 copyright Act. The sweat-of-the-brow has not been upheld in any UK court of law -ever. It is like suggesting that an accident car repair shop, which though the sweat-of-their-brows, restore a wreak to its original appearance and so can thus claim to have a copyright over that particular individual vehicle. A UK statute might state something but if the legal system finds it unworkable and too daft to uphold -then it is moot. In the description section and on the image's exif file ,if you wish, you can state that your are the restorer. Even, link to your web page or email. Just as long as its not seen as blatant advertising. Suggest: Upload the original un-restored image first and then your restored image after and the two will show up in the File History section, thus demonstrating your skill at using GIMP, Photoshop or whatever.--Aspro (talk) 16:41, 8 July 2012 (UTC)
- When did the law ever find anything too daft? ;-) The requirements are easily low enough to allow copyright on that work in the UK. And even the case mentioned in that article about football listings is still under consideration as far as I know, it may be copyright or they might just put it under a database rights law - something the US also doesn't recognize. Dmcq (talk) 17:22, 8 July 2012 (UTC)
- In the UK one can sometimes buy a castle or Manor which gives one the legal right of Droit du seigneur but if you can't enforces it, then that legal privilege is not worth a dime (or even groat). Copyright law endeavours grant a privilege to the original creator of the creative work and a legal remedy against anyone that transgress, not to those that do technical manipulations and reproductions. To do otherwise, would be to miss-attribute copyright – again something that is covered in the 1988 Act. So what the OP wants is probably illegal anyway, if one is so intent on following the letter of the law.--Aspro (talk) 18:03, 8 July 2012 (UTC)
- When did the law ever find anything too daft? ;-) The requirements are easily low enough to allow copyright on that work in the UK. And even the case mentioned in that article about football listings is still under consideration as far as I know, it may be copyright or they might just put it under a database rights law - something the US also doesn't recognize. Dmcq (talk) 17:22, 8 July 2012 (UTC)
http://commons.wikimedia.org/wiki/Commons:When_to_use_the_PD-scan_tag says you have to give me credit. 86.139.213.143 (talk) 17:00, 8 July 2012 (UTC)
- Totally with you there, Adam. You should get a credit for the restoration. Formerip (talk) 18:15, 8 July 2012 (UTC)
- Credit is not the issue, I've already mentioned above, how credit can be indicated on these images. What the OP is claiming a CC-BY copyright over an original work, that is in the PD, something which the 1988 Act cannot confer.--Aspro (talk) 18:52, 8 July 2012 (UTC)
- What I'm saying is that the OP should have a credit which, at the moment, he doesn't. Formerip (talk) 18:58, 8 July 2012 (UTC)
- Seems to me that he is claiming copyright on the parts of the restoration that have involved elements of creativity on his part. The image is still PD you can make as many copies of the extant image as you want. All fine. All the restorer is saying is that he has copyright on the restoration work and wants to CC-BY credit on that. John lilburne (talk) 19:07, 8 July 2012 (UTC)
- But there is no evidence or legal precedent that that is true, simple faithful restoration of an image doesn't confer copyright in the United States, by simple faithful is I mean removing the subtle effects of age (yellowing paper), a scratch, crease in the paper, a stain, simply making it look more like it originally did before it was damaged/aged. This isn't really a high level of creativity, and there is no evidence that this kind of activity grants you copyright. Large scale restoration, like repainting a missing section of a painting, or coloring a black-and-white photograph that would, but removing a scratch or dust, wouldn't. That's the issue. — raekyt 19:11, 8 July 2012 (UTC)
- Credit is not the issue, I've already mentioned above, how credit can be indicated on these images. What the OP is claiming a CC-BY copyright over an original work, that is in the PD, something which the 1988 Act cannot confer.--Aspro (talk) 18:52, 8 July 2012 (UTC)
- Totally with you there, Adam. You should get a credit for the restoration. Formerip (talk) 18:15, 8 July 2012 (UTC)
- Since when does a UK court have to uphold a law passed by Parliment, EVER, before Wikipedia obeys it? This is an era of international corporations, when American companies like Apple, GE, and Microsoft have to consider EU regulators before merging, bundling, or producing a new product. The argument that this is an American organization so we dont care about British copyright seems silly to me. As does the idea that a British court needs to approve Parliment's laws. Parliment IS the "supreme court" of the UK. To my knowledge there is no court that could possibly invalidate Parliment's law, ever. Wikipedia should not ignore a sovereign law. Silly or not.Camelbinky (talk) 17:46, 8 July 2012 (UTC)
- On this issue, Wikimedia takes exception to the UK law, see commons:Commons:When to use the PD-Art tag and specifically the comment by Erik Möller about this. — raekyt 18:07, 8 July 2012 (UTC)
- Since when does a UK court have to uphold a law passed by Parliment, EVER, before Wikipedia obeys it? This is an era of international corporations, when American companies like Apple, GE, and Microsoft have to consider EU regulators before merging, bundling, or producing a new product. The argument that this is an American organization so we dont care about British copyright seems silly to me. As does the idea that a British court needs to approve Parliment's laws. Parliment IS the "supreme court" of the UK. To my knowledge there is no court that could possibly invalidate Parliment's law, ever. Wikipedia should not ignore a sovereign law. Silly or not.Camelbinky (talk) 17:46, 8 July 2012 (UTC)
- The Wikimedia Foundation very much respects the copyright laws of all nations. What's tripping people up here is their emotional interpretation of the 1988 Act and the way they feel the law ought to be practiced.--Aspro (talk) 18:19, 8 July 2012 (UTC)
- I think Erik Möller put it pretty plainly how they're going to handle this situation, specifically when it dept with the NPR legal threats. I don't see how this is much different, a individual UK citizen that is a contributor here by restoring images carries with it far less legal weight than the NPR, and Wikimedia basically said they're not going to recognize their legal claims. Adam may have legal copyright claims in the United States for restoration work that exceeds beyond the simple, i.e. recreating large missing sections of an artwork, but for simply color correcting, removing yellowing paper, small stains, scratches, dust, simple clone tool work, that doesn't grant copyright and would be something the foundation has already ruled in how they wish to handle that when it comes to Adam's claims of copyright. I mean if Jimbo wants to jump in here and specificly state Wikimedia's policy on simple faithful restorations of public domain images, that would be great, because right now there has never been an "official" legal position by wikimedia on this, and I pretty sure there hasn't even been a court case in the United States or UK dealing with this either, so it's really left up to interpretations. *shrug* — raekyt 18:25, 8 July 2012 (UTC)
- First of all, to the best of my knowledge, the NPR didn't restore images, merely photographed/scanned them, and, at most, colour corrected them. I do a hell of a lot more than that. Also, there are small areas of missing information in this. 86.139.213.143 (talk) 18:56, 8 July 2012 (UTC)
- Do you honestly assert that removing dust or a scratch is of such significant creative effort as to confer copyright? — raekyt 18:58, 8 July 2012 (UTC)
- People on Commons assert that removing a copyright watermark on an image make the image a derivative. John lilburne (talk) 19:09, 8 July 2012 (UTC)
- And what is the policy for that? heh. — raekyt 19:13, 8 July 2012 (UTC)
- Apparently they don't like watermarks, so clone them out just as if it was a dust mark, then claim that is justified as they can make derivatives. Naturally one major image donor of some 80,000 images disagrees and has stopped donating anymore images to Commons. John lilburne (talk) 19:24, 8 July 2012 (UTC)
- Maybe that is something that should be addressed in Common's policy if it's an actual problem? But absence of said policy just because some people think it does qualify as giving them copyright over the modified image by simply cropping or cloning off a simple watermark doesn't mean it's valid. — raekyt 19:28, 8 July 2012 (UTC)
- Because of the way the Commons works, if an image is freely licensed and it does have a watermark, it can be removed (but the original source/author/licensing information must be transferred over to the new image). I know there are a lot of people who do not think that and just put any license they want. I admit the Commons is a mess when it comes to this (and with the work I do on there, I do not deal with a lot of watermarked images unless I am involved in an OTRS compacity). User:Zscout370 (Return Fire) 19:32, 8 July 2012 (UTC)
- The claim on Commons is that cloning/cropping out Copyright Management Information is covered under making a derivative work. If that is true then cropping/cloning out a dust spot or scratch is making a derivative work too. John lilburne (talk) 19:53, 8 July 2012 (UTC)
- Link to the actual policy that states that? — raekyt 19:56, 8 July 2012 (UTC)
- Pick your link. John lilburne (talk) 20:28, 8 July 2012 (UTC)
- None of those support your statement that the remover of the watermark is granted any kind of copyright over the image from the act of removal, that is what I was specifically asking for. — raekyt 20:30, 8 July 2012 (UTC)
- Do try to keep up. The rationale for removing the CMI from the image is that it is allowed as one is making a derivative. If one is not making a derivative then one should not be cloning/cropping the CMI from the image. "A derivative work is a new, original product that includes aspects of a preexisting, already copyrighted work." thus Comnmons claims that cropping/cloning is indeed making "a new, original product". John lilburne (talk) 20:38, 8 July 2012 (UTC)
- I think your confused here, a derivative work is yes a new work made with an existing one, BUT the creator of the derivative can only claim copyright on the NEW material added to the work, here we're talking about cropping an image to remove a watermark as a derivative, yes it's a derivative, but NOT copyright-able by the person making the derivative since no NEW ORIGINAL MATERIAL is being added to the work. Same can be said with removal of a watermark, your not adding new material, simply removing it. The extent of the cloning needed to accomplish this removal may stretch the issue, but very MINOR clone tool work I think would be extremely hard to claim is substantive enough to be covered under copyright. Again I don't see any policy of commons to backup your assertion... — raekyt 20:46, 8 July 2012 (UTC)
- Not I. You can alter an image under a CC-BY license if you are creating a derivative under copyright law. One cannot invoke the right to make derivatives to justify some action (cloning or cropping out) that is not making a derivative. So either the cloning/cropping out CMI is creating a derivative in which case the OP is correct, or it is not and the Commons policy of cloning/cropping is outside the license. I don't think one can have it both ways. John lilburne (talk) 21:03, 8 July 2012 (UTC)
- It is not a case of having it both ways! You're mixing premises. The actions can be the same but the status of that -which is acted upon- can be different.--Aspro (talk) 21:24, 8 July 2012 (UTC)
- Not I. You can alter an image under a CC-BY license if you are creating a derivative under copyright law. One cannot invoke the right to make derivatives to justify some action (cloning or cropping out) that is not making a derivative. So either the cloning/cropping out CMI is creating a derivative in which case the OP is correct, or it is not and the Commons policy of cloning/cropping is outside the license. I don't think one can have it both ways. John lilburne (talk) 21:03, 8 July 2012 (UTC)
- I think your confused here, a derivative work is yes a new work made with an existing one, BUT the creator of the derivative can only claim copyright on the NEW material added to the work, here we're talking about cropping an image to remove a watermark as a derivative, yes it's a derivative, but NOT copyright-able by the person making the derivative since no NEW ORIGINAL MATERIAL is being added to the work. Same can be said with removal of a watermark, your not adding new material, simply removing it. The extent of the cloning needed to accomplish this removal may stretch the issue, but very MINOR clone tool work I think would be extremely hard to claim is substantive enough to be covered under copyright. Again I don't see any policy of commons to backup your assertion... — raekyt 20:46, 8 July 2012 (UTC)
- Do try to keep up. The rationale for removing the CMI from the image is that it is allowed as one is making a derivative. If one is not making a derivative then one should not be cloning/cropping the CMI from the image. "A derivative work is a new, original product that includes aspects of a preexisting, already copyrighted work." thus Comnmons claims that cropping/cloning is indeed making "a new, original product". John lilburne (talk) 20:38, 8 July 2012 (UTC)
- None of those support your statement that the remover of the watermark is granted any kind of copyright over the image from the act of removal, that is what I was specifically asking for. — raekyt 20:30, 8 July 2012 (UTC)
- Pick your link. John lilburne (talk) 20:28, 8 July 2012 (UTC)
- Link to the actual policy that states that? — raekyt 19:56, 8 July 2012 (UTC)
- The claim on Commons is that cloning/cropping out Copyright Management Information is covered under making a derivative work. If that is true then cropping/cloning out a dust spot or scratch is making a derivative work too. John lilburne (talk) 19:53, 8 July 2012 (UTC)
- Because of the way the Commons works, if an image is freely licensed and it does have a watermark, it can be removed (but the original source/author/licensing information must be transferred over to the new image). I know there are a lot of people who do not think that and just put any license they want. I admit the Commons is a mess when it comes to this (and with the work I do on there, I do not deal with a lot of watermarked images unless I am involved in an OTRS compacity). User:Zscout370 (Return Fire) 19:32, 8 July 2012 (UTC)
- Maybe that is something that should be addressed in Common's policy if it's an actual problem? But absence of said policy just because some people think it does qualify as giving them copyright over the modified image by simply cropping or cloning off a simple watermark doesn't mean it's valid. — raekyt 19:28, 8 July 2012 (UTC)
- Apparently they don't like watermarks, so clone them out just as if it was a dust mark, then claim that is justified as they can make derivatives. Naturally one major image donor of some 80,000 images disagrees and has stopped donating anymore images to Commons. John lilburne (talk) 19:24, 8 July 2012 (UTC)
- And what is the policy for that? heh. — raekyt 19:13, 8 July 2012 (UTC)
- People on Commons assert that removing a copyright watermark on an image make the image a derivative. John lilburne (talk) 19:09, 8 July 2012 (UTC)
- Do you honestly assert that removing dust or a scratch is of such significant creative effort as to confer copyright? — raekyt 18:58, 8 July 2012 (UTC)
- First of all, to the best of my knowledge, the NPR didn't restore images, merely photographed/scanned them, and, at most, colour corrected them. I do a hell of a lot more than that. Also, there are small areas of missing information in this. 86.139.213.143 (talk) 18:56, 8 July 2012 (UTC)
- I think Erik Möller put it pretty plainly how they're going to handle this situation, specifically when it dept with the NPR legal threats. I don't see how this is much different, a individual UK citizen that is a contributor here by restoring images carries with it far less legal weight than the NPR, and Wikimedia basically said they're not going to recognize their legal claims. Adam may have legal copyright claims in the United States for restoration work that exceeds beyond the simple, i.e. recreating large missing sections of an artwork, but for simply color correcting, removing yellowing paper, small stains, scratches, dust, simple clone tool work, that doesn't grant copyright and would be something the foundation has already ruled in how they wish to handle that when it comes to Adam's claims of copyright. I mean if Jimbo wants to jump in here and specificly state Wikimedia's policy on simple faithful restorations of public domain images, that would be great, because right now there has never been an "official" legal position by wikimedia on this, and I pretty sure there hasn't even been a court case in the United States or UK dealing with this either, so it's really left up to interpretations. *shrug* — raekyt 18:25, 8 July 2012 (UTC)
- The Wikimedia Foundation very much respects the copyright laws of all nations. What's tripping people up here is their emotional interpretation of the 1988 Act and the way they feel the law ought to be practiced.--Aspro (talk) 18:19, 8 July 2012 (UTC)
- At this point I don't know what your talking about, the laws behind what is copyrightable on a derivative work is pretty clear, and the OP was making an argument about sweat of the brow copyright not derivative work, and these are public domain images not CC images to begin with. You can't take an image and crop it then impose a copyright for that crop and expect that to be upheld in court, just as you can't take someone's book, add some annotations too it then claim copyright over the original book's wording, you only get to claim copyright on the NEW material (the annotations). A Derivative Work is not a copyright license, it's a legal term, and does not automatically confer copyright to whoever derived a new version of a past work, theres a threshold of originality that must be met. — raekyt 21:08, 8 July 2012 (UTC)
- Hmmm. The OP is not claiming copyright on the image but on the new material that he has added. However, it is claimed here that what the OP is doing does not create any claim in copyright as he is not creating a derivative under copyright law. OTOH Commons clones out 'watermarks' (Copyright Management Information) which is prohibited under Title 17 USC § 1202. Commons justifies the cloning out by arguing that the CC-BY license allows them to make derivatives. Thus the claim from Commons is that by cloning out CMI they are making a derivative. IOW if the OP does it then isn't a derivative, but if Commons does it then it is a derivative. John lilburne (talk) 21:38, 8 July 2012 (UTC)
- At this point I don't know what your talking about, the laws behind what is copyrightable on a derivative work is pretty clear, and the OP was making an argument about sweat of the brow copyright not derivative work, and these are public domain images not CC images to begin with. You can't take an image and crop it then impose a copyright for that crop and expect that to be upheld in court, just as you can't take someone's book, add some annotations too it then claim copyright over the original book's wording, you only get to claim copyright on the NEW material (the annotations). A Derivative Work is not a copyright license, it's a legal term, and does not automatically confer copyright to whoever derived a new version of a past work, theres a threshold of originality that must be met. — raekyt 21:08, 8 July 2012 (UTC)
- Adam, your skilful in what you do and as I pointed above there are was that you can claim 'credit'. But the law doesn’t work the way you think it does. Parliament produces 'good law' only, which is taken as a basic tenant. However, if courts find that some part are unenactable (unenforceable) because they can be easily demolished by Reductio ad absurdum then that part tends to get ignored. You might not like it but Parliament enacts a mountain of laws each year and if they had to go back and remove every unenactable line, phrase, or paragraph it would take them an age. So it is left to the courts. This PD issue has been discussed ad nauseam by Wikipedia and its sister projects. (Note: We have to defend PD as well without favour). Attributing a copyright to a PD work that you have rescued, without the consent of Parliament is not a right that you have under UK law. The Act would have to say something more specific about bring PD works back in copyright and it doesn't. That's why, no courts have been able to uphold it. Add your credits in the way I suggested and leave them as PD. Can you agree so we can close this section?--Aspro (talk) 19:41, 8 July 2012 (UTC)
- Aspro, I'm not sure how relevant the legal situation in the UK is but, judging from our article on sweat of the brow, you have it exactly backwards. It seems like the 1988 Act may be read as intending to abolish sweat of the brow, but the courts have declined to interpret it in that way. Formerip (talk) 20:04, 8 July 2012 (UTC)
- Formerip: The OP states “A restoration takes between about 8 and 50 hours to do right” suggesting sweat of the brow as justification par se for a CC-BY. So should you not be agreeing with me when I state above that the courts have not upheld this yet -when applied to works already in the PD? You must differentiate sweat of the brow for artistic creations, against sweat of the brow technical restorations and read the Act as it was intended. --Aspro (talk) 20:37, 8 July 2012 (UTC)
- There is extensive creative work in figuring out how to fix elements 86.139.213.143 (talk) 21:13, 8 July 2012 (UTC)
- Formerip: The OP states “A restoration takes between about 8 and 50 hours to do right” suggesting sweat of the brow as justification par se for a CC-BY. So should you not be agreeing with me when I state above that the courts have not upheld this yet -when applied to works already in the PD? You must differentiate sweat of the brow for artistic creations, against sweat of the brow technical restorations and read the Act as it was intended. --Aspro (talk) 20:37, 8 July 2012 (UTC)
- That might well be true -but that is not something that the law recognizes in the 1988 Act. The OP's question is is about the law. Believe me, I would love it to be the other way around. I could then slap copyrights on everything that I have ever sweated over. Life can seem unfair sometimes - if you look at it that way - but most people get over it.--Aspro (talk) 21:35, 8 July 2012 (UTC)
- Aspro, just above you were arguing that we should ignore the statutory wording and now you're making the opposite argument. Excuse me for not knowing how seriously to take you. And isn't "sweat of the brow for artistic creations" a contradiction in terms?
- I think you're conflating what's moral with what's legal. If Wikipedia is a reliable place to look for the information, then the OP quite possibly is the legal owner of his restoration under UK law: "one can acquire a copyright by expending skill, labour, and judgement, but no creativity or inventiveness".
- Like I say, though, I'm not sure how relevant Commons will find that. Formerip (talk) 21:46, 8 July 2012 (UTC)
- Formerip: Where do you think I have conflated my Premises? Where in the 1988 Act does it say one can acquire a copyright by expending skill, labour, and judgement, but no creativity or inventiveness? Are you trying, not to create a proper copyright argument but a Straw man? You can see why people have ridiculed the two Texas Republicans who want to ban:[5] . It might find favour with people who live out in the sticks but not in the big cities where one's job requires clear logical reasoning. :¬)--Aspro (talk) 22:36, 8 July 2012 (UTC)
- Read for instance the section 'Making News Together' in [6] which says "The court held that the effort skill and time expended by Dr Sawkins were sufficient to consider them original works in the copyright sense." An earlier judgement said shorthand writers reports of public speeches were copyright. Dmcq (talk) 23:58, 8 July 2012 (UTC)
- If you read the facts in that document it's pretty clear that this wasn't "faithful restoration" of a copyrighted work, there was substantial improvements and modifications, including adding new instruments, new base lines, and over a thousand other musical modifications to the original. If it was simply someone taking old analog tapes and converting them to MP3's and removing some minor audio imperfections like hiss and such, then that would be equivalent to the matter at hand. We're not talking about taking an image of a painting that was damaged and repainting part of the image to replace the damaged parts, or any other significant modifications during the restoration, that I've always said is probably copyrightable (probably because only a court would say so or not, not our place to rule on it), but for MINOR FAITHFUL REPRODUCTIONS, there's a difference here, the threshold of originality would need met, and even in the UK this isn't entirely trivial to meet. — raekyt 00:08, 9 July 2012 (UTC)
- I think you're misunderstanding that case. It doesn't seem to be an audio restoration, but the correction and annotation of various written scores that had errors in them or of which no definitive version existed (ie he created hybrid versions for different sources).
- On the other hand, audio remasters do seem to be copyrightable in the UK. If you're in the UK and own any CDs that have been remastered, check the copyright statement. Formerip (talk) 01:59, 9 July 2012 (UTC)
- If you read the facts in that document it's pretty clear that this wasn't "faithful restoration" of a copyrighted work, there was substantial improvements and modifications, including adding new instruments, new base lines, and over a thousand other musical modifications to the original. If it was simply someone taking old analog tapes and converting them to MP3's and removing some minor audio imperfections like hiss and such, then that would be equivalent to the matter at hand. We're not talking about taking an image of a painting that was damaged and repainting part of the image to replace the damaged parts, or any other significant modifications during the restoration, that I've always said is probably copyrightable (probably because only a court would say so or not, not our place to rule on it), but for MINOR FAITHFUL REPRODUCTIONS, there's a difference here, the threshold of originality would need met, and even in the UK this isn't entirely trivial to meet. — raekyt 00:08, 9 July 2012 (UTC)
- Read for instance the section 'Making News Together' in [6] which says "The court held that the effort skill and time expended by Dr Sawkins were sufficient to consider them original works in the copyright sense." An earlier judgement said shorthand writers reports of public speeches were copyright. Dmcq (talk) 23:58, 8 July 2012 (UTC)
- Formerip: Where do you think I have conflated my Premises? Where in the 1988 Act does it say one can acquire a copyright by expending skill, labour, and judgement, but no creativity or inventiveness? Are you trying, not to create a proper copyright argument but a Straw man? You can see why people have ridiculed the two Texas Republicans who want to ban:[5] . It might find favour with people who live out in the sticks but not in the big cities where one's job requires clear logical reasoning. :¬)--Aspro (talk) 22:36, 8 July 2012 (UTC)
- As I said above they should include both the PD license for the US and a CC-BY_SA or other one one for the EU. Dmcq (talk) 22:25, 8 July 2012 (UTC)
- While I think it's questionable whether or not simple digital restoration is copyrightable, I see no reason not to allow the person who does the work to release their work under a Commons-compatible license if they wish. We already have tags, such as commons:Template:Licensed-PD-Art, which are used by institutions to release reproductions of public domain works under a free license. The point of such tags is that PD-Art law varies from nation to nation, and in nations where the PD-Art policy might not apply it is important to have a "fallback" license. I believe the same argument applies in this case - Adam's edits may be copyrightable in some jurisdictions, and content reusers in those jurisdictions would benefit from an assurance that the work is under a free license there. On the other hand, we should also be clear that in jurisdictions where that work is not copyrightable, content reusers are not obligated to comply with the license. Dcoetzee 04:07, 9 July 2012 (UTC)
- I don't think commons:Template:Licensed-PD-Art is a problem, provided Adam is ok with it? It addresses my concerns making it clear that the work is public domain but may hold copyright in other countries, which is Adam's concern, I think. — raekyt 04:11, 9 July 2012 (UTC)
- I think this case is similar, but not completely identical, to the Licensed-PD-Art case, in that we are not addressing only copyrightability of a slavish digital reproduction, but also threshold of originality (whether his alterations rise to the point of copyrightability), which also varies between jurisdictions. As such a slightly different template might be needed, stating something like this: "This work has been digitally restored, and those modifications have been released under the following license: (license) In some jurisdictions the changes involved in digital restoration are not copyrightable, and complying with the above license is not compulsory." Dcoetzee 04:31, 9 July 2012 (UTC)
- I don't think commons:Template:Licensed-PD-Art is a problem, provided Adam is ok with it? It addresses my concerns making it clear that the work is public domain but may hold copyright in other countries, which is Adam's concern, I think. — raekyt 04:11, 9 July 2012 (UTC)
- If the text is changed to ""This work has been digitally restored, and those modifications have been released under the following license: (license) In some jurisdictions, the changes involved in digital restoration may not be copyrightable." I'd agree. Though I think it's ridiclously convoluted, as it's not like a CC-by license is at all restrictive, and it guarantees worldwide copyight status. But then, Wikipedia regularly states core principles (e.g. Commons attempts to be a repository of materials that can be used worldwide) then ignores them whenever it suits. 31.54.23.15 (talk) 10:03, 9 July 2012 (UTC)
Your page at pt.wiki
Hi, Jimbo. I think some changes are needed on your user page at pt.wiki. I was reading it and I could find a few errors; probably good faith mistakes when translating. Some sentences apparently don't have the desired meaning. I was about to fix that, but I don't see the text in English I can use as parameter. If you can provide a text, I bet there are a few users that could help on improving that page. A link to that text in English works (or, if you want an update, a new text is also fine). Regards.‴ Teles «Talk ˱@ L C S˲» 08:31, 9 July 2012 (UTC)
Wikipedia's techno black hole
Would it be too much to ask of Wikipedia that its basic editing tools be workable? The toolbar has been sliding from flawed to nonfunctional for a long time. Is this the Wikipedia black hole of space? At the moment, I can't do an "Insert" for the links here. Can't Wikipedia do better than this at enabling its editors? Maile66 (talk) 11:16, 9 July 2012 (UTC)
http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Toolbar_bloopers
http://en.wikipedia.org/wiki/Wikipedia_talk:RefToolbar_2.0
http://en.wikipedia.org/wiki/Wikipedia_talk:RefToolbar_1.0
A kitten for you!
![](http://upload.wikimedia.org/wikipedia/commons/thumb/6/6b/Kitten_in_a_helmet.jpg/150px-Kitten_in_a_helmet.jpg)
Hello:)