Don't know about anyone else but I find it really irritating when the things I make get hosted on other people's sites with no credit surrounded by adverts, poorly written "tutorials" and requests for donations because of the thousands of hours put into the work. As far as I can tell those thousands of hours were put in by people other than the ones requesting donations.
I can agree with donations, and I can
definitely agree about some of the guides being poorly written. The first one (dsiguide.me) was quite poorly written, and upon initial release it was nothing but a giant placeholder with information about exploits that weren't even confirmed yet (like "dsibrowserhax"). Nowadays it's a page about manually editing a NAND backup and reflashing it with fwtool to install Unlaunch, then dumps you at dsi.cfw.guide (since its HiyaCFW instructions weren't great so they're just redirecting to that one now)
However, dsi.cfw.guide is a derivative of one of my older guides for the system, so I have push access to it. How do you propose we improve the guide?
There are some things I can't do as I don't own the cfw.guide domain, like removing adverts (emiyl has them there to pay for the domain), but I can absolutely make changes such as:
- Removing my donation link (I can't control emiyl's, though) because like I said I agree with that point
I can also remove the donation notices from the guide itself, and a disclaimer on the donate page that we didn't do much work besides put the guide itself together and that it's better to donate to the devs instead
- Crediting developers- we do have a few things like ugopwn repacked, but that's so things are "plug-and-play" and users just have to drop the files on their SD card. With the way Flipnote Lenny is packaged, this definitely wouldn't be necessary
We have some other things repacked that come with some .py files that do most of the grunt work of preparing HiyaCFW and grabbing a console ID from a DSiWare. I can separate these out if needed, some of them are residual from older versions of the guide anyways
I can also add developers of any software and exploits used to the credits page
If Flipnote Lenny was to be added to the guide, it would absolutely be a direct link to your page- and it would be even if this conversation wasn't happening, since the page explicitly states to do so
I also see that the version of fwtool distributed with the Flipnote Lenny generates a NO$ footer automatically. This would mean that if Flipnote Lenny were added to the guide, I could easily drop TWLNF from the guide, since that's what we're currently using for that. It's also still used to dump NAND contents to SD (as that's needed for HiyaCFW to work) but now that fuse-3ds supports DSi NANDs I can add that instead, which completely drops TWLNF
I understand you're continuing development of this, but in the meantime I'd like to make things as easy on the end-user as possible.- and Flipnote Lenny being on the guide instead of ugopwn would absolutely help achieve this. That's why I made this guide to begin with- I wasn't happy with any of the others, they'd use unsafe methods, they were convoluted, they didn't explain things well, they were outdated, and the list goes on.
@
BigOnYa:
@
K3Nv2:
@
Xdqwerty:
