"Cold Storage" by American screenwriter David Koepp comes to mind, a comedy splatter novel. I don't usually read such books, but this one was funny and entertaining.
Sounds like the early days of the web, when cookies weren’t widely used.
User sessions were created with a URL query parameter, like `?sessionid=`, and every page would pick up the sessionid and include it in every link on the page.
Who are you, which legal jurisdiction is your company located in? What is your target group? Selling local or global? Every jurisdiction probably has different rules what needs to be included on an invoice.
If you serve the U.S., then you need to calculate all the different sales taxes for each state. If you serve the E.U., you need to create PDF with included standardized XML soon. Don't know about other continents.
I think invoices are not about quick and pretty anymore, but there is a lot more to consider. You should make it clear what you provide and for which target customer.
Im currently talking to all users to make sure the system can provide exactly what they need for each country.
This is also why theres a free trial. To make sure that users see what the system is capable off before they buy it. I never want to take money from people without providing value.
It could be a good thing to have a confirmed email in the database, in case a 3-letter-agency knocks on your door because of some highly illegal content on your site.
I have to unsubscribe from five things a week that are clearly other people using my email address to sign up for things.
Someone used my email address to sign up for a Mint account. And the only way you can delink Mint is to call Mint or log into someone else’s financial account. I’m no lawyer but that seems like a very, very bad idea to me.
Their model may be one of the few that would truly be quite challenging to pull off with bare metal—running sandboxed code for 73 languages is hard to do economically with any setup, but being able to lean on cloud services for provisioning would make it much more achievable.
ah I see that might be a bit more tricky. I was wondering why the costs were so high.
For example, I serve roughly 3 million users on a $40/month VPS. I only run Postgres + Django, if I use Supabase and all these other fancy cloud SaaS I wouldn't be able to sustain it as the costs would increase 10~20x fold.
our postgres offering costs roughly equivalent of RDS so if you use it with Django I don’t think you will come close to 20-40x a VPS, ymmv, depending on your workload
We have an Auth service, but since you use Django you wouldn’t need it - sounds like you’d only need postgres (like a lot of our customers)
I don't think you get the point. RDS is expensive, just because you having pricing parity with it doesn't mean that you are going to be at the same pricing level as cheap hosting.
And thats fine, you have features on top that can be worth paying for certain customers and expenses of your own to pay. Those of us that have been around in this business for 30 years know how expensive PAAS and IAAS can be and how easy it is to roll your own solutions and when not to do that.
True, but I wonder what the cost split is. I'd expect the actual "run code from users" bit to be a minor line item, with the bulk being the actual app servers, databases and egress bandwidth.
They can very well keep the REPL/"run code from users" bit on AWS, but serve their actual website, application and database from fixed-price bare-metal servers.
This seems like a kids phone, so the "decision making unit" should be the parents in the end. I am sure they would know about Nokia, that they were happy users years ago and buy the brand again for their kids.
reply