[ryu-suke]

it's not about getting people to "work for free", it's about enabling people to create freely. The reason verified tools need to be open source is to ensure transparency and trust for users who install them, and for me to label them as verified, not to impose a one-sided standard. Users should know what a plugin does before they integrate it into their workspace. That said, nothing stops developers from making private or commercial plugins if they choose to, it will still be available on the app's plugin list but it won't be labeled as verified

[traverseda]

>The reason verified tools need to be open source is to ensure transparency and trust for users who install them

Is that not true of the code you've written here as well? I don't understand why you have different rules for yourself or for people developing for your platform.

[ryu-suke]

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.