1,114 karma · joined December 10, 2016
Building http://openwa.dev/
https://twitter.com/smashah
The worst thing about Puppeteer is chrome and it's bad memory management so I'm going to give playwright a spin soon.
It will need to start from the individual level so I will be encouraging everyone around me to limit their exposure to Indian businesses.
I think it's time to consider Boycotting, divestment and sanctions of India since it's flat-spinning into the clutches of full-on fascism.
Very sad.
But that's the same as any organization. In normal business, you're meant to follow the main tenet of "maximize profit", "treat customers well". Businesses follow those tenets as they see fit. There's no reason for every open source project to be cookie cutter.
One shortcut with all this is just to allow maintainers to surcharge a premium with deploy buttons.
Unfortunately there are limited tools/resources out there to answer the question "how can i build a cloud deployment option for my open source project" without 25 layers of abstractions. This is why open-source projects end up raising millions of dollars (e.g strapi, appsmith just off the top of my head). All this money just for all these companies to essentially build the same thing.
Ideally, there should be a service/tool (maybe thenile will be it) where I answer a few questions.
Containerised? Stateful? Long lived? Keep alive? Allow end users to deploy many instances? % premium per instance over cloud costs? License per instance? Pricing (tiered, volume, stairstep?) On end customer's own infra? Min resources per instance. Airgapped per user/airgapped per instance/all instances running on same cloud? Instance management API? Update strategy? Big Green button to update all instances at once?
And it should spit out a ready to deploy setup where I can start monetising my open-source project while concentrating on maintaining the project.
If the above exists then congrats, you disrupted the main reason for open source projects raising millions of dollars.
Every instance is linked to an end users number, licenses are sold per number per month. Self-hosted SaaS.
Thankfully I've managed to get sustainable growth as a solo open source maintainer by offering licenses for advanced features only businesses would need.
I'm sure Abraham would be proud to have had his name attached to essentially a weapons contract masquerading as a peace deal between two evil governments.
Prevalence of MLMs doesn't make any of them any less impractical.
Are you doubting that VCs can be victims of their own in-group biases?
Can't help but think the famous VC concept of "pattern matching" is a euphemism for something more sinister.
Changing the license is weaponisation?? It's the bare minimum and least intrusive. And then you all complain when someone tries to implement a Hippocratic or Do Not Harm license. "WEAPONSIATION"?? Really?
The lesson of all this is to keep an eye on your supply chain. Simple as. I think it's a sign of entitlement when you expect OSS devs to build you robust and reliable systems then leave the rest of themselves at the door.
I mean how does discourse itself provide the discourse-hosted version (https://www.discourse.org/pricing)?
Do they spool up a new instance via K8S? Do they use terraform every time someone signs up? How do they manage one paid user wanting to run multiple discourses? There should be a guide for this, it would make a lot of OSS maintainers' lives much easier.
Is there some sort of how to forum/guide on setting up a hosted versions of open-source projects? Googling this specific thing is quite difficult. A good alternative to setting up my own hosted service is for me to be able to ask DO to charge a $2/10 pm premium via my DO deploy buttons instead. I have sent thousands of clicks their way of which i see $0 via basic referrals. One can dream!
Nowadays a non-templated bug issue is autoclosed.