Right, there's been some great suggestions already and I'm going to answer questions.
Void: No poll because they make people vote without actually expanding on the topic. We really need good posts for this, this is a major feature that will lead to much bigger things than this at a later point.
And yes, login will be done with forum credentials.
FynnMcScrap: We would introduce a ship password feature, preventing the ship from being moved to another account unless you know this password. We'll probably introduce this soon because it's an ingame feature. Eventually if we want deletion and switching it to another ship impossible, you'd have to enter that password in a command like /shipstate that would serve as a ship lock on/off. This would solve the issue.
John Wildkins: There's little point considering the only moment this would go down would be when discogc itself go down. I'll see what I can do though.
the reason is simple as it is, as actual news show hacking a cloud is possible and there is no way to secure it.
if i were a hacker there are many points to attack such a system, first the password of the account owner, then the data way and last the server where the accounts are.
There are more ways to attack a cloud and who is responsible in terms of loosing all accounts or getting hacked?
The programmer, the server owner or you as a user.
The user because he is the one who trusted in such a system.
(10-12-2014, 10:48 AM)hades durin Wrote: i am against such an idea
the reason is simple as it is, as actual news show hacking a cloud is possible and there is no way to secure it.
if i were a hacker there are many points to attack such a system, first the password of the account owner, then the data way and last the server where the accounts are.
There are more ways to attack a cloud and who is responsible in terms of loosing all accounts or getting hacked?
The programmer, the server owner or you as a user.
The user because he is the one who trusted in such a system.
Disco can already be hacked, it wouldn't make a massive difference. Most of the time, hacks are the result of a user being compromised, and they're usually compromised due to severe neglect or poor understanding of computer security. I believe your understanding of computer security is likely a little bit limited, otherwise you wouldn't say "hacking a cloud" as such a thing is impossible as the cloud is only an architecture. It's the servers that are a part of this architecture that you hack.
Our backend is quite secured, and is regularly improved even more whenever we can afford time to work on it. Honestly this is not something I'm scared about, if somebody wanted to hack the server and grab all the data, they could already have done it a long time ago.
The only thing that can happen is a specific user being compromised, and that's going to be their own fault, not ours.
I quite like the Idea, though I agree that backups would need to be run, you never know what circumstances might hit the servers. Overall the Idea is a great thing, which streamlines it even more, of course everyone would need to use Launchpad for it. (there are still some who use FLAM).
I'd like to keep the launchpad as it is but I have no objection to the proposal, as long as we maintaine export import and store the accounts regularly.
I like the idea but if we can't also store them clientside... not sure how I feel about that
Another concern: This being stored on the same server box that the gameserver is? Alot of us already have lag issues, would hate to see what happens when a buncha people try to download their accounts, while some huge battle is going
laaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaag city
[ sci·am·ach ]
/sīˈamək/
A simple, angry man casually working his way through life on a personal quest to acquire copious amounts of street cred.