ToS

[matthewr6]

I'm thinking we copy most of what another site has, because I don't want to call a lawyer to review hand-written ToS (though we probably should after modifying whatever ToS we use)

[PullJosh]

I'd say take an existing TOS, and then just add a portion that states that we reserve the right to revoke access to the service without warning yadda yadda yadda.

[matthewr6]

Which CodePen already has :P

[PullJosh]

Steal theirs.

[PullJosh]

And if there's anything that needs to be modified, just cut & paste portions of other TOSes.

[matthewr6]

Yeah, that's what I was planning to do - I'll get everyone here to review it.

[PullJosh]

Okay, sounds good! :D

[matthewr6]

Don't close this - will post the modified terms

[an-OK-squirrel]

KK!

[BookOwl]

OK

[alyssarosenzweig]

No. Just no. This is a bad idea on so many levels. A good license will do everything you need. And copying licenses / terms of services, is still copying... putting you in more legal trouble than you started in.

(Disclaimer: I am not a lawyer. This is not legal advice. Consult a lawyer if you're serious about this.)

[matthewr6]

Yeah figured that out about copying licenses yesterday when I did some research

[matthewr6]

But "a good license" doing everything we need won't cut it if we plan to make this expand past purely an editor.

[alyssarosenzweig]

@Firedrake969 Then my point would be don't expand this past just the editor--- too much maintenance overhead!

[an-OK-squirrel]

I have to say I agree with bobbybee on this one. There's not a point with sharing or loving/faving when it comes to HTML.

[matthewr6]

It's an experiment I'm willing to try, even if I need to maintain it alone. To me, this is practice in Django, integration testing, and deploying as well as just making another SPA.

[matthewr6]

Um Codepen has stuff like favoriting ;P

[an-OK-squirrel]

Okay, you maintain it. It's still going to be super annoying to moderate.

[matthewr6]

I don't think it'll get that big

[PullJosh]

It probably won't.

But what if it does? How do you plan to moderate if this somehow explodes? It probably won't happen, but if it does, we want to be ready - no point in planning on the project being a failure.

[matthewr6]

It's really easy to lock down everything in a few line changes.

[an-OK-squirrel]

So if the site gets too big, shut it down? Yeah, sounds good to me.

[matthewr6]

Lock down the logins/registration but keep the editor.

[an-OK-squirrel]

That's a terrible plan :P

[matthewr6]

It's a last resort only

[alyssarosenzweig]

@Firedrake969 Well, make more resorts :P

[matthewr6]

What type? Ski? Beach? :P There are a lot of ways to start moderating, such as manually approving users (which we already do, in a way)

[robinp7720]

Why are you guys focusing on the backend when nothing has been done to actualy make elemental. You guys are talking about an authentication system with sharing projects and everything without having a working block based html editor. If you guys are gonna continue with this backend crap, this project is going to take ten times longer!

[matthewr6]

PullJosh (and possibly others) are working on the frontend already. The backend is the easy part in this case. Instead of coming on here to say that, ask PullJosh what needs to be done :) I'm primarily working on backend because it's what I want to practice on, though I'll start doing more frontend once the UI is worked out.

[robinp7720]

The backend is just over complicating things right now. We don't need a templating engine for a block editor.

[matthewr6]

Then don't use it. PullJosh is just completely ignoring the backend - follow his example. Leave it to others to reconcile fe with be if you don't want to. also fixed your post

[BookOwl]

Can you please be nicer, @robinp7720 Thank you

[robinp7720]

Sorry,I have a very aggressive nature :(

Anyways, scratch uses a rest api as a backend for saving and loading everything and the editor is standalone.

So I'd recommend either 2 branches or 2 repos. One for the front end and one for the backend rest api. This way the editor could be run completely standalone from the backend.

[BookOwl]

It's OK :) I like your idea, you will have to convince @Firedrake969 though...

[robinp7720]

@Firedrake969, I believe I have to convince you! SO here is my attempt. You like backend and hate frontend? You will never see front end if they're both seperated! I dont know how hard a rest api is in python (Never tried it) but it would allow us to easily port elemental to android and IOS with something like XDK or something similar! It would also allow everyone to ignore the django templating syntax and just work purely on making elemental the best it can be!

Please say I convinced you! :)

[matthewr6]

I don't hate front end but I was planning on using Ajax for most things anyways :P

[robinp7720]

! So I convinced you! yay! Anyways, I think is is the wrong place to have talked about this :p

[matthewr6]

If convincing means agreeing... Lol As said - you don't need the templating syntax to work on Elemental. Why do you keep thinking that?

[robinp7720]

because it the only reason people use templating engines? (I presume. I've never used django but some require you use atleast some templating syntax)

[matthewr6]

It requires no templating syntax at all.

Think of it as what PHP does but better.

[matthewr6]

Thoughts? Some parts are somewhat copied, yes, but they're standard templates for ToS.

Basically, be good, and anything you do is your fault. Not ours. Here goes.

By using ElementalCode (the "Service") and its hosting site elementalcode.herokuapp.com (the "Site"), you agree to the following terms. ElementalCode reserves the right to block and/or terminate your account without notice from the Site if the end user violates any of the listed terms.

You may not use the Service for anything illegal under United States and European Union law, including hosting or sharing illegal or illegally obtained files. You may not save anything that may be considered NSFW (such as, but not limited to, sexually explicit content and vulgar language).

You agree to defend, indemnify and hold harmless ElementalCode from and against any and all claims, damages, obligations, losses, liabilities, costs or debt, and expenses (including but not limited to attorney's fees), resulting from or arising out of a) your use and access of the Service, by you or any person using your account and password; b) a breach of these Terms, or c) Content posted on the Service.

In no event shall ElementalCode be liable for any indirect, incidental, special, consequential or punitive damages, including without limitation, loss of profits, data, use, goodwill, or other intangible losses, resulting from (i) your access to or use of or inability to access or use the Service; (ii) any conduct or content of any third party on the Service; (iii) any content obtained from the Service; and (iv) unauthorized access, use or alteration of your transmissions or content, whether based on warranty, contract, tort (including negligence) or any other legal theory, whether or not we have been informed of the possibility of such damage, and even if a remedy set forth herein is found to have failed of its essential purpose.

Your use of the Service is at your sole risk. The Service is provided on an "AS IS" and "AS AVAILABLE" basis. The Service is provided without warranties of any kind, whether express or implied, including, but not limited to, implied warranties of merchantability, fitness for a particular purpose, non-infringement or course of performance.

ElementalCode does not warrant that a) the Service will function uninterrupted, secure or available at any particular time or location; b) any errors or defects will be corrected; c) the Service is free of viruses or other harmful components; or d) the results of using the Service will meet your requirements.

We reserve the right to update these Terms of Service at any time without notification.

[an-OK-squirrel]

You may not use the Service for anything illegal under United States and European Union law, including hosting or sharing illegal or illegally obtained files. You may not save anything that may be considered NSFW (such as, but not limited to, sexually explicit content).

Needs to specifically include swearing,

[matthewr6]

"such as but not limited to"

[PullJosh]

Seems good (coming from someone who knows basically nothing about law.) As long as it says "we aren't responsible for what you do", and also "we reserve the right to kick you off our site", we should be all set.

Nobody reads them anyway, so we can reserve more rights than we even need, just to be safe.

[matthewr6]

lol yeah

[an-OK-squirrel]

But some people think swears are completely fine

[matthewr6]

Ok, I'll add it. Anything else?

[an-OK-squirrel]

Maybe he'll lower the price by a few hundred thousand dollars xD

[matthewr6]

Anyways, serious input?

[an-OK-squirrel]

My input is complete already.

[matthewr6]

Ok, cool. @PullJosh?