Skip to content
TORNLIFE More

Tampermonkey update

Started by Hawk [2080065] on in Tools & Userscripts.

19 replies · 838 views · thread synced · 18 days ago · View on torn.com
About this thread

Posts archived: 20 / 20 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
20
Discussion span
→
People posting
12
Likes on archived posts
22
Posts by staff, officers and moderators
2
Authority score
57 / 100
Historical score
33 / 100
Story score
45 / 100
Engagement score
65 / 100

Most-liked replies

  • DeKleineKobini [2114440] Committee · 8 likes ·
    Developer mode is specifically for extensions and can be toggled on chrome://extensions. They don't really mention what they are talking about, but as an extension developer myself I recon that they are talking about Chrome's MV3 which will heavily restrict …
  • DeKleineKobini [2114440] Committee · 2 likes ·
    Firefox will still keep MV2 support, and does not do everything that Chrome does with MV3. This means that things might keep working, but it will depend on the tool as they might have to support 2 codebases which not …
  • WhackedMaki [2587660] · 1 likes ·
    I've got my developer mode turned on in Kiwi Browser, but it still isn't working.
Hawk [2080065] · #1 · edited

UPDATE

For TamperMonkey scripts, Chrome is requiring dev mode be turned on now.

 

If your scripts aren't working on Chrome, click the TamperMonkey extension and it'll tell you how to flip the switch

 

 

*This is what they announced they would do 8 months ago (the beginning of this thread)

DeKleineKobini [2114440] Committee Committee · #3
Developer mode is specifically for extensions and can be toggled on chrome://extensions.

They don't really mention what they are talking about, but as an extension developer myself I recon that they are talking about Chrome's MV3 which will heavily restrict ad-blockers, and apparently also userscript managers. Timeline wise they'll probably be forced to move to MV3 by June 2024 (as all extensions will, including TornTools which is also still on MV2) and be impacted by heavy restrictions. If I'm right about the reason why it will be a problem, then all extensions like this will be affected heavily like this and moving to ViolentMonkey won't solve that except maybe change the timeline a bit although I'd think that they all will wait until the last possible moment to switch to MV3.
Shaitan [2802630] · #4
Thanks DKK that clears it up a bit, so this won't affect me as I'm using Firefox, ie it's specific to Chrome based browsers?
DeKleineKobini [2114440] Committee Committee · #6
Firefox will still keep MV2 support, and does not do everything that Chrome does with MV3. This means that things might keep working, but it will depend on the tool as they might have to support 2 codebases which not everyone will want to.
Alfonzie [2730058] · #10

Now having issues using kiwi browser and unable to toggle on developer mode within extensions.

On mobile.

 

Any advice?

 

Anyone else come into problems today or recently.

No scripts working 

Alfonzie [2730058] · #13

I was unable to.

 

So I've had to switch over to using torn PDA.

With a non browser(app interface)

all my scripts work fine here.

 

And after some PDA tweeks it's running near perfect to my kiwi browser

Looney [3011616] · #15

I got rid of Kiwi and went to Firefox, having Firefox issues now 👎🏻 some scripts aren't even working on TornPDA.

Hawk [2080065] · #17 · edited

For TamperMonkey scripts, Chrome is requiring dev mode be turned on now.

 

If your scripts aren't working on Chrome, click the TamperMonkey extension and it'll tell you how to flip the switch

 

 

*This is what they announced they would do 8 months ago (the beginning of this thread)