devdocs/todo.txt

@@ -6,6 +6,7 @@
 todo: License agreement changes for SAAS customers, this is huge and I hadn't thought of it before, wording is very different in this case, fuck, need to wing it I guess
 	https://flgpartners.com/saas-pivots-transitions-perpetual-to-subscription-saas-models/
 	needs to be available separately in docs
+	Needs a disclaimer about the right to refuse service if becomes too high usage i.e. subject to usage limitations to cover our ass and check with D.O. how to clamp that from going into expensive territory for us?
 
 
 todo: ROCKFISH different license key signature if it's a SAAS license
@@ -23,8 +24,15 @@ todo: if SAAS needs to do some things differently:
 	CLIENT - alt license agreement when SAAS
 	CLIENT - hits OUR copy of documentation if SAAS?? (not sure if this is necessary or desireable but something to consider)
 	DOCS - alternative txt when SAAS about how licensing works
-	
-
+	DOCS - doesn't need a version selector ultimately as always latest version
+	BACKUPS - do we backup, do they who is ultimately responsible for the preservation of the data?
+		what does D.O. say about this?
+		Can it just be an on top of charge or should we just bundle it into the charge and accept it's necessary?
+	SERVER - much smaller attachments max size, right now it's set to huge as possible but we need to cap that shit hardcore
+	SERVER - Ability to set a maximum attachment size
+	SERVER - hide any info about the droplet technical stuff like ram and ops stuff, we don't want them to have an idea how much memory they can have, or do we?
+		maybe it's a plust because we can say you get a maximum storage for attachments of XXGb based on droplet size and it's an add-on to go with a bigger server??
+		Because some people need it and will pay for it if it's offered.