Build your personal knowledge base with TriliumNext Notes - TriliumNext/Notes
TLDR: After the fantastic Trilium Notes entered maintenance mode, a significant group of community members (including myself) have committed to moving the project forward.
🎁 An official backward-compatible TriliumNext Notes release should be available soon!
If you haven’t heard of Trilium Notes (Or TriliumNext Notes), you should check it out. For an example of what TriliumNotes looks like, you can check out the slightly outdated screenshot tour. Trilium Notes is IMO the best truly open, and truly libre note taking software that exists.
Originally coming from OneNote, I’ve tried many…many alternatives, and it has been a joy switching to TriliumNotes.
🍻 This free (gratis), open-source, self-hosted, personal wiki/note software offers all the following with no nags, no paywall and no restricted features - you get all the goodies up front!
Note cloning (notes can exist in multiple locations at once)
Interactive note visualization maps
Various note types (canvas, mermaid diagrams, web view, relation map, code, etc)
Various bulk folder import and export options (HTML, Markdown, Text)
Good documentation, Matrix support chat, Github Discussion forums, awesome lists
The main downsides are:
The mobile (android) app currently is only for composing notes (not for reading other notes on the server). You must use the mobile browser version (which works quite well) to get a ‘fuller’ experience. (The new TriliumNext project does plan to improve the mobile experience).
Only one user per server is currently supported (this is a high priority for the TriliumNext team)
Some people don’t like database note taking software since they prefer files in a directory, but this isn’t an issue for me since I can automate the export of TriliumNotes (using the api) and save the notes to Nextcloud or my local file system for easy viewing.
📢 If this project interests you, you can follow the progress on github and get involved if you would like to see this project flourish! There are teams to help with development, issue triaging, documentation, testing, etc.
Its dangerous to send goalposts flying around that fast, be careful or you’ll hurt yourself.
Your response is condescending, arguing from ignorance, and arguing in bad faith. I will reply this time, because once again you’re trying to build an argument on extremely shaky ground and I don’t enjoy people spreading ignorance unchallenged. However I won’t engage any further and feed whatever you think you’re getting from this.
I haven’t suggested that people should use Obsidian over OSS solutions. I was simply pointing out your argument against Obsidian’s architecture was poorly founded.
The data you’re insinuating will be lost is pure FUD. While the format isn’t standard markdown, none of the well implemented solutions are, because as you so rightly pointed out, markdown has little to no support for most of these features.
However, obsidian’s format is well documented and well understood. There are dozens of FOSS plugins and tools for converting or directly importing obsidian data to nearly every other solution. Due to obsidian’s popularity, it’s interoperability this way is often far superior to FOSS solutions’.
obsidian’s format is well documented and well understood. There are dozens of FOSS plugins and tools for converting or directly importing obsidian data to nearly every other solution. Due to obsidian’s popularity, it’s interoperability this way is often far superior to FOSS solutions’.
To reiterate this claim: just because Erica gave Shida enough time to document his work in the open, she is entitled to exploit foss contributors for profit. Is that your point here?
Also not only she can exploit foss contributors when it suits her, she also can remove their work from the ecosystem whenever momentum for acquisition is ripe. Do you think it’s false?
If Erica doesn’t pay you to write these comments, does it feel morally right to you defending these capitalist practices?
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Its dangerous to send goalposts flying around that fast, be careful or you’ll hurt yourself.
Your response is condescending, arguing from ignorance, and arguing in bad faith. I will reply this time, because once again you’re trying to build an argument on extremely shaky ground and I don’t enjoy people spreading ignorance unchallenged. However I won’t engage any further and feed whatever you think you’re getting from this.
I haven’t suggested that people should use Obsidian over OSS solutions. I was simply pointing out your argument against Obsidian’s architecture was poorly founded.
The data you’re insinuating will be lost is pure FUD. While the format isn’t standard markdown, none of the well implemented solutions are, because as you so rightly pointed out, markdown has little to no support for most of these features.
However, obsidian’s format is well documented and well understood. There are dozens of FOSS plugins and tools for converting or directly importing obsidian data to nearly every other solution. Due to obsidian’s popularity, it’s interoperability this way is often far superior to FOSS solutions’.
To reiterate this claim: just because Erica gave Shida enough time to document his work in the open, she is entitled to exploit foss contributors for profit. Is that your point here?
Also not only she can exploit foss contributors when it suits her, she also can remove their work from the ecosystem whenever momentum for acquisition is ripe. Do you think it’s false?
If Erica doesn’t pay you to write these comments, does it feel morally right to you defending these capitalist practices?