I don’t get the point. Now, we cannot use the word “worth” anymore to describe anything that could hypothetically move the market down by a few percent when sold? With the usual ups and downs of Bitcoin, we will probably barely see it in the graphs…

It’s 0.4% of the market cap. It’s not like Satoshi with his 10% of the market cap came back…

Thanks.

“Outline” looks interesting… Bad project name (hard to find), but good job.

you can link between notes and add plugin to see the graph. To get a note link, click on it with right button and there is an option to copy a link to that note. You can also link to a section of note with hashtags

Thanks. But I’m immediately asking myself, why Joplin had to reinvent the wheel here. Some other apps to the same. I get that Markdown itself was “underspecified”.

But why does a link to a different note need to look like this?

[Test](:/981236487219346972134687216439723)

A colon followed by a / and the name of the file without its extension (md)… This kind of makes sure that other markdown apps won’t be able to handle it. I know that others use [[Name]] notation or @@Name notation, but why not just sticking to the basics and using something like…

[Test](981236487219346972134687216439723.md)

…?

its hard to find something that fits you 100 %, but you can try make your own, that is how most of the foss projects start :)

True

I like Jopin, but the user experience feels a bit old (don’t want to say outdated) compared to something like Logseq.

And I also like the idea of links between notes and it becoming a graph. My nested folder structure in Joplin has gotten large.

I don’t like that Joplin does not store the notes as real markdown. They are not readable by humans until you export them.

I do not want Wysiwyg via mouse, e.g. by clicking the “bold” button. Trying out Logseq felt really good. For example, it allows to open sections of a large file on the right, which is nice, because you can easily focus on that part.

I like how Logseq has a nice “table of content” plugin that renders the TOC on the side instead of injecting it into the markdown file, which is not nice, because the file changes and you need to always update the TOC.

But I also don’t like what others describe here about Logseq’s markdown handling. A heading being after a bullet point feels wrong.

Adding functionality to Joplin via Plugins is an option, but the plugins will maybe not work on Android…

IMO, there is no optimal solution for me. I like parts of Joplin and others of Logseq, but there is no solution that has all of them.