Simple CIA converter requires an existing .3ds file, this one downloads straight off the eshop. They perform different functions, and one isn't "better" than the other.And this is why simple CIA is helluva allot better.
Simple CIA converter requires an existing .3ds file, this one downloads straight off the eshop. They perform different functions, and one isn't "better" than the other.And this is why simple CIA is helluva allot better.
Simple CIA converter requires an existing .3ds file, this one downloads straight off the eshop. They perform different functions, and one isn't "better" than the other.
heh, helluva alot better eh? Well, as Plailect said above, it isn't really the same thing, so apples to oranges really... however, assuming that they did perform similar actions, let's take a look at some other aspects, so sure simple CIA converter is easy to use, BUT it is old. Plain and simple. This may get "old" but it won't ever be in the state Simple CIA Converter is in, why? Simple, it's "open source" (quotes because it isn't licensed). Anyone can fix up an old script with minimal effort, whereas we'd have to disassemble the simple CIA converter, convert the assembly back into some language like C (or if you'd really like to deal with the ASM then go for it) then once all of that work is done, make changes and recompile... it simply isn't worth the effort. Not to mention that there's a lot of things that Riku's tool doesn't do properly, so while it might produce "Valid" results that work on your console, they will never be clean results without a lot of work, and Riku isn't interested in releasing his work anyways... anyways rant aside, enjoy the inferior, closed source tools, which have a different purpose than thisAnd this is why simple CIA is helluva allot better.
3ds simple cia converter is more used if you want to make your cart into a cia, while plaicdn/funkycia are used more if you bought it from eshop and already is an installled title.heh, helluva alot better eh? Well, as Plailect said above, it isn't really the same thing, so apples to oranges really... however, assuming that they did perform similar actions, let's take a look at some other aspects, so sure simple CIA converter is easy to use, BUT it is old. Plain and simple. This may get "old" but it won't ever be in the state Simple CIA Converter is in, why? Simple, it's "open source" (quotes because it isn't licensed). Anyone can fix up an old script with minimal effort, whereas we'd have to disassemble the simple CIA converter, convert the assembly back into some language like C (or if you'd really like to deal with the ASM then go for it) then once all of that work is done, make changes and recompile... it simply isn't worth the effort. Not to mention that there's a lot of things that Riku's tool doesn't do properly, so while it might produce "Valid" results that work on your console, they will never be clean results without a lot of work, and Riku isn't interested in releasing his work anyways... anyways rant aside, enjoy the inferior, closed source tools, which have a different purpose than this![]()
really? I didn't know that /sarcasm3ds simple cia converter is more used if you want to make your cart into a cia, while plaicdn/funkycia are used more if you bought it from eshop and already is an installled title.
I think your missing the point you can use anyone's Titlekey3ds simple cia converter is more used if you want to make your cart into a cia, while plaicdn/funkycia are used more if you bought it from eshop and already is an installled title.
"According to git" is not a license and is a completely bullshit point (said every Software Engineer ever). I could send you a DMCA take down notice if you want to be technical as I never attributed a license (I should probably GPL it eventually). Removing a dependency is not a "major change" and would have been a perfectly acceptable pull request. Also, slapping your name on a forked project (or any project really *looks at countless other unoriginal CFW projects*) is just greasy. Do you see me slapping my name on any tools I release? No, because I shouldn't have to! People should know it's your project because you wrote it, not because you forked another project and put your name on it *looks at countless other unoriginal CFW projects again*. You know what SALTs project is called? firmloader because it describes the exact functionality of the program. *sigh* I guess we will always have the problem of some kid forking bitcoin to create his own altcoin or linux to create his own distro with his name on it, but that is fucking lame (also those projects are under a copyleft license unlike mine).
Do you know what bothers me the most? You didn't even bother to submit a pull request after releasing. This is NOT how you do open source (which again, my code isn't). This is how open source dies when there are a hundred billion forks of the exact same project with updates!
sure, in fact you need hax to run the resulting games because they will be unlegit always, this cannot create legit content.most likely gonna be used for piracy
sure, in fact you need hax to run the resulting games because they will be unlegit always, this cannot create legit content.
stuff like FunkyCIA, GroovyCIA etc... they can create legit stuff, and personal legit cias, which if they were able to be installed... (lol - no idea why they can't i wish someone would patch that in a cfw) - we have have legit backups of our own games playable without hax (once installed)
you misunderstand me, i'm not sure what part though sorryUnless you know of a way to get the keys Nintendo uses to sign games.
you misunderstand me, i'm not sure what part though sorry
GroovyCIA should have the same functionality as FunkyCIA, at least it should.My bad I thought you said FunkyCIA, GroovyCIA can't install legit cia's.
Groovy CIA does have the same functionality as Funkycia. It is literally just a graphical interface for it with a few extra features.GroovyCIA should have the same functionality as FunkyCIA, at least it should.
they don't 'install' cias, just tools for making them.
what i meant above, it is possible to leave all the data and signatures intact untouched. so, the cia would be legit for the console - not shareable legit.
but these cias do not install... we always get an error.
once we blank out the console id in the ticket, the cia magically installs... annoyingsurely patchable i guess... but i don't have the skills
Sure, the explanation for the little code was me covering my ass since Relys started throwing around legal threats. I'd be happy to include a large notice if the standard github "forked" link isn't enough.I would just like to say that I'm the original writer of the script you forked for this. I never attached a license to my release, nor did I release it to the public domain. That means I technically retain all rights as to how the code should be used, and whether or not to allow it to be reproduced or modified. You can claim that very little of the original code remains in your fork, but it's still a fork of my script.
Now, I will say I'm not that upset over this, though. But I would like it to be made more clear that this is a fork. I think a small notice in the original post and the readme would be sufficient.
![]()
if its not on the eshop its not on the eshop, this cannot just pull games out of thin air, so no unless the game is stored on nintendo's server then there is no way to get it short of adding support for privately uploaded files to random hosts which imho is way beyond the scope of a app such as this, go visit your local neighborhood isosite for publicly uploaded filesSince this only has support for the eshop, what are the chances PlaiCDn will have support for game carts in the future?
Edit: More newer games get released on the game cart instead of the eshop (unless you pre ordered the digital version of a game)
It lists my installed 00040000 titles along with their title keys. The checkbin command now seems to be functioning as it should. @Plailect Now I'm experiencing an issue running the .py version while the .exe version works fine. I know I have Python 3.5.1 installed, yet I continue to receive the syntax error.Script has been updated, try again with new version.
C:\Users\...\Desktop\PlaiCDN-master>PlaiCDN.py
File "C:\Users\...\Desktop\PlaiCDN-master\PlaiCDN.py", line 333
print('Checking Hash: ' + format(float(fh.tell()*100)/fhSize,'.1f') + '% done\r', end=' ')
^
SyntaxError: invalid syntax
C:\Users\...\Desktop\PlaiCDN-master>
Most of the differences in that diff is you switching from tabs to spaces. This is the real diff, notice how there's very little actually added, this whole thing could have been a Pull Request titled "Added Python 3 Support, TitleKey validation and Better Cross-Platform support". Also you tried to prove your point using a tool again, tools aren't absolute.I took a good look at "your" code in more detail, only to discover that your DMCA claim is bullshit since most of what you actually wrote (28 lines of which you got from StackOverflow) in the original project isn't even close to the same as mine.
I put in some PRs so I guess that makes 2/6. My personal issue with your project is that literally the whole thing could have just been a pull request. The changes are nice but rather than doing what anyone else would have done and actually contribute back, you were selfish and forked a repo, stamped your name on it and made a whole thread dedicated to it for attention.The rest of the code (which wasn't written by you) was added by pull requests, which is what an open source project has (even though you seem to have a different idea of open source than most).
My script uses either none or essentially none of that original code, so unless each of the people who pull requested to "your" (apparently not open source but still open source) project also agree that I'm committing some kind of atrocity and want to pursue legal action, your claims are completely irrelevant and downright offensive.
Hate me and get as salty as you want about it, but forking hurts open source project more than it helps, especially when changes don't turn up in the original project. And I could say the same about you, you only want all the advantages of using his and other's work with the advantage of having your name distastefully slapped on it.Do you know what bothers me the most?
It's the fact that you seem to want all the advantages of using others' work and open source, but also want the closed source advantage of DMCA (which thankfully is irrelevant since you didn't write any of the code this uses).