Bespok's ultimate goals are as follows: -To engage in personalized marketing -To be trusted, because we do personlization
When we mention personalization, it involves gathering extensive user data, such as their behavior, purchase history, and browsing preferences. We understand that handling such sensitive information might lead to concerns about intrusion into users' privacy.
To establish trust in our system and demonstrate our transparent data collection practices, we have no choice but to open-source our software. By adopting an open-source approach, we can gain a competitive advantage in terms of trustworthiness and reliability.
Another crucial aspect of our long-term goal is to become a platform that facilitates data collection for any software operating on the internet. We aim to challenge the narratives surrounding companies like Facebook, TikTok, Google, etc., which have been criticized for exploiting user data to benefit advertisers. We believe that our approach can bring about a positive change, providing advertisers with an alternative platform where everything is conducted openly, instilling greater trust in the system among users.
I think the path forward towards the stated goals above is to start with a Mailchimp alternative. And eventually become the open source personlization marketing platform.
Hope you guys self host it today or sign up to check it out! Don't forget to give us a star on github!
MIT Licenced!
...said Afi and the very next day the license gets changed to AGPL-3.0
https://github.com/bespoke-surf/bespoke/commit/434dffe407b8a...
In the future we might make it much more simple, so you can just opt into any smtp service and start sending emails.
> Bespoke is MIT licensed for env variabe OPEN_SOURCE=true
> Bespoke Cloud is Business Source Licenced for env variable OPEN_SOURCE=false
> You will be violating our Business Source Licence if you have the environment variable OPEN_SOURCE=false
I would personally be uncomfortable using any software licensed in this manner, since you're not licensing the code itself, but the code in a particular environment. It's also pretty useless to add this complexity since the usage of that environment variable could easily be patched out while under use of your "OPEN_SOURCE=true" conditions.
Right now this was the only method I could come up with to release thing faster. I might think this through a little longer.
Thanks for the feedback :)
That prevents a private company from forking a closed source version without paying you.
It's Klaviyo that you're talking about?
