Since I'm not even necessarily prepared to commit to writing a login server, I definitely have no intention of organizing a derivative project. I mentioned the fork just to point out that there is no reason that a person with views other than /dev/noob's would necessarily have to take what he gives them or shut up. There are other alternatives.
As far as your statements about claiming code as your own... I don't know where that came from, but it is a non-issue. I have seen that used, in the past, as an argument for keeping the login server closed source but it doesn't make sense. There is nothing in the eqemu license that says that you _have_ to use the eqemu login server. Nor is there anything that says that you, as a server op, have to disclose that your server runs eqemu. If a server op chooses to bypass the eqemu login servers and instead has an activex applet in their webpage that automagically alters the eqhost file and launches the game, more power to them. The end-user wins, because they don't have to go through the process of registering w/ this site (and its rather asinine registration rules). The server op wins, because they have sovereign control over their own server via login server independence.
I'm perfectly happy to agree to disagree on this one. I would certainly never invest the time and money necessary to run a server without complete control over every aspect. There are many other valid reasons for wanting your own login server, though. Since I periodically entertain the notion of getting a fast connection and hosting a server, I also periodically consider alternatives to the public login server. My surprise that more people don't feel the same way is equaled by my disappointment at the responses given to those who do.
|
Threaded Mode
