Inarguably, the latest Nintendo banwave for those using homebrew and/or CFW on their 3DS systems has affected a lot of people. By my estimate, roughly 40% of homebrew and CFW users have been banned, with the number likely to grow over time. Considering the large number of CFW users that affects, and the fact that many of these users probably had friends install CFW for them and don't know what they're doing, I propose the following easy-to-use app: It automatically backs up all of the following files affected by the app It automatically randomizes the last six digits of one's device ID in the SecureInfo_A file It automatically downloads and applies the latest public LocalFriendCodeSeed_B file (the URL would have to be applied manually for copyright reasons, similar to how one would get freeShop to work) It automatically applies the proper settings to minimize ban risk (e.g. turning off the Spotpass "share information" setting) In other words, it's an automatically updating freeShop for unbanned LocalFriendCodeSeed_B files. Public LocalFriendCodeSeed_B files are inevitably going to get banned, but it usually takes several weeks for that to happen. When the public LocalFriendCodeSeed_B file is banned, the user would just have to open the app and tap the "Unban me" button again, repeating the process with the latest public LocalFriendCodeSeed_B file and getting another several weeks of online play. This would be the most efficient way of dealing with the bans with regard to LocalFriendCodeSeed_B file-consumption. If we assume Nintendo doesn't increase the frequency of banning public LocalFriendCodeSeed_B files, then by my estimate, twelve or so public LocalFriendCodeSeed_B files would get the entire 3DS community through a year of online play, which is very efficient. Considering that 3DS online play likely has an expiration date in 1-2 years a la Wii and DS online play, that's only about 12-24 public LocalFriendCodeSeed_B files total. If Nintendo increases the frequency of public LocalFriendCodeSeed_B banning, then the project can die, and we can at least say we tried. I would work on the project myself, but I'm far too busy in my increasingly busy adultish life, and I wouldn't know where to begin anyway. I have a private LocalFriendCodeSeed_B file, so it really doesn't matter to me personally. If the project took off, I would consider donating 1-2 of my spare LocalFriendCodeSeed_B files to the cause. What do you think?