TriliumNext Notes will become Trilium Notes

[eliandoran]

When we started the TriliumNext organization, the main purpose of our project was to continue to maintain the @zadam 's Trilium Notes which underwent maintenance.

From the beginning, the TriliumNext name was more of a placeholder, my hope was to gain at some point the original name.

I've been in discussions with @zadam and he has agreed that the TriliumNext project is mature enough to regain the original name and has kindly transferred the original repository to us (see https://github.com/TriliumNext/trilium).

As such, in the upcoming weeks we will:

1. Migrate all the TriliumNext code to the original trilium repository.
2. Port the issues and discussions over to the original repository.
3. Rebrand the application and the organization.

If you have any questions or concerns, let us know.

[Lewis8265]

I mean this in the nicest way, but I personally struggle to see the value in going back to the previous name. It just seems like a waste of time that could be better spent. Everyone is now used to TriliumNext, so why not just keep it is that? No need to fix what isn't broken :)

[eliandoran]

It's a good take and there's nothing wrong in thinking that.

For me there are two arguments:

• You'd be surprised but there are a lot of people not aware of the Next naming, and they still raise issues and pull requests on the original repo.
• There is a certain resonance to the original name, the Next in our name feels a bit intrusive (being in the middle of Trilium and Notes). We might be used to it but new users aren't.

Compared to the other refactoring tasks we had to do, it's going to be a walk in the park.

[hugener]

What are the implications for Unraid installs?
Would somehow be an update or would we need to install fresh? Not sure how migration would work.

[ptmorris1]

What are the implications for Unraid installs? Would somehow be an update or would we need to install fresh? Not sure how migration would work.

Edit container, enable advanced view and should be able to point your docker version to new repo, if it changes. Currently set to triliumnext/notes:latest

[doobes]

I've run into a number of people who had just written Trillium off because they thought it was dead.

Am curious how this will affect my Docker install.

Good work Elian

[eliandoran]

Am curious how this will affect my Docker install.

Probably just a change in the image name, we'll see.

[carloshelly]

Wonderful news! Does this mean trilium next will then update itself via flatpak repository? it's quite a challenge to get it working under Fedora42.
If not, any plans to integrate such platform? Thanks :)

[eliandoran]

Does this mean trilium next will then update itself via flatpak repository?

Flathub support is not yet planned, due to the complexity. We still deploy flatpaks, but we have an issue with the desktop shortcut having the incorrect entrypoint (which can be fixed by manually editing the file). We'll solve it at some point but it requires digging in pretty deep in our build stack.

[carloshelly]

This is what I did:
Step 1 - Download the flatpak package from this github

Step 2 - Apply this code:
nano ~/.local/share/applications/com.triliumnext.notes.desktop

[Desktop Entry]
Name=Trilium Notes
Exec=flatpak run com.triliumnext.notes
Icon=/pathto/icon.png 
Type=Application
Categories=Utility;

chmod +x ~/.local/share/applications/com.triliumnext.notes.desktop

Under the version 0.93, it would work and sync properly. Since the version 0.94.0+, the app has been acting weird and would stop syncing. Also the desktop entry would only be run as a temporary app, you cant pin it to the bar. Its really sad(syncing issue), its the best notes app out there with no sync issues between devices and so on (unlike obsidian, you gotta pay).
The app is quite important, acting as another copy of those oh shit moments!

I will document this in the issue sections with more details for sure. I did :P (edited) https://github.com/TriliumNext/Notes/issues/2268

I am not a developer, I cant know whats best really. Flathub did seem a solid idea to get more users especially with the upcoming rollback namechange!

[philipmgrant]

Does it make sense to get the existing app removed from Flathub? It's based on v0.63.7 of the pre-Next Trilium project - https://flathub.org/apps/com.github.zadam.trilium

Probably good to avoid anyone installing that and being frustrated that it's out of date.

[FliegendeWurst]

Perhaps this would also be a good time to get a landing page going: https://github.com/TriliumNext/Notes/issues/339
I might have some time to create a basic landing page in the next few weeks.

It would also be nice to get a domain name for the landing page (and eventually, docs).
Common TLDs (.net / .org / .info) cost about $10 / year per domain. .eu costs even less, and I already got that one for a year, in case we want to use it.

[eliandoran]

@FliegendeWurst , absolutely good point.
I have already started some work on the website, but I would appreciate some ideas/content, or even design contributions.
Everything is already pushed in apps/website.

Regarding the domain, we've bought triliumnotes.org. I'm not 100% happy with it since I would have preferred a .com (but someone bought it), or a shorter one like trilium.org (also parked).

[meichthys]

I believe @perfectra1n has triliumnext.com
trilium-notes.com is still available.

[perfectra1n]

Yeah - Elian is a connoisseur of Trilium domains currently lol

He’s looking for fine vintage of “.com” domains 🧐

[FliegendeWurst]

• Port the issues and discussions over to the original repository.

I'm wondering, wouldn't this mess up ~all issue/PR references (#<number>)?

Github does have a built-in "Issue transfer" feature, but it won't transfer references in old commits / comments.

EDIT: just noticed #170 is still open. Perhaps we can close it after rebranding back, and writing a short summary of the situation.

[eliandoran]

I'm wondering, wouldn't this mess up ~all issue/PR references (#)?

@FliegendeWurst, it sure will, unless we rewrite the commits (i'd have to think about it).
Either way, even in this fork we had commits pointing to issues in the old repo that exhibited the same issue.

[FliegendeWurst]

Another option would be to rename TriliumNext/trilium → TriliumNext/trilium-old (or similar), and then just keep the new repository. Or is there a reason we don't want to do that? Only for the transparent redirect of old links to zadam/trilium to the updated repository?

I'm worried we'll have to go on a little detective mission for every old issue/PR reference... especially since more than 2000 IDs are valid in both repositories.
Commit history rewriting is best avoided at all costs, as far as I know.