I get where you’re coming from, but the distinction is pretty straightforward: Hollow is the platform, and plugins are extensions that users install separately. The open source requirement for verified plugins isn’t about fairness between the platform and developers, it’s about ensuring transparency for users when they install third-party extensions.That said, not all plugins have to be open source, developers are free to create private or commercial plugins, and they will still be available inside the app. They just won’t carry the verified label, which exists purely to help users make informed choices.
traverseda|1 year ago
Some big companies can do unfair stuff like this. Somehow obsidian manages. I don't think you can with what you have right now. You make a compelling enough project, spend enough money on marketing, you probably can. If you want grassroots support it's not happening with that model. At least not from me.
You could consider sharing the source under the business source license. That might still give you whatever protections you're looking for but that you're not stating outright. You have sort of dodged the question as to why it's not open source, and you're not saying what your future plans are that mean it can't be open source. That concerns me.
Give the BSL (business source license) some serious consideration. I don't think you're going to get a bunch of developer early adopters if they don't have some ownership over the product.
edoceo|1 year ago