Are you sure you want to go to an external site to donate a monetary value?
WARNING: Some countries laws may supersede the payment processors policy such as the GDPR and PayPal. While it is highly appreciated to donate, please check with your countries privacy and identity laws regarding privacy of information first. Use at your utmost discretion.
@TrickyFoxy
Please reread the section of the TOS you agreed to here.
OUJS Admin
Re: @gregorzalda:
There's no trackable evidence that the "Bobber" account is yours. Unfortunately if you messed up the authentication on your end, which is what you are implying, there is nothing we can do. You may consider it orphaned.
OUJS Admin
Re: @f9y4ng:
Usually I would refer to this FAQ for recommended reading (and still do) however they seem to have not supported private properties for classes yet.
You have to wait for it to be supported by them or go issue check them.
OUJS Admin
Re: @gregorzalda:
No but you've been truncated. I appreciate the honesty and this is the final change for this account.
OUJS Admin
Re: @MoonDivision:
That would be against the Terms of Service. Please reread the link at the bottom of every page. You accepted this when you signed up. Please also reread the About link at the bottom of every page as well.
This is FOSS site (and it's quite obvious that everyone can fork everyone's code) not a no-derivative OSS site and has been discussed in full length on development. This will not change. If you feel you can't meet these guidelines then remove your scripts i.e. it's your decision.
Your account will remain flagged and if it happens again on this FOSS site your account will be immediately eligible for removal. We technically didn't have to give you the notice.
Thank you for your cooperation.
OUJS Admin
Re: (current code location):
Attribution-NoDerivatives 4.0 International =======================================================================
You can't do this in your published code on OUJS. It is in conflict with your current
@license
ing in the UserScript metadata block and is against the Terms of Service.You have an extremely short time to remedy this before the account and script are eligible for removal.
OUJS Admin
I'd like to give some warning about a notified, scheduled, VPS maintenance.
From the 17th to the 18th of June 2024 things may be limited or not working correctly during the process at various times. Try back again later if you encounter an issue.
We appreciate your patient with our host provider.
OUJS Admin
Re: @KNAPKT:
No that's not true. You were also warned and didn't heed the warning.
However... Congratulations you are the very last person that will be able to ask this on a newer account.
OUJS Admin
Re: @sjehuda:
If I were a new user and saw your version vs the other accounts version... I'd say... hmmm yours seems to look newer so try yours...
In a plain, blunt, evaluation... your scripts
@version
is 2.6 and your source mentions 2.7 ... and the transferred is at 2.1 ... i.e. it was poorly maintained by both accounts. If I were to use it, I would see that and down vote both scripts for lack of consistency.OUJS Admin
Re: @sjehuda:
I've already commented on this above. What you do with informing your users is yours to address.
I've also discovered that my distro's snap is seriously out of date for Falkon. Using the flatpak now which includes the GreaseMonkey extension. Updated our target Falkon about page to reflect this. Yes your script works on Falkon 24.02.1 here.
OUJS Admin
Re: @sjehuda:
Under https://openuserjs.org/scripts/sjehuda/Flash_Player_(ruffle)#enable-support-for-flash-files you should put something like you just wrote with the "every page" addition to number 1:
Nicely done on part 3 btw.
You should also put an example test url (which you provided above) but on the main page of the script saying something like "Try it at ...".
If you let the user what is going to happen and what to do to test it then I can clear the flag and this will be relisted.
Please remember that you are the Author and they may not fully know much about JavaScript so in plain language lay out what your script does. If they do know JavaScript they could be ready to evaluate the script as well after trying to get it to work... but if someone doesn't know what it does (a starting point) then they'll just skip you or down vote because it won't work for them since you didn't provide a "Unit Test" URL.
OUJS Admin
P.S. It works for me under current Firefox with the example URL. I still have the issue of my distro's Falkon being too old compared to yours and snap (with the newer one) doesn't include GreaseMonkey (i.e. they crippled it). So testing in Falkon probably won't occur for me.
Misc note: You are welcome to use instead of the eagle Unicode character (use
width
andheight
attribute on a htmlimg
tag to do this). This is a permanent member of our GH CDN of images because of the about page we provide for Falkon.OUJS Admin
Re: @sjehuda:
All that is currently available is Open Discussion notices ... Log in... go to your https://openuserjs.org/users/sjehuda/scripts and look for the orange comment bubble with ellipsis and a number to check.
Other notifications haven't been developed/contributed by anyone (and you know this already because you created the RSS feed one which is over on Development).
Everything is public here usually. Please remember that some things not everyone wants to see. If they do then there is https://openuserjs.org/all discussions. Choose wisely including on your "Merge"... this issues. I'm interpreting those as one of your personal TODO list issues... if you asked us to do it we would probably say "no" (or possibly ignore it) just like the unlisting request. Self sufficiency with the tools available.
OUJS Admin
Re: @sjehuda:
As I have previously mentioned unlisting may happen when Flagged. This is not a Author owner choice. All scripts are public unless there is an ongoing issue and the system decides to unlist it. If it hits the Admin+ TODO list then it usually gets addressed, sometimes with permanent removal.
I also mentioned elsewhere that self sufficiency is the goal with the available tools. So no... you are capable of deleting your script if you choose that path. If you leave it on here you are asking for people to give it peer review i.e. rate it or flag it. That's how publishing works. If someone tries it and it doesn't work they are well within their rights to down vote it. Flagging would be a bit much though unless it was doing something that you didn't divulge it was supposed to do in the Script Edit Info page and
@description
.OUJS Admin
Re: @sjehuda:
No you may not. If it doesn't work keep it locally. The only way to clear the Flag is to either fix it, or delete it and you may reupload when it does work... else we'll remove it, usually permanently. Your https://openuserjs.org/garage/Help_making_ruffle_to_work should be sufficient to reference what you need back when you do figure it out. Because you are in the proverbial basket right before the chopping block and I'm the executioner of it... if I don't feel that you are responding in a timely manner I'll take the necessary action. As I mentioned before you've been given extra opportunity to correct this.
That would be a nice addition to the "Edit Script Info" page as well as a
@match
provided it's going to be around for a long time.@require
since it appears to be duplicate code from when I started this issue? i.e. manually inject but not twice.@run-at
¹ ² ³ but can be affected by other engines such as Tampermonkey using@sandbox
but I previously mentioned controlling it forced for possible better global compatibility.setTimeout
to check at last case analysis... but usually preferred is some MutationObserver.OUJS Admin
You still are:
... and you are still:
with the remaining
@require
.I'm giving you time because you are asking.
I'm going to spell it out for you.
@description
when finished and also with saying how, exactly, to use this with your "Edit script info" page.@match
and/or@include
instead of every web page.OUJS Admin
Several things.
Again I am not going to address the (possible) solution here but in the discussion I created earlier.
OUJS Admin
Moving discussion
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.
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:
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 save it is what I guess you mean. If so yes.
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.
Please don't tell people personal information in public venues. Not a wise idea. Edited your post.
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.
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:
There used to be one of that name.
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.
details
orsummary
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.summary { display: list-item; }
and any other relevant CSS modification for bootstrap.<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