-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notion independence #89
Comments
Hi @ralienpp Thank you for the questions and feedback.
Building a UI from scratch is a time-consuming task. Notion is friendly to feed the data while providing an excellent cross-platform UI, which will boost the dev progress greatly.
Agree, if we fully trust Notion, that's no problem, but if no, Notion won't be a good choice.
Good idea, I will do some research to see which one will be a good fit next. Again, thanks for sharing your thoughts, will continue the research and discussion. |
As a follow-up, perhaps considering an open-source alternative to Notion could be a good compromise: https://github.com/docmost/docmost It can be self-hosted, so there are no privacy concerns, and you can still reap the benefits of not having to work on a UI. |
Thank you for the recommendation. I will study it then, especially to see whether it could support APIs for uploading the data. |
docmost is nice, but it doesn't support API uploading; we cannot use it in a programmatic way. |
I'd like to understand the rationale behind choosing Notion as a way to display results.
If one wants to self-host the solution for privacy reasons (e.g., if data are aggregated from sources that include proprietary information), then sending results to Notion would defeat the purpose, no?
If
auto-news
could generate an RSS feed of its own, or save the results to a Markdown file, or perhaps use a static site generator - it could still serve its purpose without having to invent a UI from scratch.The system would be more appealing for my use case if it could be entirely self-hosted, running along my own instance of ollama.
The text was updated successfully, but these errors were encountered: