Marti Admin

This script is incredibly vague and includes/matches too widely. Secondly the external host is at a tipping point for obfuscation. It's interesting that some are trying to get Flash back but inappropriate to inject everywhere and yet do nothing.

This is your 2nd strike btw... more than most people get.

Please fix the script so it doesn't get flagged again and you will be removed for TOS violations.

OUJS Admin


You should be swapped now. Please login using the original user name at your convenience.

OUJS Admin


I usually wouldn't respond to this sort of rant because there is no actual question presented here yet... but...

I found two breadcrumbs, that if you prove the account is yours, then I can swap the authorizations.

  1. If you can demonstrate that you have delete control of one of your images from imgur from this script that would be a positive affirmation.
  2. Temporarily change your profile description or add some sort of comment (with your usernames here and my username) over there with GF that is referenced at this script that would also be a positive affirmation.

You will need to let me know here when to look and wait for me to respond. Otherwise fork your own scripts.

As far as your rant goes... go blame E.M. for that, not us. Reminder of etiquette please.

OUJS Admin


Re:

Validation has to occur starting here on OUJS and if you can't do that then unfortunately it's orphaned.

OUJS Admin


Re:

If you can prove that you have some mastery of that old account... say by deleting the imgur picture that is included on that script on imgur (don't forget to save it for when you get restored on proving success) which will reflect on the scripts homepage here... then I can merge your new account auth into the old one.

You will need to let me know here to check back on it. This appears to be your only option btw from a scan of the other account. If you are unable to do this then the account is probably orphaned and you'll be left with forking the script to the new account.

OUJS Admin


Re: @kevinpan.cs12:

I failed to receive that notification due to reasons unknown.
...
I really have no idea what's identified as obfuscation, too.

Search my Comments under my account around mid July for the old username... and you'll see the reason here and the linkage back to where GH account was clearly notified. OUJS notifications one just has to pay attention atm but GH has email notifications and unread notifications for those. So there were clear notifications... again not required.

too late to say it, right?

Too late to save it is what I guess you mean. If so yes.

Is it possible to recreate an account with that username?

Probably but mitigation will include observance of the prior account activities under the same handle i.e. since there was a strike on the username it could affect a future mitigation of flags raised.

composition of ...

Please don't tell people personal information in public venues. Not a wise idea. Edited your post.

Can I reuse the old authentication way in my other new accounts?

I seem to recall that the specific authentication associated with the account is permanently banned but seem to recall username is not. No there won't be an exception made.

I'm afraid of getting banned again by reusing it.

That's what I said earlier here in this reply. It won't be in anyone's favor if things were previously flagged... however it will be investigated appropriately.

Long story short the account holder gets to start over from scratch due to the obfuscation.

OUJS Admin


Re: @kevinpan.cs12:

I used to have an account named kevin_pan_940506

There used to be one of that name.

I believe that I didn't violate any rules as far as I know.

Presuming that account was yours, yes that account holder did violate the TOS with Obfuscation. There were multiple attempts to contact that account holder (which technically aren't required with this type of TOS violation but completed none-the-less) and no response was returned within a reasonable period. The default action was applied.

OUJS Admin


Re: @sapioitgmail.com:

Better late than never here... apologies.

  1. The site doesn't allow details or summary HTML tags for user content. i.e. those tags are sanitized. This is unlikely to change but perhaps a discussion on Development would be considered... however it would need the establishing owners approval.
  2. If the site did allow them, then our theme needs some modification for showing the arrow with summary { display: list-item; } and any other relevant CSS modification for bootstrap.
  3. Also our current markdown parser would require it to be:
<details><summary>ReadM Manga Before</summary>

![ReadM Manga Before](https://i.imgur.com/5t198F5.png "ReadM Manga Before")

</details>

... with the line breaks... but again those specific tags aren't allowed.

This is really a Development type query for the future please.

OUJS Admin


Re: @Mottie:

We're going to try a work-around for this to force compatibility of markdown with sanitize-html dependency.

Sanitizing will always have a higher priority over html user-content but hope this methodology handles this for now.

OUJS Admin


Re: @pedro.souicloud.com:

The account was connected to a github account (which was deleted)

Unfortunate.

the site just logged me into my first account (this one).

Yes it will.

Can my access to that account be regained?

No because the GH account is no longer there. I can say with relative certainty that it's your addresses for both accounts but we can't verify that it's your identity.

can the script that I published there be deleted

No.

since I'm unable to update it?

Just fork it from yourself on OUJS using the Submit Code as Fork button at the bottom of that page.

OUJS Admin


Re: @Fask:

I deleted the imgur image that I had for the "TfT Main Page Remake"

That will allow me to swap your identities.

tried this, but unfortunately still received the "Authorization Fail" error.

You tried four times with Twitter and twice with Steam at your current address. The four gave you "Authorization Fail" and the two gave you "Strategy Fail" (assume it's because something was done on the Steam side). If you know what happened on Steam and if you can prevent it... please try not to let it happen again. :)

I don't know.

Alright was worth a try. Date would have had to have been exact if you did take a guess at the time of day.

Anyhow... you are flipped. So @Fask is the "orphan" of your old Steam keyed account and @Prios is your active Steam keyed account now. You were booted off your current session in order to achieve this seamlessly. As you know @Prios is not on probation so you may log in anytime. I dropped the DB's for that just in case you triggered it at your current address with the @Fask.

Since Twitter is probably defunct you may want to add another strategy.

If for some reason you have any additional issues regarding this please ping me on GitHub with an issue as no new accounts here on OUJS will be swapped for you... just these two.

Thank you for taking the time to answer the questions.

OUJS Admin


in the meantime you as Fask need to prove that the Steam account is yours by temporarily modifying your bio line on Steam and have me see it after you notify me here to go look.

Confirmed on Steam. You can change that back. Still need more time to ponder and I have to go do an IRL thing. I realize that your @Fask is a new account and you won't be able to reply for around 24 hours (Don't try to log in until after then otherwise it "rolls" and it'll restart the 24 hour countdown) due to probationary status. Find out what you can to answer the remaining questions.

OUJS Admin


Re: @Fask:

... Fingers crossed ...

Can you tell me the last date and approximate time here on OUJS that you logged in at for @Prios? (Do not guess as that will not be a good thing if you are not correct)

OUJS Admin


Re: @Fask:

Did you also try logging into Twitter first then here (manually selecting Twitter in the drop list)? Does it fail like my new account test?

... btw ensure you are logged out of all other authentication strategies (Steam) first during testing... or the site will nab that.

OUJS Admin


Re: @Fask:

... Fingers crossed ...

Did you save your imgur images to an album that you can delete one for OUJS access proof?

OUJS Admin


Re: @Fask:

Fingers crossed that that is enough.

I just updated and retested Steams auth strategy along with some other deps and the backend updates. Try it again. It was a little weird that I was logged in already and it asked me to login again. Anyhow I realize the @Fask account is also Steam so presumably you could/can/have create(d) a new account on Steam. You need to use your old Steam account though.

regardless of which authorization method I try

If you notice any superscript RO text, after the manually selected authentication method in the login page, on the ones you have that probably means it won't work. See also #1982.

As far as restoration I'm going to have to ponder that for a bit. But in the meantime you as Fask need to prove that the Steam account is yours by temporarily modifying your bio line on Steam and have me see it after you notify me here to go look.

I can't say for sure if you'll gain access to the OUJS account as anyone can upload a script with someones namespace... hence why the profile is always a preferred place to cross-identify yourself (It demonstrates that you had actual access to the account). I will need some time to scour the logs and that account.

OUJS Admin




Re: @ringofyre:

@gaspar_schot

This should clear the error in the script with bad @match syntax:

--- /scripts/gaspar_schot/Supercharged_Local_Directory_File_Browser/source@8.0.1+d0c9b4f
+++ /scripts/gaspar_schot/Supercharged_Local_Directory_File_Browser/source
@@ -10,7 +10,7 @@
 // @homepageURL    https://openuserjs.org/scripts/gaspar_schot/Supercharged_Local_Directory_File_Browser
 // @icon data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAIAAAACAAgMAAAC+UIlYAAAACVBMVEUmRcmZzP8zmf8pVcWPAAAAAXRSTlMAQObYZgAAAFBJREFUeF7tyqERwDAMBEE3mX5UiqDmqwwziTPHjG7xrmzrLFtRaApDIRiKQlMYCsFQFJrCUAiGotAU5hTA1WB4fhkMBsOJwWAwgHvB8CHpBcTbpxy4RZNvAAAAAElFTkSuQmCC
 // @match      file://*/*
-// @match      about:blank
+// @include      about:blank
 // @match       https://www.example.com/path/to/directory/*
 
 // @require https://cdn.jsdelivr.net/npm/markdown-it@13.0.1/dist/markdown-it.min.js

Greasemonkey Port 3.10.0.1rc5pre-sm.xpi is available now at the SF file repo.

This fixes an additional inconsistent compatibility issue introduced with SM 2.53.14 through 2.53.16 with the locale preventing management and general usage failure... some SM preferences were renamed/missing but not in all SM locales which is very odd and a Services method. em:minVersion remains the same i.e. SeaMonkey 2.40 or better.

REMINDER: My profile here says how to get in touch especially for compatibility fixes since I found this one floating about the inet. Always remember that SourceForge is the current OFFICIAL SOURCE for this original add-on.


Re: @sjehuda:

Is it possible to hide page from search and profile?

No.

Is it also possible to reset installs number? (5415)

No. If you are worried about increases for the future see https://openuserjs.org/about/Frequently-Asked-Questions#q-is-there-a-way-to-not-count-script-updates-with-this-sites-install-counter-

// @supportURL https://openuserjs.org/scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/source

That's not how that key works. Should be https://openuserjs.org/scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/issues

Please update your version to 2.7

Yes... both of you should version bump after you make all the necessary changes to trigger the .user.js engine manager to know that there is one.

OUJS Admin


Here's what I mean about the license header and keys in code:

--- /scripts/sjehuda/RSS+Atom_Feed_Subscribe_Button_Generator/source@2.1+6350c31
+++ /scripts/sjehuda/RSS+Atom_Feed_Subscribe_Button_Generator/source
@@ -11,10 +11,12 @@
 // @version     2.1
 // @date        2013-04-19
 // @icon        https://upload.wikimedia.org/wikipedia/en/thumb/4/43/Feed-icon.svg/128px-Feed-icon.svg.png
+// @downloadURL https://openuserjs.org/install/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.user.js
 // ==/UserScript==
 
 /*
- * Copyright (c) 2006-2013, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2006-2014, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2017-2023, Schimon Jehudah (http://schimon.i2p)
  *
  * Permission is hereby granted, free of charge, to any person
  * obtaining a copy of this software and associated documentation

... and ...

--- /scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/source@2.1+6350c31
+++ /scripts/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator/source
@@ -11,10 +11,14 @@
 // @version     2.1
 // @date        2013-04-19
 // @icon        https://upload.wikimedia.org/wikipedia/en/thumb/4/43/Feed-icon.svg/128px-Feed-icon.svg.png
+// @updateURL   https://openuserjs.org/meta/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.meta.js
+// @downloadURL https://openuserjs.org/install/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.user.js
 // ==/UserScript==
 
 /*
- * Copyright (c) 2006-2013, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2006-2014, Manpreet Singh [junkblocker@yahoo.com]
+ * Copyright (c) 2017-2023, Schimon Jehudah (http://schimon.i2p)
+ * Copyright (c) 2023, Manpreet Singh [junkblocker@yahoo.com]
  *
  * Permission is hereby granted, free of charge, to any person
  * obtaining a copy of this software and associated documentation

As far as the unsupported @date key that can be handled however both accounts see fit.


There is an inconsistency in the script source vs. what you did @sjehuda. Copyright year term is incorrect compared to original. That must remain the same as the USO source code page. Also the license header block has to remain forever in any publishing. It can be updated year wise of course to 2023 if it's the original author. Technically your name should also appear for the period that you managed your copy @sjehuda

Secondly... I've forked it (which you could have done @junkblocker and how I did it as you... you can always undo it and redo it yourself if you want the practice but I also copied the script info markdown) by going to sjehudas script Source Code page and clicked the Submit Code as Fork. This should be sufficient enough.

As far as your users @sjehuda you'll have to do your usual deprecation method (or something new) that we've talked about before. You can always create // @downloadURL https://openuserjs.org/install/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.user.js so that script updates you trigger load junkblockers on update... then the user will need to uninstall yours otherwise two copies will be present on their system.

And @junkblocker you would also ideally add that key in the UserScript metadata block but also the // @updateURL https://openuserjs.org/meta/junkblocker/RSS+Atom_Feed_Subscribe_Button_Generator.meta.js... so to keep the users from getting confused or their .user.js engine managers.

OUJS Admin


Greasemonkey Port 3.10.0.1rc4pre-sm.xpi is available now at the SF file repo.

This fixes an inconsistent compatibility issue introduced with SM 2.53.14 through 2.53.16 with the locale preventing management and general usage failure... some SM preferences were renamed/missing but not in all SM locales which is very odd. em:minVersion remains the same i.e. SeaMonkey 2.40 or better.


Re: @sjehuda:

SPAM!

  1. This is the Authors own issue... so within reason it's not spam as it was already pre-verified as doing exactly what it says vs the script source.
  2. You are spamming this script issue with your message... more precisely harassing. You are doing your best to test your ability to be eligible to be removed permanently.
  3. If you feel a user is spamming you flag the User with brief yet concise details.

Please don't test my patience any more. The subject of this intervention is closed here.

OUJS Admin