Hello everyone ,
I’m from Brussels, Tehran, and Shiraz
Working on my startup, Lutino.io
How I found Logseq: Through a brilliant friend of mine and noticed in potential in producing structured content, even to the level of OWL2 ontologies, while staying connected with the power of Shell. I’m looking into how to better integrate Logseq with the command line so I can have full immersion between the power of Unix scripting and the command line and the power of Web and integrations that are enabled via APIs, as they grew to be more and more commonplace. But command line stays the only interface for many decent pieces of software and exclusively so, due to the non-relevance of a graphical user interfaces, again mainly due to the cost of development, which in fact Logseq can also help bring down but that’s for another day.
Nice to meet you all. I have a number of good proposals in shaping the framework for the potential that Logseq has. One of the things that I find fascinating with Logseq is the ability to commodotise the production of data and not just any data, data in a connected graph. At the same time, it’s its commitment to privacy-first and the fact that their version is actually provable. Although, I can be critical of the iCloud-only on Apple devices, which sort of forces certain users into uploading their content, unencrypted (i may be wrong about this) on Apple’s controlled cloud.
But its use of Electron is a brilliant choice of architecture. With this kind of architecture[^1], a plugin developer can theoretically give the assurance to its users that their stuff is solely stored on their local storage. Because at the end of the day, this is what this game comes down to. It’s the assurance and trust you can gain from your user so they are not worried about privacy when they interact with software you have written for them, at the end of the day, to make their lives better, as opposed to the somewhat common practice of stealing people’s data to enrich other AI models, which they would then sell for profit. I’m saying, Logseq’s arch should be able to address that concern, fully because it can guarantee off-the-grid processing, Edge computing, as it were.
[^1]: and it being open as open as Logseq is being, which is great, by the way.