Wikipedia talk:WikiProject User scripts/Scripts/WikiBreak Enforcer
![]() | This project page does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
|
|
|
The Department of Fun notice should be added to the article
[edit]The talk page has it, but not the project page. Anonymous from Stack Overflow (talk) 10:23, 1 December 2021 (UTC)
A way to request restore for mistake
[edit]I think we should add some ways like: request in the user talk page of an interface admin or email an interface admin (it's hard because users are logged out, or get an email address for email an interface admin like global block appeals) for people who want to hide their IP address. Thingofme (talk) 13:59, 26 February 2022 (UTC)
- I agree. Pehaps an ARB-COM style email feature allowing us to contact interface admins. ---CX Zoom(he/him) (let's talk|contribs) 13:51, 5 March 2022 (UTC)
- We should have some email like User:Interface administrators to email, because now IP address can reveal private information. Thingofme (talk) 03:27, 27 March 2022 (UTC)
Protected edit request on 8 August 2023
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
"In cases of errors, an interface admin can remove the script from your user JavaScript page for you."
This is simply inaccurate and a waste of resources. In case of errors, you should go to https://en.wikipedia.org/Special:MyPage/common.js?safemode=1 , as this simply disables all user scripts. QuickQuokka [talk • contribs] 11:13, 8 August 2023 (UTC)
Not done: That will not prevent you from being kicked back out of your account. Izno (talk) 21:07, 10 August 2023 (UTC)
- @Izno: How so?
?safemode=1
literally disables ALL user JavaScript, and I don't see how the WikiBreak Enforcer is any different. QuickQuokka [talk • contribs] 00:39, 13 August 2023 (UTC)- Because safemode does not persist in navigation. Izno (talk) 03:10, 13 August 2023 (UTC)
- @Izno: How so?
Protected edit request on 18 August 2023
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
turn the Script under
/*** BEGIN WIKIBREAK ENFORCER ***/
and /*** END WIKIBREAK ENFORCER ***/
.to regular text to remove the redundant link. Grandmaster Huon (talk) 14:56, 18 August 2023 (UTC)
Not done I fail to see the purpose of doing this. * Pppery * it has begun... 13:26, 21 August 2023 (UTC)
Protected edit request on 29 February 2024
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Urdu interwiki link is wrong and nonetheless leads to a non-existent page. Please remove it. Best regards, ─ Aafī (talk) 08:52, 29 February 2024 (UTC)
Protected edit request on 30 March 2025
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Remove the link set on logged back out
in the second sentence, which is currently WP:LOGOUT because it takes you to the "Editing while logged out" section of the WP:SOCK policy, and it is not relevant to the context of this sentence. Justjourney (talk) 04:13, 30 March 2025 (UTC)
This doesn't work if your device time is incorrect or if you change it
[edit]You can easily bypass the enforcer - if you just change your device time > enforcedBreakEnd
Big flaw. If people knew about this flaw - this entire feature becomes irrelevant Cinaroot (talk) 15:06, 16 May 2025 (UTC)
- @Cinaroot I don't think it's intended to flawlessly lock you out of your account, but make it more difficult to get back in so you think: Hey, should I really skip my break? loserhead (talk) 15:35, 16 May 2025 (UTC)
- Well - this is supposed to be a enforced break. Sometimes we need it to stop addiction or remove ourselves from conflict etc... If I was able to take a break myself - I wouldn't need this. Now I know - I can override this anytime - what’s the point - it’s completely useless Cinaroot (talk) 00:45, 17 May 2025 (UTC)
- It may be completely useless for you, now that you know that. But at least for me the need to take unusual actions (disabling JS, setting your time, etc.) to step out of the logjam discouraged me in the past. And of course, even if the JS were perfect, it couldn't possibly stop you from creating a new account. There are stronger tools available, like Category:Wikipedia administrators willing to consider placing self-requested blocks. * Pppery * it has begun... 03:46, 17 May 2025 (UTC)
- Well - this is supposed to be a enforced break. Sometimes we need it to stop addiction or remove ourselves from conflict etc... If I was able to take a break myself - I wouldn't need this. Now I know - I can override this anytime - what’s the point - it’s completely useless Cinaroot (talk) 00:45, 17 May 2025 (UTC)
Protected edit request on 16 May 2025
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
I made a page that tells you how to save yourself if you mess up using the script (here) add a mention of it? loserhead (talk) 15:38, 16 May 2025 (UTC)
Not done No, that defeats the entire point. We shouldn't mention this, and interface admins IMO should not be granting requests that do end up their way. (To be clear, this is my personal opinion, and not a consensus of the interface admin team). * Pppery * it has begun... 18:48, 16 May 2025 (UTC)
- Expanding on this, I have used WikiBreak enforcers several times. I found they lost their effectiveness in large part because I figured out from first principles how to disable JavaScript. The point of this process is to attempt to bind your future self, not to pretend-bind your future self with something you knew from the beginning was a facade. The current system of telling you to grovel before the interface admins (okay, I'm embellishing the tale a bit ... ) works well enough as a failsafe (although I would like it even more if people were actually bound), but telling everyone how to push the magic buttons IMO won't. * Pppery * it has begun... 18:53, 16 May 2025 (UTC)
- @Pppery I made that page as a failsafe of sorts if you were to mess up the date and couldn't get back in until the heat death of the universe or something but now reading your reply I shouldn't have made the page... I've tagged it under CSD U1 loserhead (talk) 13:56, 19 May 2025 (UTC)
- in previous thread - iv exposed if you change time on your device - you can get around the enforcement. Cinaroot (talk) 00:47, 17 May 2025 (UTC)
- Yes, of course, there are ways around it, and that's inevitable. But we shouldn't go out of our way to broadcast that fact, in part for reasons you explained in the previous section * Pppery * it has begun... 03:46, 17 May 2025 (UTC)
- Expanding on this, I have used WikiBreak enforcers several times. I found they lost their effectiveness in large part because I figured out from first principles how to disable JavaScript. The point of this process is to attempt to bind your future self, not to pretend-bind your future self with something you knew from the beginning was a facade. The current system of telling you to grovel before the interface admins (okay, I'm embellishing the tale a bit ... ) works well enough as a failsafe (although I would like it even more if people were actually bound), but telling everyone how to push the magic buttons IMO won't. * Pppery * it has begun... 18:53, 16 May 2025 (UTC)
Change script to use mediawiki server time - instead of local time
[edit]![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
The issue with current script is that - it uses device local time for enforced break time. this logic is obviously flawed - as user can just change device time to get around the WikiBreak
I have written a script - that will use wikipedia sever time , instead of local time
Please see it here User:Zcricket01/common.js Zcricket01 (talk) 04:58, 17 May 2025 (UTC)
Done (well, I didn't do the UI changes, but I did the meet of it). Sorry, everyone, now the beans have been spilt ... * Pppery * it has begun... 19:59, 18 May 2025 (UTC)