User talk:Smasongarrison/Archives/2022
Please don't ever change the dimensions of any svg fle. - Erik Baas (talk) 01:14, 24 July 2022 (UTC)
Useless, and the code is a mess.
If you really want to compress SVG files, try this:
<svg width="274.6" height="100" xmlns="http://www.w3.org/2000/svg"> <defs> <pattern id="Pattern" width=".125" height=".5"> <path id="X" d="M24 21v6H8v-6c0-3 3-5 6-5h4c3 0 6 2 6 5zm-8-6a5 5 0 1 0 0-10 5 5 0 0 0 0 10z"/> </pattern> </defs> <rect fill="url(#Pattern)" width="200" height="50"/> </svg>
You'll see 16 puppets in a rectangle, like File:16 people icon.svg. NB.: It's not the same, but I wrote this in a couple of minutes to demonstrate what SVG is all about. File size: 316 bytes!!! - Erik Baas (talk) 03:01, 25 July 2022 (UTC)
- Well, thanks for spending the time to write this...
- Right now, I'm mostly just poking around as I think thru how to incorporate wikimedia into my data science class. Smasongarrison (talk) 03:09, 25 July 2022 (UTC)
MwJSBot.js[edit]
Hi. How did you use MwJSBot.js to reduce SVG file size? I installed Rillke's SVGedit.js, but none of the buttons seem to do anything. (Please ping.) Thanks, Kwamikagami (talk) 09:25, 26 July 2022 (UTC)
- Kwamikagami, I didn't. I copy and pasted from various manual svg cleaners. Smasongarrison (talk) 12:33, 26 July 2022 (UTC)
- Okay, thanks. Kwamikagami (talk) 18:41, 26 July 2022 (UTC)
File source is not properly indicated: File:Uwiringiyimana Agathe.png[edit]
This media was probably deleted. |
A file that you have uploaded to Wikimedia Commons, File:Uwiringiyimana Agathe.png, was missing information about where it comes from or who created it, which is needed to verify its copyright status. The file probably has been deleted. If you've got all required information, request undeletion providing this information and the link to the concerned file (
[[:File:Uwiringiyimana Agathe.png]] ).
If you created the content yourself, enter If someone else created the content, or if it is based on someone else's work, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you! |
GeorgHH • talk 13:45, 30 July 2022 (UTC)
- Hopefully, the original uploader has that missing information. I only cropped the already uploaded image. Regardless, thanks for all your hard work on tasks like this! Smasongarrison (talk) 14:18, 30 July 2022 (UTC)
File:American Legion Seal SVG.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Jonteemil (talk) 20:46, 8 August 2022 (UTC)
Please notice that your alteration clipped off part of the image. Fry1989 eh? 00:24, 3 August 2022 (UTC)
- My apologies for not seeing that! Thanks for letting me know. I'll fix it. Smasongarrison (talk) 00:26, 3 August 2022 (UTC)
- Greetings once more. It appears a distortion has happened by accident to File:Flag of Zimbabwe (Variant).svg. Fry1989 eh? 21:30, 10 August 2022 (UTC)
- Thanks for catching that. (What I suspect happened is that when I double checked the render after a cache purge, I accidently just hit refresh instead.) Smasongarrison (talk) 23:50, 10 August 2022 (UTC)
- Greetings once more. It appears a distortion has happened by accident to File:Flag of Zimbabwe (Variant).svg. Fry1989 eh? 21:30, 10 August 2022 (UTC)
File:Flag of SFR Yugoslav Turkish Minority.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
— Red-tailed hawk (nest) 01:47, 13 August 2022 (UTC)
Please halt your conversions with svgomg[edit]
Hi!
I recently noticed that you had been applying svgomg to some of the files I've been uploading. E.g. File:Ronneby_vapen.svg. While I'm sure there is some optimising which can be done your script is doing two things which are undesirable. The first is that it deletes all of the metadata, that includes embedded creator, license, date and title information. The second is that it deletes any id-tags which I've manually added. I normally name the larger components to make the files easier to reuse (and to make the xml easier to navigate). All of this careful work gets nuked by your script. I'd appreciate it if you could revert your changes to the affected files and halt your script until you have addressed at the very least the metadata issue. /Lokal_Profil 07:13, 1 August 2022 (UTC)
- Absolutely! My apologies. Smasongarrison (talk) 12:45, 1 August 2022 (UTC)
- How does this one look? https://commons.wikimedia.org/wiki/File:Heraldic_Horse_head.svg
- I smoothed some paths, but kept all the metadata and ids. (If it isn't ok, I'm happy to revert.) regardless, your feedback was really appreciated and resulted in me looking much more carefully at the innards of files.
- Smasongarrison (talk) 15:10, 13 August 2022 (UTC)
Issues with SVGOMG version of File:NROL_39_vector_logo.svg[edit]
Hey, I notice you uploaded a new slimmed down version of NROL_39_vector_logo.svg but I noticed the background's gradient is absent and appears to show flat #002439 color instead. My upload preserved the gradients which other uploads missed during conversion from PDF. I am reverting it for now but after fixing that feel free to upload an alternate version. Thank you. Ohsin (talk) 05:18, 28 August 2022 (UTC)
- I reverted it but 600px preview still renders flat color, perhaps a cache related issue. Ohsin (talk) 05:34, 28 August 2022 (UTC)
- Thanks for catching that! Sorry for missing it, which I trimmed down the file. Probably had the same cache issue when I looked at it to see if it had preserved everything. Smasongarrison (talk) 06:22, 28 August 2022 (UTC)
File:Allianz Riviera Logo.svg has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that.
The file you added has been deleted. If you have written permission from the copyright holder, please have them send us a free license release via COM:VRT. If you believe that the deletion was not in accordance with policy, you may request undeletion. (It is not necessary to request undeletion if using VRT; the file will be automatically restored at the conclusion of the process.) Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.
|
Elisfkc (talk) 22:25, 28 August 2022 (UTC)
Hello, can you edit the resolutions of File:Flag of the United States (1959-1960, 3-2 aspect ratio).svg, from "800 × 487" to "800 × 533 pixel", as File:Flag of the United States (3-2 aspect ratio).svg? Stephan Sensuality (talk) 23:42, 31 August 2022 (UTC)
File:Flag of Moroni, Comoros.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
SpinnerLaserzthe2nd (talk) 11:58, 12 September 2022 (UTC)
File:Finnish Christian Democrats logo FI.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
— Red-tailed hawk (nest) 01:27, 23 September 2022 (UTC)
File:Chaser Flag.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Pseudomonas (talk) 17:48, 6 October 2022 (UTC)
COM:AN[edit]
Glrx (talk) 02:44, 10 October 2022 (UTC)
Please stop "optimizing" SVG files[edit]
Applying optimizers to SVG images is against guidelines. See Help:SVG guidelines.
Furthermore, you are damaging images. See File:Ambox metro icon.svg where your optimization changed the appearance of th image.
Moreover, you are removing SVG metadata
that includes license information and elements such as cc:attributionUrl
. Removing metadata may violate license agreements. See, for example §3.a.1.A at [Creative Commons — Attribution-ShareAlike 4.0 International — CC BY-SA 4.0 CC-BY-SA 4.0 legal code] that requires retaining supplied information.
Glrx (talk) 02:32, 10 October 2022 (UTC)
- As I explained in the AN post,
I wasn't aware that reducing file sizes was against the SVG guidelines. My apologies if that's the case. Smasongarrison (talk) 03:30, 10 October 2022 (UTC)
Anyway... I'm going back through my edits to see if there are any other errors I accidentally added. Smasongarrison (talk) 03:46, 10 October 2022 (UTC)
Smasongarrison (talk) 12:32, 10 October 2022 (UTC)
Furthermore[edit]
your svgomg-edits made W3C-valid files invalid, as Abc box.svg.
As with BSicon hKRZWa red.svg or Icelandic Socialist Party.svg, such very simple images can be redrawn with a text editor instead of svgomged, when a justfied need for a new upload exists. -- sarang♥사랑 11:22, 10 October 2022 (UTC)
- As I explained in the AN post,
I wasn't aware that reducing file sizes was against the SVG guidelines. My apologies if that's the case. Smasongarrison (talk) 03:30, 10 October 2022 (UTC)
Anyway... I'm going back through my edits to see if there are any other errors I accidentally added. Smasongarrison (talk) 03:46, 10 October 2022 (UTC)
Smasongarrison (talk) 12:32, 10 October 2022 (UTC)
Dupe cat[edit]
Category:U+0023 vs Category:Hash. They should be either properly disambiguated, or merged. Taylor 49 (talk) 09:43, 12 October 2022 (UTC)
File tagging File:Agents Photo3.jpg[edit]
This media was probably deleted.
|
Thanks for uploading File:Agents Photo3.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case.
Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:Agents Photo3.jpg]] ) and the above demanded information in your request. |
— Haseeb (talk) 03:56, 13 October 2022 (UTC)
Notification about possible deletion[edit]
Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.
If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Affected:
Matr1x-101 (talk) 18:53, 3 November 2022 (UTC)
Convert to SVG[edit]
I noticed that you tagged File:Africa relief location map.jpg and File:Africa land cover location map.jpg with {{Convert to SVG|map}}. To be honest with you, I'm not convinced that's a good idea, because I know from experience, that when done properly (i.e., by not producing a fake SVG), the result will be anything but satisfactory. M.Bitton (talk) 01:53, 8 November 2022 (UTC)
- I was on the fence about tagging them based on the same reasoning you mentioned. I was also leaning toward tagging them as "{ { BadJPEG } } ". Do you think that would have been the better choice? Smasongarrison (talk) 02:02, 8 November 2022 (UTC)
Wrong taggings[edit]
You redraw Flag of Yellow Ukraine.svg but did not update that it is now drawn with a text editor, you let it "Created with Inkscape".
It is your resposibility to correct file descriptions after a substantial change !
When you make such changes, please don't leave a mess of wrong descriptions. -- sarang♥사랑 09:19, 25 November 2022 (UTC)
- Thanks, I appreciate the feedback. Smasongarrison (talk) 16:35, 25 November 2022 (UTC)
Welcome[edit]
Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content). You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki. More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump. |
|
-- 03:08, 14 February 2012 (UTC) — Preceding unsigned comment added by Wikimedia Commons Welcome (talk • contribs) 03:08, 14. Feb. 2012 (UTC)
Since Wikimedia-Projects, (i) don't have any hirachy (decissions should be argument-based, which needs a lot of time), and (ii) have a high fluctuation of new people, and (iii) reentering Users, that are ignoring the rules, Wikimedia-Projects are in my opinion a very harsh place, to keep the administration administrable. Expecially as a Newbie, not knowing all the rules, this might can feel demotivating to some.
I think most Users, including Admins, mostly gained critics at the begining. At the beginning I also did some useless svg-file-optimizations and then I adapted my svg-edits to more usefull edits (mostly repairing broken SVGs), and I also wrote the first draft of Help:SVG_guidelines. If you need any help, feel free to message me.
Best — Johannes Kalliauer - Talk | Contributions 00:38, 27 November 2022 (UTC)
Please stop[edit]
Please stop immediately your converting of SVG files !
It is not only not required, it is clearly against the rules we have on Commons.
Furthermore, you are not doing good work, sorry. SVGomg can be a helpful tool, but you are using it as your toy;
treating simple SVG files with SVGomg is not always the best choice to reduce file size, this should better be done by manual recoding.
See as an example VWASSER.svg:
it had been drawn with Inkscape needing 40.774 bytes,
you made it 602 bytes,
but really simplified it will need 215 bytes (5.2 ‰).
This is a file not used anywhere — it is of no use to treat unneeded files !
Another example of many is Flag of Umayyad.svg, with 199.617, 733 and 165 bytes (0.8 ‰).
Or Cercle vert 50%.svg, with 2.242, 362 and 187 bytes.
There is really a lot of work needed on Commons to make things better. Your playing with hundreds of files does not make anything better, on the contrary, it just increases disc space.
Please keep your fingers off from not-so-efficient files.
When you want to be a useful contributor on Commons, I can tell you what is really in need.
Or when you see the request to redraw one or the other SVG file, you can be told how drawing can be done.
When you have some idle time and like to use it for the Wp community, there is enough work waiting. -- sarang♥사랑 07:49, 18 November 2022 (UTC)
- More essential:
- when you change a file, you should always update the image generation taggings to the current file state, and not leave a now wrong description.
- And when you touch an SVG file not having yet the Image generation taggings, you should add one of the current file state.
- it will also be good habit to check the W3C-validity before you upload an SVG. Your Cercle vert 50%.svg has severe errors.
- This is much more necessary and helpful than your mass-treating of correctly working SVG files. -- sarang♥사랑 17:34, 18 November 2022 (UTC)
- Hi sarang,
- I understand that you have strong feelings about this issue. I read thru the guidelines, and thought that they were just that guidelines... We've had these conversations before and I tried to be responsive on this issue. But no one else including any admin (or youself) said anything about whether these were rules or guidelines. My interpretation is that these are guidelines, not rules. https://commons.wikimedia.org/wiki/Commons:Administrators%27_noticeboard/Archive_90#Massive_edits Smasongarrison (talk) 17:44, 18 November 2022 (UTC)
- Hi!
- I think you have a missconception about policities and guidlines.
- Administrators can enforce everything that is well-founded and/or is in consensus with the community, Commons:Policies_and_guidelines just help them to decide. (Commons:Ignore_all_rules)
- In theory: If someone makes something stupid, which is neither written in any guideline nor discussed on any talk-page, could be blocked infinitly without any warning. (Generally that won't happen because most common serious violations are written in policies/guidelines, or users get at least a warning of stopping their behaviour.)
- I saw you are warned by User:Sarang on your talk-page and mentioned by User:Glrx on the Admin noticeboard. (I did not look into the details, maybe I oversaw something.)
- I, as an administrator, do not care who warned someone, if someone warned you, I expect that you read it and that you consider the given arguments.
- Even though you are right, that not every violation needs to be reported, and costs man-hours. However if somone is continouing on violating written or unwritten rules, they might have to expect consequences.
- In my opinion users normally do not need to distinglish between guidelines and policities, as soon as they are aware of them, they need to follow them, except they have reasons for validating them.
- The key difference beteween a policity and a guideline is imho that a policity has a wide acceptance, however guidelines may have exceptions, see Teminology for en:Wikipedia
- I recommend reading:
- Commons:Policies_and_guidelines or in more detail on Wikipedia: en:Wikipedia:List_of_policies_and_guidelines
- Commons:Ignore_all_rules or in more detail on Wikipedia: en:Ignore_all_rules (some even more specific essays: en:Wikipedia:"Ignore_all_rules"_essays_and_related_topics)
- I really appricate that you play with open cards and you link to relevant discussions (e.g. Special:Diff/707660992 Special:Diff/695812984) which might critizise you, that is why I assume good faith.
- According to Help:SVG_guidelines#SVG_sourcecode_edits_without_visual_change, pure source-code edits are not allowed. In the English, German and most likely most Wikipedias source-code edits are not allowed, even though they do not have any policity that prohibit them. On Wikimedia Commons most source-code edits stay unnoticed, that's why they are hardly sanctioned (differently to Wikipedia). I tollerate source-code edits to a certain extend, however you are exceeding this limit by far. And if those edits make more mistakes (1,2,3), than corrections they can't be accepted.
- Any edit needs to have a purpose to be allowed, and additionally the purpose must predominate the disadvantages. Just not violating any rules, does not legitimate to make an edit.
- Making edits just to increase your edit-count will lead to a block.
- — Johannes Kalliauer - Talk | Contributions 12:14, 21 November 2022 (UTC)
- Hi there,
- Thanks for the wisdom! I appreciate it, especially spelling out the difference in norms. In the AN post, I actually asked about this, and didn't receive any response, even from the folks who reported it. So I interpreted that as overzealous editors. However, now I understand that to be an oversight. Obviously, moving forward, I will abide by the Help pages.
- thank you for making this much clearer for me.
- ~ Smasongarrison (talk) 14:28, 21 November 2022 (UTC)
Your last upload was so bad that I redraw it -- sarang♥사랑 15:36, 21 November 2022 (UTC)
- Dude, per the guidelines isn't a tenfold reduction worthwhile? I'm glad that your improving the code, but you're going to have to be more specific about what is so bad about reducing the file size from 323 KB to 2kb. Smasongarrison (talk) 15:52, 21 November 2022 (UTC)
- Just slimming a file is of no use when it is a very poor drawing. A simple traffic sign in 1 254 × 1 254 pixel is nonsense, it is only difficult to look at without zooming. The five strokes were not equidistant; I have not looked for the design of the saudi signs, but at least the file is now a bit better,
- Reducing the file size to much below 10% is just an exception, but no allowance that such reductions should be performed ! When a file is touched (reuploaded) there should be more advantages, e.g. replacing poor Inkscape SVG code by reasonable code
- Much better than reuploading is displaying better code, for an educational purpose -- sarang♥사랑 16:01, 22 November 2022 (UTC)
- ok -- I appreciate your expanding on what you mean by "so bad". Again, I'm really trying to understand your point. about what counts as enough of an improvement. Are those kind of recommendations in that help page? (It's been a little while since I read through it. ) I'd be happy to work with you on making one if there isn't one. I think that might be a useful document to prevent miscommunications like this from happening in the future.
- Smasongarrison (talk) 17:31, 22 November 2022 (UTC)
- Is a 10-fold reduction worthwhile? Probably not. A local store sells a 16 TB disk drive for $320. That's $20/TB or $0.20/GB or $0.0002/MB. Most SVG files are less than a MB, so the storage cost is insignificant. (It also does not save any storage at WMF because files are not deleted.) It is probably not worth the labor cost to work on the file; there is no payback. Even worse can be the annoyance cost. If a file is watched, then a person will look at the change. So even if it cost nothing to reduce the file, there is a downside cost in man hours.
- Compare that to fixing a typo in an illustration. We don't care about the trivial storage cost, and those users watching the file will appreciate the improvement.
- There are plenty of stupid SVG files on Commons. Some of your edits have removed Adobe
i:PGF
. I'm happy to see that element removed, but that does not mean I would support a campaign to eliminate the element from all Commons SVG files. It is not a good thing, but it is not so bad that it needs to be stamped out completely. - The major problem I have is not showing that it's not bad but rather asking what it seeks to accomplish.
- The point of your editing campaign seems to be just slimming down the data storage requirements. That campaign has been ruthless and has had bad consequences such as affecting the display of some images. It has also removed metadata. There have been discussions about removing metadata, but there has not been consensus. Inkscape adds a lot of useless or redundant information, but it also adds information about standard symbols, drawing layers, and layout grids. It costs almost nothing to keep that information around, and the information may be valuable if the image is subsequently edited. Your campaign ignored that value. It trades a lot of problems for less than 20 cents of diskspace. There's also been a lot of controversy over the edits, and that cost is orders of magnitude above any alleged diskspace savings.
- I do not doubt you thought you were doing something reasonable.
- Glrx (talk) 20:22, 22 November 2022 (UTC)
- Thanks all of this is really helpful information. I appreciate it and all of you walking me through some of the benefits vs costs. (Sorry that this reply is brief. I've got a meeting in a couple minutes. ) Smasongarrison (talk) 14:52, 23 November 2022 (UTC)
- I wrote that a file-recution of factor 10 is tollerated. As already written it does not mean that it such file-reductions should be done. Such file-reduction could also be done fully automatic by a bot. The reason why I added this exception is because if a file will get reused several times, it might make sense to improve one image to simplify making derivatives. Sarang edits the source-code of SVGs in a text-editor, so he has a very different viewpoint. As written earlier a file-reduction, just to reduce the disk-space, does not make sense, because (i) every additional version needs additional diskspace and (ii) diskspace is cheap. Sarang rewrites codes, so that it is easier to make derivatives. Some "Useless elements" (e.g. line-breaks) should be kept in the code for better readability and ediability. With file-size-reduction, I primarly mean simplifing the code, and not so much of reducing the file-size. But thats in my opinion that is in the gray-area, where different users might come to different opinions. Simplifing a image at SVG_examples by few percantages is imho desired, however simplifing a "random" image with hardly traffic does imho hardly make any sense. That's why it is called a guideline, because (i) there might be well-explained exceptions and (ii) it is difficult to write quantiative statements.
- @Glrx: I agree everything you are saying. I would like to know your opinion on the following question: This Talkpage seems to be watched by some us, and some persons might read the comments here. So even if my edit costs no diskspace, thre is a downside cost in man hours. Or in other words: Is it worth discussing what reuploads are allowed or not, or are we just waisting everyones times?
- Rhetorical (self-critical) question: If someone could get blocked just because of tickeling watchlist because of reuploads, should I get blocked because I add a comment on this talkpage, which will be read by several users. What is the differnece? How do you measure what improvents are valuable?
- — Johannes Kalliauer - Talk | Contributions 20:44, 26 November 2022 (UTC)
- @JoKalliauer:
- Discussion is good because it helps clarify some issues. And yes, there are still areas where we may disagree. There might be a more general place to discuss it, but this discussion arose because we wanted to talk to Smasongarrison about our views. So here is fine.
- The difference is the watchers of this page choose to watch it, and the content that people add is reasonable. If some editor started adding spurious comments to random pages (thus tickling the watchlists with no purpose), was asked to stop but did not, then I think that user could be blocked to stop the disruption. A similar problem is when someone posts messages to mailing lists with hundreds of subscribers; 360 people taking 10 seconds to delete the message is a man-hour. It can also cause knowledgeable subscribers to leave the mailing list, and that might hurt the community a lot.
- For a contemporary example, SchlurcherBot annoys me and many other users. Most of its watch notices are about an SVG file is an SVG file. I do not see such an edit as valuable enough to disturb so many watch lists.
- Which improvements are valuable? That's a good question. An objective decision would examine costs, but calculating costs and benefits can be subjective. I'm tempted to say that all image files on Commons should have metadata that points to its File: page. If someone copies a file off wiki, then the metadata will still show the origin of the file. That could save somebody from a lawsuit, but it has a huge cost. And it would be unnecessary for files that are never used or never copied off wiki.
- Glrx (talk) 22:51, 26 November 2022 (UTC)
Validation[edit]
Once more: when you edit, upload, reupload an SVG file, please validate it. You reuploaded files and neither revalidated them nor made the validation when there was not yet one! You should not let it to others whats your duty when you changed something -- sarang♥사랑 13:43, 27 November 2022 (UTC)
- I appreciate the feedback, but you're going to have to point me in the right direction on how to get the validation templates to work. I spent considerable time on trying to figure it out. Smasongarrison (talk) 13:48, 27 November 2022 (UTC)
File:2008 Dancing landscape.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
Yann (talk) 19:02, 29 November 2022 (UTC)
File:Logo of Sarasota, Florida.svg has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that.
The file you added may soon be deleted. If you have written permission from the copyright holder, please replace the copyvio tag with {{subst:OP}} and have them send us a free license release via COM:VRT. If you disagree that the file is a copyright violation for any other reason, please replace the copyvio tag with a regular deletion request. Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.
|
Εὐθυμένης (talk) 09:43, 30 November 2022 (UTC)
File:Logo of Sarasota, Florida.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.
If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. |
—Mdaniels5757 (talk • contribs) 01:33, 1 December 2022 (UTC)