Phamhilator Network v2

[ArcticEcho]

With the recent in introduction of Yam it would seem in the best interest of everyone to clearly lay down a new (fresh) structure for the network, but this time, keeping in mind we're creating a functional network based collection of bots, rather than three individual bots.

This will also be a good opportunity to work on a majority of missing features (and active bugs), as well as clearing any confusion over the bots' names (currently there's a "Pham", "Yam" and the "network" itself). So, if everyone agrees,

• Phamhilator (bot) -> Pham,
• Yamhilator (bot) -> Yam,
• Phamhilator (network) -> Phamhilator.

These changes will inevitably mean a full data reset (judging by the current performance of Pham, that may actually be a good thing). A new branch has also been created.

---

• Remove CE.Net submodule (replace with NuGet package).
• Add licence snippet to all source files.
• Replace all usage of JsonFx.Json with Newtonsoft.Json.
• Move Yam sockets (and other objects necessary for basic network communication) to Phamhilator.Yam.Core.
• Merge Pham's core into the UI (move any used methods/classes to Phamhilator.Yam.Core).
• Centralise authorised users/owners data.
• Add flagging abilities to Pham (Re-enable Pham's flagging capabilities #65).
• Upgrade current data management system/centralise data.
• Reset term data.
• Remove CsQuery (and replace Json.Net) (Remove CsQuery (and replace Json.Net) #77).
• Implement new Pham internals (Code spring cleaning + core restructuring #37).
• Yam: monitor Pham error rate, auto restart if necessary.
• Pham: implement/fix misc. FRs/bugs.
• Deploy the network.

[Unihedro]

Will there be milestones for each step of the v2_network production?

[ArcticEcho]

I don't see why not :D