There was no fork, if you talk about a blockchain fork.
What happened is, that feathercoin changed it’s hashing algorithm from scrypt to neoscrypt in order to remain ASIC resistant and allow people to mine Feathercoins with ‘standard’ hardware like GPU and CPU without spending a lot of money to buy ASICs.
There has been a group of people who didn’t like that move to Neoscrypt and they created a new coin called ‘Feathercoin classic’ which remained on the Scrypt algorithm.
If you already use the 0.9.6.1 client, you are on the latest production version of the client and all should be fine for you.
If you want to mine again, you may need to update your mining software to allow Neoscrypt for mining.
There are some posts in the mining section which software can be used and how to configure it.
Ideas expoused in this patent seem similar to ideas in Private Blockchain Address 2014, and stealth coin white papers from the same period. The “envelope method” of hidding payment details is also common.
That is a very positive write up. Some of those developments mentioned (were experimental and ) are being reviewed for future viability.
It is important that FTC can continue to support functionality, currently we are behind on keeping up with head for “normal” required basic functionality of a blockchain coin. i.e. I’d prefer the publicity when we are at v14 wallet and 6 of the mobile wallet and our auto build system is fully up. Or at least a chance to weed / review out unsupportable features.
As an open and open source project, we can only move as fast as members can contribute. As such the article under estimated the importance of the FTC forum and members in getting FTC to where it is.
There is a good background knowledge of the system and development process within FTC admins / contributers to push forward quite quickly with some more (programming in particular) support.