I had two main problems with LogSeq when I used it:
1. Not designed from the ground-up to prevent data loss. Has had data-loss issues in the past.
<strikethrough>2. An electron app that doesn't let you open multiple documents at once. (edit: nevermind, seems like they did lots of feature development here)</strikethrough>
That said, I don't know of any other good local-first outliners (i.e. like Workflowy).
> Additionally, some application developers directly parse a file in Mozilla’s source code management system called certdata.txt, in which Mozilla’s root store is maintained in a form that is convenient for NSS to build from. The problem with the scripts that directly parse this file is that some of the certificates in this file are not trusted but rather explicitly distrusted
Could the file be split to retroactively fix everyone doing this?
It's not strange. Many religions contain an absolute prohibition against denying your faith. It prevents any true believers in those religions from having government documents.
What?!? How does that work? Does he just draw up a blueprint and write "solid gold block goes here" and them some contractor says "yes that gold block will be $NNNNN" and includes it in the budget??
> but it’s way too much of a hassle to be used in the wild.
No it's not, it's just rare that you'd have the ability to inject CSS but not JS.
A core skill of hacking is being able to see through the things people would normally see as "hassle" or "friction" to the reductionist "what keys do I have to press on the machine in what order to make this happen".