Update LICENSE

[ImprovedTube]

No description provided.

[raszpl]

Afaik old project was on GPL 3, once something is GPL 3 it cant be changed into more restrictive license ergo its still gpl 3

No, thats not it, now I remember
all accepted pull-requests are assumed, to come under a viral copyleft license, GNU agpl-3.0-7abcdef
agpl-3 is viral, any agpl3 code shipped means whole project must be agpl-3
https://opensource.google/documentation/reference/using/agpl-policy#:~:text=This%20viral%20effect%20requires%20that,or%20service%20is%20actually%20distributed.

[ImprovedTube]

hi :) 🤗 you might want to read / catch up here code-charity/youtube#2421 and other @mentiones

Isn't it wonderful (mentally & and for the users), to have a project where at least 2 people have thought about 100s or 1000s of issues?

RE: License: The first line indicates copyrights.

©️ 2012-2024 ( no warranty / liablity ) Thank you!

(Then why quote halves of sentences?)

For simplicity & intellectual growth: Unless stated otherwise, ... And free of copyrights to the original maintainers. (these intellectual contributions are granted to the original maintainers free-of-charge, non-exclusively, for publishing & modification. Contributors do have the right to be mentioned in credits)

( In other words: External pull requests are assumed to be under a viral free license considering the rest of the world (as it is a common standard), but also with a normal (non-viral) permission (only to the original maintainers)(, so that and the original project can simply run as always / as the first 9 years when few pull requests were merged.) )

• More interestingly, you might also read the draft for a new type of license acknowledging developers as shareholders (which they mentally are either way. Something that existing licenses are missing. Greetings @Maniues)
• While you were essential for the Project in 2024 💕.

[ImprovedTube]

(As said) i have a lot of understanding for your exhaustion(?)

i was utterly amazed and so relieved you were working a lot these month! And regret i was unable unexpectedly to work here in June.

[ImprovedTube]

unsure how and why to practice categorical /competitive misunderstandings.
(To belittle ourselves and our project? )

code-charity/youtube#2287 (comment) :

if anything code-charity/youtube@912b34d broke it and NOW with this patch hyperlinks will have no color :)

...No.
You already did so much! (Did that also make you any less-willing to "admit" tiny/every-day blunders? /The more effort you pay, the more "silly" i must be? i usually mean to apply the courtesy /professional-distance to comment rather positively and ignore confusing impulses (among other since we represent a popular app in public. Feel free to use email to or any)

---

a defector

That was only about the tiny screenshot? Or you didn't feel like a good team?

this is NOT vivaldi bug

NO, chrome documentation did most-likely not refer to something only Vivaldi has & only 1 in 2000 browser users has
( i had told about the fun to run a project used by 0.0x% of youtube users & care for bugs unique to a browser used by 0.0x% browser users? I am not sure how this was enough for an angry troll to come up, and even change your perception of truth?)

(Yes, the chrome documentation has a headline of some paragraph - when quoting badly isolated and we can speculatively assume Vivaldi misunderstood that - or can just regret the lack of a public bug tracker. I appreciated Vivaldi for productivity (and i'm not sure why it is such an emotional thing to some, about doing one's own thing despite of frustration?)

---

...

---

Glad about your work!
Hope you are fine!