ryu-suke

Thanks for the feedback.

I always describe it as a digital workspace as i see that as much of a global definition for the app, yet when i first started what i was working on is something similar to obsidian and notion but without it being natively a note taking app. Something empty that can be customized fully and supports plugin system, all that to make something that doesn't require to be constantly modernizing.

thanks again for the support.

I get why that might seem a bit off. I linked to the GitHub org because i was only presenting the project's idea and hoping for feedback and support, the website was also provided there.

Another user point that as well, English is not my first language so i think i miss used the word 'approved', if a plugin is open source it will be labeled as verified otherwise it will be unverified, in both cases they will be available in the app's plugin section for installation.

That’s fair, I understand that open source is a deciding factor for some people. I also get concerns about sustainability right now, there will be no subscriptions as i said in the site it will be free no matter what, The financial side of the app is purely based on donations, and the focus is on growing an ecosystem of tools that developers can build on freely.

Thanks again for considering it, and for your feedback

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.

Hollow isn’t open source, so there’s no public repo for the core project. If you’re looking for more details about how Hollow works, I’d recommend checking out the website https://hollow-space.web.app/

Thanks, I released a simple Play video a while back showing an earlier version https://www.youtube.com/watch?v=1ShchM6MDIU. and what i would say changed a lot from that version is the notebook, i would recommend reading the changelog of the new version after watching that video https://hollow-space.web.app/changelog

Great points, The ideal users are those who want a highly customizable digital workspace without being locked into a rigid structure, and i do have plan on releasing some videos about that. thanks for the suggestion, definitely something I’ll be doing!

Thanks for the heads-up, they are from the original Next.js template i used that haven’t been fully adapted yet, I’ll be fixing these soon

The decision to keep Hollow closed source isn’t about restricting users, it’s about ensuring stability while maximizing customization through plugins and themes. you can extend it freely using the plugin system, much like how browsers allow extensions without requiring users to alter their source code.

I understand concerns about long term sustainability and rug pulls. Unlike subscription based models or cloud locked apps, Hollow is 100% local, and the app remains fully usable regardless of future updates. The goal is to foster a plugin driven ecosystem rather than requiring contributors to maintain the core software.

And Thanks for trying out Hollow, really glad to hear you find it promising.

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

customizability lies in its plugin and theme system, not in modifying the core source code. The goal is to give users complete control over their experience without needing to edit the underlying codebase. You can create plugins to extend functionality, design themes to change its look and feel, and tweak everything to fit your workflow, yet i do understand how important for apps to be open source, therefore i wont guarantee that happening any time soon