New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Twinkle: Avoid warning where user is tagging own work for deletion #118

Closed
BarkingFish opened this Issue Jun 17, 2012 · 4 comments

Comments

Projects
None yet
3 participants
@BarkingFish

BarkingFish commented Jun 17, 2012

For as long as I can remember using Twinkle, whenever you tag or mark an item of stuff you uploaded (userpage, talk page, image, etc) for deletion using Twinkle, it still goes ahead and warns you that you have done so. That may not be the intention, but usually when I do something, i don't have a tendency to forget within 10 seconds or so :)

Since Twinkle can already detect that a user is warning themselves, talking back to themselves, reporting themselves to ARV etc, would it be possible within Twinkle to code it to either ask if you want a warning, or for it to be added to Twinkle's preferences so that users can avoid warning themselves about stuff they already know please?

@atlight

This comment has been minimized.

Collaborator

atlight commented Jun 18, 2012

It is a fair point. I am fairly sure you can manually turn off the notification in most cases, but that is only effective if you knew you created the page yourself. (You can't turn off notification for BLP PROD, but I don't know why you would be using that for a page you created yourself!)

@mc10 mc10 closed this in 6289561 Aug 25, 2013

@atlight

This comment has been minimized.

Collaborator

atlight commented Aug 26, 2013

This doesn't fix the issue: it is still possible to notify yourself in CSD, XFD, and DI. It may be difficult to fix this in some of these modules, which is why I haven't done it already :)

@atlight atlight reopened this Aug 26, 2013

@mc10

This comment has been minimized.

Collaborator

mc10 commented Aug 26, 2013

My bad, I did not realize that the issue was more pervasive than I thought; I'll take a look at the other modules when I have time.

@atlight atlight closed this in c037748 Jun 21, 2014

@atlight

This comment has been minimized.

Collaborator

atlight commented Jun 21, 2014

Now fixed. Only took 2 years and 3 days!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment