Leaderboard

We have a zero tolerance policy on phishing.

Moved to Questions.

Value is subject to the market...crypto works more like a stock than money. Its value changes nearly continuously. Until we sell, there is no fixed value for it. If we sold it right now, we'd have $0.58. When the coin price goes up (which it will over time, its down right now for a few reasons), your work will be worth more to us. If you're curious about the price and price history, you can track the value of the coin here: https://coinmarketcap.com/currencies/electroneum/ (You've earned us 6.71 coins).

I think this would be a good solution

No. This server will be its own thing. We have no plans to replace the linux servers or cPanel. We're trying to avoid Plesk because of cost and complexity. I'm most likely going to end up developing a barebones back-end myself. IIS doesn't really have a great web-based front end, so odds are users will need to install the Windows RSAT and manage that aspect with the conventional MS tools if the web tools MS provides don't cut it and free ones don't already exist. Recent research suggests one good (and relatively easy) solution would be to configure the Windows server as a "slave server" for the existing linux boxes. IIS/.NET would be offered like Mono and Java are now on Tommy...you'd just sign up for a Tommy or Johnny account like always, and "request IIS" in cPanel. You'd get an FTP folder and a user account on the Windows server where you upload your ASP.NET stuff and configure IIS. Then you visit it through your existing cPanel account's website as if it was a subfolder, kind of like what a Java WAR does now (upload, configure/deploy, and it appears as a virtual folder) This would mean everything except IIS/ASP.NET is handled by our already-proven cPanel servers, so we don't need to reinvent the wheel implementing DNS management, user management, and the tons of other things cPanel does. PHP and other languages could be made available through IIS as well if there's demand for it. Also, stock IIS has very little functionality for shared environments. For instance, it has no capability for user management except by site (and each needs to be on a different port I believe). Plesk cheats by using one IIS site for all users and just having its own user management system outside the Windows one to control access. I suppose I could develop a user management solution if need be.