transition could be smoother than I expected it seems, at least based on this thread's comment https://github.com/zadam/trilium/issues/4620#issuecomment-2509921587 Now, I didn't try myself... I was considering to give Trilium a try to replace Obsidian but I'll wait for Trilium Next to be available and stable in Cloudron.

There are threads saying that running in Terminal xattr -c /path/to/app will clear the flag. Mixed feelings about this. hey, why not, surely devs on Trilium are legit and it's just Apple bureaucracy err, that's a slippery slope and the protection's are there for a purpose. hmmm, are Trilium devs not committed enough to sign their apps properly (it's not difficult compared to the rest of their dev effort, jeez, even I have an Apple developer licence. Going to take a timeout and just use the browser interface for now.

Right, Cloudron won't be able to backup individual notes or export them since it has no clue about what's going on inside an app. Solution has to come from Trilium itself.

@jdaviescoates Oh, right on. Thanks! I didn't look closely enough at that page.

@girish Damn. I wasn't expecting resolution that rapidly! Thanks! Updated. Solved.

@nebulon Posting here the reply from project owner, in case it is useful to someone later on: I'm wondering if it is possible to make notes protected by default? Kind of. The protected status is "inherited" from the parent note when creating it. So if you make all notes protected then any new note created will be protected by default (since any possible parent is also protected). This applies while in protected session. Also, can one edit the duration of a protected session (by default 10 minutes)? Yes, in Options -> Other -> Protected session timeout

This is not related to Trilium, but the previous Ferdi maintainer (who was different from the owner), has restarted working in a fork, Ferdium. There's no binary out, but I'm on the alpha and all is working as before for me, so I'm happy. Link: https://github.com/ferdium/

@girish Good point, I thought this was coming from cloudron package I'll investigate where this is coming from further, thanks for the hint !

@zezaung hm in this case, it may be better reported in the upstream project I think, they are the experts on their app internals.