Love your contents! I have been using Logseq for almost a year, but I am about to quit out of frustration with all plugins failing to load. I've read a lot of people raising the same issue; some of them claimed to have solved the problem but still, they have yet to clarify how did they do it. Can you make a video solving this issue? The error notif: "This plugin #(Plugin name) takes too long to load, affecting the application startup time and potentially causing other plugins to fail to load."
Logseq is already doing a big mistake that is integrating ChatGPT. They can't do that and claim to be privacy-first. ChatGPT is even blocked in Italy for violating privacy laws. Another mistake was omitting to say that they built a closed source module to handle encryption and we discovered it only because of a user attempting to build Logseq for an architecture that was not targeted by that module. Such behavior is highly controversial in FOSS. Some users are already thinking to maintain a patched version i.e. removing controversial features. A fork is not feasible now but if Logseq will be valuable enough while making these mistakes there is a chance some contributors organize in a team and start a fork with the added value of developing in the open and not privately in a company.
I like to apply a modified version of Hanlon's Razor as much as possible when evaluating the actions of others - "never attribute to malice that which is adequately explained by ignorance". And I don't use ignorance as a judgemental term there, but rather an all-encompassing term -oversight, confusion, lack of experience... Tienson has written about this issue here: discuss.logseq.com/t/why-logseq-ai-and-how-to-preserve-privacy/17486
@@CombiningMindsPKM I don't see where my comment implied malice, I used the term "mistake" multiple times. Nor I see why good intentions would relieve the issue: "The road to hell is paved with good intentions".
Can you provide a link to this information about Logseq integrating ChatGPT? I'm researching different options and would like to read more about this, thanks.
What kind of headphones do you use Dario?
Bose QC35s :)
Love your contents! I have been using Logseq for almost a year, but I am about to quit out of frustration with all plugins failing to load. I've read a lot of people raising the same issue; some of them claimed to have solved the problem but still, they have yet to clarify how did they do it. Can you make a video solving this issue?
The error notif: "This plugin #(Plugin name) takes too long to load, affecting the application startup time and potentially causing other plugins to fail to load."
Unfortunately this is not something which I have experienced. It's best to log a bug: github.com/logseq/logseq/issues
I’d be so curious about your Hugo workflow. Do you have a video on it?
I don't have a video on it specifically, but there is this video that I did with Brian Sunter: ruclips.net/video/RzT20ejft3c/видео.html
Logseq is already doing a big mistake that is integrating ChatGPT. They can't do that and claim to be privacy-first. ChatGPT is even blocked in Italy for violating privacy laws.
Another mistake was omitting to say that they built a closed source module to handle encryption and we discovered it only because of a user attempting to build Logseq for an architecture that was not targeted by that module.
Such behavior is highly controversial in FOSS.
Some users are already thinking to maintain a patched version i.e. removing controversial features.
A fork is not feasible now but if Logseq will be valuable enough while making these mistakes there is a chance some contributors organize in a team and start a fork with the added value of developing in the open and not privately in a company.
I like to apply a modified version of Hanlon's Razor as much as possible when evaluating the actions of others - "never attribute to malice that which is adequately explained by ignorance". And I don't use ignorance as a judgemental term there, but rather an all-encompassing term -oversight, confusion, lack of experience...
Tienson has written about this issue here: discuss.logseq.com/t/why-logseq-ai-and-how-to-preserve-privacy/17486
@@CombiningMindsPKM I don't see where my comment implied malice, I used the term "mistake" multiple times. Nor I see why good intentions would relieve the issue: "The road to hell is paved with good intentions".
@@alxlg Good point. I guess I'm guilty of not following the razor myself and reading the comment in a harsh tone 😏
Can you provide a link to this information about Logseq integrating ChatGPT? I'm researching different options and would like to read more about this, thanks.