RELEASE Awoo Installer - A No-Bullshit NSP/NSZ/XCI/XCZ Installer Based on Tinfoil

Oh shi.. I'm about to have serious talk with Huntereb then

Waaaait, what is this?

 

That isn't in the readme or any file in the repo. That is from the git history, which I flattened. Distributing the source code outside of git removes that. The license compels distribution of source code, not git metadata. Nothing was stolen, you just aren't happy that the repo was flattened I guess?

edit: to be clear, awoo didnt put you in the contributors section, github did via git history. clearing git history, removed that.

 

It's a part of repo since commits are part of repo with history. It's just an automation of giving credits provided by GitHub. Please don't tell me that you didn't know that. BTW readme file is not a part of source code as well but somehow you paid attention on what is written in there.

If I'm happy on unhappy doesn't make sense, I'm personally good with this.
Just curious. What was your motivation? Why did you copy-pasted it instead of clicking 'fork' button? Who are eligible to be a part of tinleaf team?

 

You are very confused. Open source licenses require distribution of source, not the git history itself. I did not do a proper fork because a) I do not have to, to comply with the licenses b) I do not want any links on my github to a furry meme repo. c) I do not want any of awoo's history in the repo because its full of cancer. The purpose of the project was a clean break from Awoo, which means wiping the history.

 

You're the one who don't understand Open Source project licensing. This project is licensed under the GPLv3 license, which requires credits, states and document every changes made to the original source code and to use the same license (Which you are not, btw, since you are using Ms-PL) if any part of the source code is used.

 

This project is not licensed under GPL3. 99% of it is MIT. The 1% awoo actually wrote is GPL, and then the bits I added are MS-PL. Mixing these licenses is fine as long as the source is distributed in compliance with GPL.

GPLv3 does not require crediting people in the way you are claiming.

 

blawar is right - tinleaf does not violate any part of license.

 

Yeah, after you last reply I looked in your repo and now I really confused.
So, let's walk thru it one more time with more details: I contributed to GPLv3 project on GPLv3 terms. Somehow results of my work appears on your application that is now uses incompatible with GPLv3 'Microsoft Public License (Ms-PL)', doesn't include any reference to original authors.
That's what I call 'clearly stolen'. You literally took a part that is GPLv3 and instead of throwing it away as a fruit of a poisoned tree you're trying to prove that it's legal. Sounds a bit weird to me =)

Anyway, want to users be informed. And as I said I'm fine with it as long as Hubntereb/Behemoth are fine with it.

 

I recommend that you do some more research on how open source licenses work, and I do not mean that in a snarky way. Especially how mixing licenses works. Licenses are legal contracts, and they can be very nuanced. To your credit, few people truly understand them.

Free software is free software, not software that is only free if it is used in a way you agree with.

 

I did some research and can't figure out how did you move license from GPLv3 to MS-PL %)
IDK, maybe this would help: https://www.gnu.org/licenses/license-list.en.html#ms-pl
Please don't think that you have right to do with GPLv3 code the same things that people do wit MIT or BSD ones. It's different

 

You are confused, I did not relicense GPL code to MS-PL. I wrote a library in MS-PL. All modifications I made to awoo's code is indeed still GPLv3. The library code I added is MS-PL. Library code is not required to be compatible, as GPL allows you to link to non-free libraries.

 

Aaah, so you removed all the notices about GPLv3 from there before making changes, didn't add any references to the original project, authors, licenses and added a license to your library in the root of the project to make GitHub think that the entire project is under MS-PL while it's not.
Yes, makes sense.

 

I just came here to give the routinely

"Need another Awooooo version for FW 11 USB compatibility"

owo

And yes: I refuse to use another installer.
Awoo rocks.

 

All code I write is under MS-PL. The real scandal there was awoo making github think it was a GPL project, when 99% of the code was MIT. Truth be told, it's really a MIT project.

However, you did point out one thing that was correct: I had forgot to add the Awoo GPLv3 license. That was an oversight and not intentional, and I have just added it to the repo. Thank you for pointing it out. And that is all the attribution that I am required to give.

 

Even having different point of view I'm glad we made these things clear.

 

That said, feel free to submit a PR that adds a translation credits file, or some sort of comment somewhere in the code that you feel adequately credits your work. My goal here was not to discredit or offend you. I just do not want any of awoo's history in the repo.

 

Will come to you once make something interesting to PR =)
Anyway, I appreciate it.

 

Actually you had that there all along but accidentally overwrote the LICENSE file a week ago: https://github.com/blawar/tinleaf/commit/82f62f610f87a68b3332a31ad3a7bbc89a851f07

 

Hi, I know this is an old thread but I was wondering, how did you measure the speed?. I was using Goldbricks and Nut, mainly because Goldbricks allowed NSZ, but I move to Awoo mainly because you can send a bunch of files and install them in batch, while in Goldbricks you have to select them one by one. The problem is that I feel Awoo is way, WAY more slower than Goldbricks / Nut (USB).

Any way to improve speed?

Oh and by the way... Did you really hand draw your avatar? XD

 

Awoo Installer 1.3.4 is out !!!
https://github.com/Huntereb/Awoo-Installer/releases

• 11.0.0+ USB support
• NS-USBloader network-stopper feature (Thanks @developersu)
• add Spanish translation (Thanks @PabloPerezRodriguez)
• fix XCI installation if card was inserted prior (Thanks @ITotalJustice)
• fix potential handle leak on various errors
• various small language fixes
• Updated signature patches for Hekate + Atmosphere on 11.0.1