dluciv Author

  1. dluciv
  2. Everlasting Juick
  3. Issues
  4. Invalid Script License
dluciv Author

You've been relisted... double check please.

I was probably late to read this... But anyway, what did it mean exactly? =)

  1. dluciv
  2. Everlasting Juick
  3. Issues
  4. Invalid Script License
dluciv Author

Re: @Marti:

Thank you, glad to hear this, as things will remain simple =). So I notice different license on GitHub from where the asets come from and it will be enough.

  1. dluciv
  2. Everlasting Juick
  3. Issues
  4. Invalid Script License
dluciv Author

Re: @Marti:

No, I mean multiple licenses =). OpenUserJS shows them both, but I am still not 100% sure that all other code will handle them correctly. But there were no complains yet, anyway, so let it be as is (according to your suggestion).

And the last question. I do not mock. I have just realized that the picture I use is licensed CC:BY-NC-SA 4.0. It is a character of Russian visual novell, called Everlasting Summer (sorry, I saw no online translators which can handle it). And the script title itself is a cue, though the script itself is not related to the novell at all (it only adds "everlasting" scrolling to the site).

So please just tell me if it is no problem to show CC picture form GitHub shown on OpenUserJS, or I can change something again. Hope it does not matter because OpenUserJS only references the picture, but does not store or modify it, but I decided, that it is better to ask =).

  1. dluciv
  2. Everlasting Juick
  3. Issues
  4. Invalid Script License
dluciv Author

Re: @Marti:

It is ok. I have accepted it. Not 100% sure it is correctly parsed everywhere, but here, in GreaseMonkey, TamperMonkey and ViolentMonkey it does not break anything.

  1. dluciv
  2. Everlasting Juick
  3. Issues
  4. Invalid Script License
dluciv Author

Re: @Marti:

Marti, thank you. I have changed it to dual licensing (WTFPL + MIT), so it should fit here.

Btw if you get some time you can read up on the Tivo fiasco with GPL v2 versus v3 and you can see why GPL exists. It's on the web.

Sure, I will.

  1. dluciv
  2. Everlasting Juick
  3. Issues
  4. Invalid Script License
dluciv Author

Re: @Marti:

Marti, thank you.

Very sad that WTFPL is not OSI-approved. But I want to keep it as is if possible, as I really think users should be able to do what the fuck they want to with my dirty code.

Is there any reasonable way to leave GitHub project WTFPL-licensed and release everything there under MIT or BSD? Can userscript have multiple licenses? Or may be use one @license tag with both licenses?

Regards, Dmitry