FlightTime
Status: (Around)
{{ping|FlightTime}}
with your message. Thank you
If you feel that I have reverted an edit or issued a warning in error, please Click Here and let me know. I am human, and I do make mistakes. Please don't interpret an error on my part as a personal attack on you. It's not, I promise. I ask you to simply bring it to my attention; I am always open to civil discussion. To keep discussions coherent, I will usually answer in the talk page where the first message was placed. If I left you a message on another talk page, please answer there: I will have it on my watch list. Thank you. |
No RfXs since 17:37, 25 December 2024 (UTC).—cyberbot ITalk to my owner:Online |
Welcome To My Alternate Talk Page FlightTime ( talk · contribs · count · accounts · move log · global rename log · uploads · logs · rights)
Click here to leave a new message
It is 3:14 PM where this user lives in the Mojave Desert. ( )If you're here, then my main talk page is protected. I do occasionally check this page, but to be sure I'm aware of your post please include {{ping|FlightTime}} with your message. Thank you FlightTime
|
Welcome to my talk page.
Archives Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 |
This talk page is automatically archived by lowercase sigmabot III. Any threads with no replies in 14 days may be automatically moved. Threads with fewer than two timestamps (no replies) are not archived. |
Redirect suppression
editHi FlightTime. While I was looking at some file moves, I noticed that you still almost always rename file without leaving behind a redirect. Per WP:PMRC, redirect suppression is permitted only for redirects that would have otherwise been eligible for speedy deletion. (Indeed, "a pattern of using the permission to suppress redirects that would not have been eligible for one of the criteria for speedy deletion" is a ground for revocation per WP:PMRR#3.) As I noted to you over a year ago, there used to be a boldly added redirect-suppression criterion PMRC#10 (link to an old page version) for "Moving little-used files when all uses have been manually changed to the new title (WP:CSD#G6)" from 2019 to 2022, but it was removed because there was substantial opposition to deleting/suppressing these redirects, so it didn't have the consensus necessary to be included in a criterion for speedy deletion.
Additionally, when you rename files without leaving a redirect, it seems that you sometimes request deletion of existing redirects for the file as G8. However, that criterion explicitly excludes "Redirects that were broken as a result of a page move or retargeting (these should instead be retargeted to their target's new name), except where R2 speedy deletion would then immediately apply if they were fixed (e.g., redirects to articles that have been draftified)". For example, File:CHowan.png and File:TaiwanBeer Leopards.webp were therefore ineligible for G8.
With that in mind, could you tell me what criterion for speedy deletion (or equivalently redirect suppression), if any, each of the following suppressed move redirects (to pick a few) would fall into?
- File:Chowan University (logo).png
- File:Commentary on Palestine Peace Not Apartheid.jpg
- File:Sven Höek title card.jpg
- File:Godzillasaurus 1954.jpg
- File:Screenshot 2024-07-14 10.13.39 PM.png
SilverLocust 💬 03:05, 9 January 2025 (UTC)
- Sorry, I don't see the problem here. If there are no incoming important links I do not create needless redirects, if a redirect exist that no longer has a target I request deletion, however I do see your point about redirecting the existing redirect to the new target. - FlightTime (open channel) 01:10, 10 January 2025 (UTC)
- For one thing, suppressing the file redirect will always break the image in old revisions of whatever articles used the image, see
- As someone who looks at old revisions of pages fairly often, it's somewhat annoying when the images are broken due to renaming when there was no reason that they needed to be broken – and indeed given that it usually violates policy to suppress these redirects. Additionally, not all incoming links are wikilinks. People do link to Wikipedia from other websites as well as reuse Wikipedia content, which almost always requires linking for articles and sometimes requires linking for images. Since redirects are cheap, they should generally be left unless problematic. See also the discussion I mentioned previously for some reasons people gave that these file redirects shouldn't be suppressed.
- I'd also note that you didn't answer my question above. If you don't have an answer, my assumption is that you're not able to point to criteria to support those redirect suppressions. I'll pose another question. Would you rather (A) try to use page mover permissions in a manner consistent with the policy, specifically as it relates redirect suppression (which you always have the opportunity to seek to change by consensus), or (B) no longer have page mover permissions? I would hope that's easy to answer. SilverLocust 💬 05:31, 10 January 2025 (UTC)
- @SilverLocust:, Well, "for one thing, I always fix article (file display) links before I even rename a file, any other links ie.. bot reports, user's archive pages, anyone can still click the red link and get the new filename from the move report. I have no control what others' do (permalink), (permalink), (permalink), (permalink) None of those permalink are of my doing. Is this some kind of training issue or a prelude to you removing my move rights? - FlightTime (open channel) 14:34, 10 January 2025 (UTC)