myeducate wrote:

python_megapixel wrote:

TheRealNetherBefore wrote:

python_megapixel wrote:

But WHY? You aren't actually giving a good reason for making it proprietary. “It will never be open source” means pretty much nothing.

Because they want to? Isn't that a good enough reason to do something on your own website?

No it's not. I won't bother explain why because MasterOfTheTiger already has.

Why do I have to say this, again? Nj this is dead news.

rant warning!

ScratchNetwork's backend won't be open-source for these reasons.
1. It's my intellectual property. - Yeah, I can do what I want with it.Please stop saying that and actually provide a coherent reason why you don't want it open source. What are you gaining from keeping it closed?
2. It's used for more than ScratchNetwork. Many of my clients rely on the EDXTN framework everyday. Well, do them a favour by allowing them to freely use it then.
3. Data is an invalid argument - for those saying “but what is SN doing with my data??” you need to rethink. SN only collects your Scratch username. The EDXT collects your IP for hit logging, for that people read UK2's privacy policy. There is no way to hide whatever I post from everyone if I go back on it. So yes, it collects much more than just my username. Also, you are technically breaking European law by not having a popup.warning about your use.of cookies.
4. Security is also an invalid argument - I am not stoopid. I know how to secure my websites, and I don't need people to call me “lazy” for “not protecting information” when I am. Until recently, PushPoints were open to a ridiculously simple exploit equivalent to having a “steal” button. Not exactly secure
5. Your access to ScratchNetwork is not your freedom. - really, it isn't. What does that have to do with it?
6. The client is already open source. - Everything you see on SN is opensource. The backend isn't. Surely that just breaks the project into several pieces?

Yeah anyway, that's all.

python_megapixel wrote:

myeducate wrote:

python_megapixel wrote:

TheRealNetherBefore wrote:

python_megapixel wrote:

But WHY? You aren't actually giving a good reason for making it proprietary. “It will never be open source” means pretty much nothing.

Because they want to? Isn't that a good enough reason to do something on your own website?

No it's not. I won't bother explain why because MasterOfTheTiger already has.

Why do I have to say this, again? Nj this is dead news.

rant warning!

ScratchNetwork's backend won't be open-source for these reasons.
1. It's my intellectual property. - Yeah, I can do what I want with it.Please stop saying that and actually provide a coherent reason why you don't want it open source. What are you gaining from keeping it closed?
2. It's used for more than ScratchNetwork. Many of my clients rely on the EDXTN framework everyday. Well, do them a favour by allowing them to freely use it then.
3. Data is an invalid argument - for those saying “but what is SN doing with my data??” you need to rethink. SN only collects your Scratch username. The EDXT collects your IP for hit logging, for that people read UK2's privacy policy. There is no way to hide whatever I post from everyone if I go back on it. So yes, it collects much more than just my username. Also, you are technically breaking European law by not having a popup.warning about your use.of cookies.
4. Security is also an invalid argument - I am not stoopid. I know how to secure my websites, and I don't need people to call me “lazy” for “not protecting information” when I am. Until recently, PushPoints were open to a ridiculously simple exploit equivalent to having a “steal” button. Not exactly secure
5. Your access to ScratchNetwork is not your freedom. - really, it isn't. What does that have to do with it?
6. The client is already open source. - Everything you see on SN is opensource. The backend isn't. Surely that just breaks the project into several pieces?

Yeah anyway, that's all.

python_megapixel wrote:

myeducate wrote:

python_megapixel wrote:

TheRealNetherBefore wrote:

python_megapixel wrote:

But WHY? You aren't actually giving a good reason for making it proprietary. “It will never be open source” means pretty much nothing.

Because they want to? Isn't that a good enough reason to do something on your own website?

No it's not. I won't bother explain why because MasterOfTheTiger already has.

Why do I have to say this, again? Nj this is dead news.

rant warning!

ScratchNetwork's backend won't be open-source for these reasons.
1. It's my intellectual property. - Yeah, I can do what I want with it.Please stop saying that and actually provide a coherent reason why you don't want it open source. What are you gaining from keeping it closed? nothing, invalid argument.
2. It's used for more than ScratchNetwork. Many of my clients rely on the EDXTN framework everyday. Well, do them a favour by allowing them to freely use it then. how do I make my money?
3. Data is an invalid argument - for those saying “but what is SN doing with my data??” you need to rethink. SN only collects your Scratch username. The EDXT collects your IP for hit logging, for that people read UK2's privacy policy. There is no way to hide whatever I post from everyone if I go back on it. So yes, it collects much more than just my username. Also, you are technically breaking European law by not having a popup.warning about your use.of cookies. nope as you do not require that.
4. Security is also an invalid argument - I am not stoopid. I know how to secure my websites, and I don't need people to call me “lazy” for “not protecting information” when I am. Until recently, PushPoints were open to a ridiculously simple exploit equivalent to having a “steal” button. Not exactly secure “security bug”
5. Your access to ScratchNetwork is not your freedom. - really, it isn't. What does that have to do with it?
6. The client is already open source. - Everything you see on SN is opensource. The backend isn't. Surely that just breaks the project into several pieces? okay

Yeah anyway, that's all.

MasterOfTheTiger wrote:

I have to say that I am deeply disappointed with your decision not to take any of this seriously at all. I am going to start my own project.

myeducate wrote:

MasterOfTheTiger wrote:

I have to say that I am deeply disappointed with your decision not to take any of this seriously at all. I am going to start my own project.

Okay - a competitor would be ideal
What are you going to write it in? Checked out firebase? That might be useful.

MasterOfTheTiger wrote:

myeducate wrote:

MasterOfTheTiger wrote:

I have to say that I am deeply disappointed with your decision not to take any of this seriously at all. I am going to start my own project.

Okay - a competitor would be ideal
What are you going to write it in? Checked out firebase? That might be useful.

I forked your client. This will be a good learning experience. However, I do not think that mine will be able to compete very well (due to my lack of knowledge), but there needs to be a service like ScratchNetwork that respects the user.

I will gather a team to work on this (something you cannot do).

I am not doing this as an attack against you, but against the proprietary nature of ScratchNetwork.

Firebase does not seem like a good option (I am not sure it is free), but I will look around.

MasterOfTheTiger wrote:

myeducate wrote:

MasterOfTheTiger wrote:

I have to say that I am deeply disappointed with your decision not to take any of this seriously at all. I am going to start my own project.

Okay - a competitor would be ideal
What are you going to write it in? Checked out firebase? That might be useful.

I forked your client. This will be a good learning experience. However, I do not think that mine will be able to compete very well (due to my lack of knowledge), but there needs to be a service like ScratchNetwork that respects the user.

I will gather a team to work on this (something you cannot do).

I am not doing this as an attack against you, but against the proprietary nature of ScratchNetwork.

Firebase does not seem like a good option (I am not sure it is free), but I will look around.

Coder_Annika wrote:

MasterOfTheTiger wrote:

myeducate wrote:

MasterOfTheTiger wrote:

I have to say that I am deeply disappointed with your decision not to take any of this seriously at all. I am going to start my own project.

Okay - a competitor would be ideal
What are you going to write it in? Checked out firebase? That might be useful.

I forked your client. This will be a good learning experience. However, I do not think that mine will be able to compete very well (due to my lack of knowledge), but there needs to be a service like ScratchNetwork that respects the user.

I will gather a team to work on this (something you cannot do).

I am not doing this as an attack against you, but against the proprietary nature of ScratchNetwork.

Firebase does not seem like a good option (I am not sure it is free), but I will look around.

Can I jon the team?