> It's easy to add data sources, but they still have to be programmed:
And do they need to be programmed in go and compiled into the app? Or can one write a shell-script or python-program and collect from their output?
> I'm not really sure what you mean by "optimized parts"
If you modularize a software to the point that the parts are working independent of each other, then you are able to replace them per demand. For example, you can use a different UI, which is better for your workflow. Or use different sources which are only relevant for your personal circumstances. etc.
We have this with email, where mail-servers and mail-clients are independent parts of the ecosystem. Where open protocols like IMAP allow for scripts and external programs to work side by side with your client to attach missing functionality.
This level of modularization is missing in most of those aggregator-tools I've seen so far. And I think it's doing more harm that benefiting the users. For example, what if your app is saving its entries via IMAP, and your UI would load it via IMAP to present it in an optimized interface? It would mean your timeline could also be filled by all other mail-capable sources, while the data in your backend could also be customized by any IMAP-capable tool, like filters, etc.
And do they need to be programmed in go and compiled into the app? Or can one write a shell-script or python-program and collect from their output?
> I'm not really sure what you mean by "optimized parts"
If you modularize a software to the point that the parts are working independent of each other, then you are able to replace them per demand. For example, you can use a different UI, which is better for your workflow. Or use different sources which are only relevant for your personal circumstances. etc.
We have this with email, where mail-servers and mail-clients are independent parts of the ecosystem. Where open protocols like IMAP allow for scripts and external programs to work side by side with your client to attach missing functionality.
This level of modularization is missing in most of those aggregator-tools I've seen so far. And I think it's doing more harm that benefiting the users. For example, what if your app is saving its entries via IMAP, and your UI would load it via IMAP to present it in an optimized interface? It would mean your timeline could also be filled by all other mail-capable sources, while the data in your backend could also be customized by any IMAP-capable tool, like filters, etc.