devdocs/todo.txt

@@ -3,12 +3,46 @@
 
 
 todo: update post on forum on Thursday, not before trip to vic.
+todo: Licensing 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/
+
+
+
+todo: CLIENT UI license changes for subscribers around the LICENSE pages and route??
+
+todo: LICENSE must prevent a user from moving their data from perpetual to sub and vice versa without the right key so we can control it
+	otherwise they could just download the data and run it locally as it's got the license in it
+	See immediately below potential solution
+	CONSIDER: is this an issue?  If so how to control it, maybe some kind of file flag or invisible config key or something??
+	This has implications for competitors running subscription services
+		i.e. havabyte says I'll host it for you just download your data and send to me and I'll do it for less
+			The critical part is the update, if the license permits updates for subs it has to be only when we do it
+			otherwise they self host and enjoy free updates unless we zap the license..hmm... needs something more here
+
+			Maybe they can't download the backup with the license intact??
+			Maybe they can't intereact with the license page at all if it's subscription, just view it??
+todo: SAAS different license checking method to ensure only *we* are hosting it if it has a saas license
+	something location dependant, a different license server address?  
+	We might host with other than digitalocean at some point so we can't look for that as a key
+	I guess we have our own approved IP addresses maybe in rockfish, if the license request comes from anywhere else than set for that customer we go fuck no and shut it down??
+	Does digitalocean ever change the ip address?
+	** Actually a static file outside of the backup would be ideal as it is easily transferrable by us, doesn't rely on ip address fuckery and can contain a signature inside it just like the license does, same key so we know it's legit
+		and if no file present then it's not hosted by us and as long as the license is perpetual then we're ok, but if the file not present and it's an SAAS license they fuck that shit stops working says not running from a licensed location.
 
 
 
 - NEW WEBSITE flesh out the framework and post as an alternate v8index.htm intrey portal so can fully make it without affecting v7
 	get the live test server stuff worked out too in advance
 	sb triggered from a route to make things simple and so client / website doesn't need to do too much
+	Try it on a phone, it looks shitty on my phone the images are way too small
+	I need to rethink the website images
+	also it needs a summarizing paragraph at the top with links not just jump right into features
+	Images need to be clickable to zoom in on them figure out how to do that hopefully bootstrap has built in thing
+	Needing pricing and plans to be broken out by type maybe with a calculator to figure price
+	NOTE: for the new website when marketing the plans Subscription vs perpetual etc there is a lot of useful ideas in the links I've been using for pricing to get some text content for the pages to help people choose.
+	i.e. https://www.linkedin.com/pulse/basic-differences-between-saas-subscription-perpetual-frederic-hanika
+	"What other reasons would a customer have to use SaaS or ask for a subscription instead of a perpetual license? Well, a very often-observed point is frustration with internal IT that has very long delivery cycles and are usually themselves very restricted by internal budgets and, hence, cannot deliver new functionality short term. Another large point in favor of a subscription contract from the customer perspective often is to avoid lengthy capital expenditure approval processes. Subscriptions can be and hence usually are priced to fit into the budgets of departments, which means the decisions can be made there and don’t need to be funneled into complicated corporate approval processes.
+	How does this impact the software vendor on the other side? A shift in buying power from central buyers to more departmental buyers, the need for more business and solution oriented sales approaches and usually much shorter sales cycles."
 
 
 - SHAREIT product codes once have pricing figured out fully and agreed on by joyce