rmenessec / Steam DRM Highlighter Revenant

If s/he comes forward and asks me to take this down, I will of course do so

That would be indeed the situation if needed.

Since I am not the original author, I can't specify a license;

Not exactly true... the default arbitration is off your fork of it... however...

if I could, I would license it under the Creative Commons CC0 license.

Please read http://opensource.org/faq#cc-zero and https://openuserjs.org/about/Terms-of-Service#acceptable-licensing. If you did/do decide to license your fork with this particular license your script and your account may be eligible for removal.

In summary... we appreciate the explanation... however trying to prove that it came from a specific author may be nearly impossible without some further validated information. You probably should put a link to the USO mirror page from where this came from for additional attribution.

Re: @Marti:
It's been a long time since I installed the original script, but I believe this is what I used originally, and have since modified for my own use.

As mentioned, I was unable to contact the original author. I posted the modified version only so that others could benefit from additional DRM terminology highlighting I've added.

No license of any kind was specified by the author originally. If you believe that it's acceptable for me to continue posting my modifications, the MIT license looks closest to CC0 and is OSI-approved.

How would you like me to proceed?

PS: I didn't receive a notification from your post. How can I ensure that I receive notifications? I'm logged in via OATH.

How would you like me to proceed?

You are arbitrated at MIT already because you didn't pick a @license but you may want to announce it yourself with the @license key in the UserScript metadata block. Other than that you are doing it perfectly. We favor FOSS with strong attribution when it's a derivative and you've done it very well with what you believe was the link to the USO mirror. Proactive good faith efforts always help when there might be a conflict with a Script Author in the future... I think you will be fine.

I didn't receive a notification from your post.

That feature doesn't exist yet... some node and our dependencies issues are stalling us from implementing this at this time... other higher priorities right now... but we're working on it one step at a time.

How can I ensure that I receive notifications?

I use https://openuserjs.org/issues and look for my username in the Category column. There is at least one Userscript that may help you filter things out in the interim.

Re: @Marti:
Thanks for the update. Are there RSS/Atom feeds lurking anywhere that I could use?

Failing that, I know there are a few "web site to RSS" services out there; I've used Feed43 in the past with mixed results. Any suggestions there?

Thanks again!

Re: @rmenessec:

Are there RSS/Atom feeds

Not yet. I'm in the same boat as everyone else right now... development link is below on every page... I haven't had time to look for feed dependencies due to other issues as my role in development... but there is an issue open for notifications and other tracking methods. Extreme long term patience is requested. :)

"web site to RSS" services out there;

Didn't know those existed... add another thing to the mile long TODO list to check out. ;) Thank you.

It's definitely not intended for mass use, but this might help you in the short term:

https://feed43.com/ (self-signed cert)

If you can provide a slightly less public way to contact you, you're welcome to the "edit" link for the custom feed I just created, so you can use it as an example. (It should track all new issues with this script.)

feedyes.com was looking promising until it failed to detect the second issue in the list. I may try it again later - I'd rather not have to write even very simple "code" to generate RSS feeds this trivial. You can find a few other sites like Feed43 / feedyes.com via https://alternativeto.net/

It is your page to close the issue if you like... the general rule of thumb is you can reopen/close at your leisure... the creator can always close (that would be me)... so I shall do that now.

I'll look into that RSS after some time... the issue I'm tackling now runs deep and only shows up with certain use cases and is difficult to track down.